<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Fixed vs Fluid Website Layouts</title>
	<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/</link>
	<description>Patrick Burt</description>
	<pubDate>Sat, 22 Nov 2008 06:38:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Patrick Burt</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-4220</link>
		<author>Patrick Burt</author>
		<pubDate>Fri, 13 Jun 2008 12:26:05 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-4220</guid>
		<description>min-height as well as max-width, are not valid in all browsers iirc.</description>
		<content:encoded><![CDATA[<p>min-height as well as max-width, are not valid in all browsers iirc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robberto</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-4216</link>
		<author>Robberto</author>
		<pubDate>Fri, 13 Jun 2008 09:37:51 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-4216</guid>
		<description>In fluid layouts you can solve the problem with line length by using css to give that div. a "max-width: 700px" (or whatever width suits you). 

See the effect at the simple layout I 'm experimenting with on my website.</description>
		<content:encoded><![CDATA[<p>In fluid layouts you can solve the problem with line length by using css to give that div. a &#8220;max-width: 700px&#8221; (or whatever width suits you). </p>
<p>See the effect at the simple layout I &#8216;m experimenting with on my website.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Burt</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-3048</link>
		<author>Patrick Burt</author>
		<pubDate>Thu, 03 Apr 2008 14:37:53 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-3048</guid>
		<description>Hi Devman, thanks for the comment.

The fluid/liquid layouts I've seen were often the result of web developers rather then web designers. Although there are bare areas to the right and to the left of fixed layout websites, they don't give a sense that the website is barren or lacking. Which I like. :)</description>
		<content:encoded><![CDATA[<p>Hi Devman, thanks for the comment.</p>
<p>The fluid/liquid layouts I&#8217;ve seen were often the result of web developers rather then web designers. Although there are bare areas to the right and to the left of fixed layout websites, they don&#8217;t give a sense that the website is barren or lacking. Which I like. <img src='http://www.pat-burt.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devman</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-3046</link>
		<author>Devman</author>
		<pubDate>Thu, 03 Apr 2008 14:22:46 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-3046</guid>
		<description>Well, this is an interesting topic.  I prefer the fixed size.  A website is merely a marketing tool.  There are lots of debates but when it comes down to it even if you are selling products directly the site is there for a marketing purpose.  Now, if you come at it from a marketing perpective you want to keep the look to be the overal experience that was intended.  I have not seen a fluid/liquid layout that actually does this.  For example, on this sit the article whould be about 1/3 the size (hieght wize) and the comments would be very tiny looking.  Giving the website a baron and laking feeling.  I am sure not what the author would want to portray.

It is just like movie, it has an aspect ratio because that is the way it is ment to be viewed.  Sure some televisions will strech and pull an image but that is up to the end user.  Much like what browsers are doing now with zoom.  Anyway that is my 2 cents.  The idea of fluid is great but when a site does go really big or small i have never seen one that looks good (or looks like what the designer would intend), there is always a general browser size that works best for any site.  Which is why i think that people with large monitors don't have the browsers in full screen.  So why not just fix the size.</description>
		<content:encoded><![CDATA[<p>Well, this is an interesting topic.  I prefer the fixed size.  A website is merely a marketing tool.  There are lots of debates but when it comes down to it even if you are selling products directly the site is there for a marketing purpose.  Now, if you come at it from a marketing perpective you want to keep the look to be the overal experience that was intended.  I have not seen a fluid/liquid layout that actually does this.  For example, on this sit the article whould be about 1/3 the size (hieght wize) and the comments would be very tiny looking.  Giving the website a baron and laking feeling.  I am sure not what the author would want to portray.</p>
<p>It is just like movie, it has an aspect ratio because that is the way it is ment to be viewed.  Sure some televisions will strech and pull an image but that is up to the end user.  Much like what browsers are doing now with zoom.  Anyway that is my 2 cents.  The idea of fluid is great but when a site does go really big or small i have never seen one that looks good (or looks like what the designer would intend), there is always a general browser size that works best for any site.  Which is why i think that people with large monitors don&#8217;t have the browsers in full screen.  So why not just fix the size.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 Variables of Article Readability &#187; Wayne Liew Dot Com</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-1109</link>
		<author>10 Variables of Article Readability &#187; Wayne Liew Dot Com</author>
		<pubDate>Tue, 27 Nov 2007 12:45:17 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-1109</guid>
		<description>[...] more of it at Fixed vs Fluid Website Layouts and do you see why this affects your post [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] more of it at Fixed vs Fluid Website Layouts and do you see why this affects your post [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Design and Some Weekly Links &#60;&#60; Vandelay Website Design</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-278</link>
		<author>New Design and Some Weekly Links &#60;&#60; Vandelay Website Design</author>
		<pubDate>Sat, 25 Aug 2007 16:09:03 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-278</guid>
		<description>[...] Fixed vs. Fluid Layouts from Patrick Burt. This article covers the differences between the two different styles of layout, with the advantages of each. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Fixed vs. Fluid Layouts from Patrick Burt. This article covers the differences between the two different styles of layout, with the advantages of each. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Burt</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-258</link>
		<author>Patrick Burt</author>
		<pubDate>Fri, 24 Aug 2007 00:47:21 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-258</guid>
		<description>Xeos, please don't mention font tags, I might get a hernia. :P

Anyways, I am working on a slight redesign/tweak. I'll be honest, when I did this template (really quick) i didn't know the limitations/options in WordPress. Now I'm pretty aware of what's going on, so I can afford to do something a little cooky.</description>
		<content:encoded><![CDATA[<p>Xeos, please don&#8217;t mention font tags, I might get a hernia. <img src='http://www.pat-burt.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>Anyways, I am working on a slight redesign/tweak. I&#8217;ll be honest, when I did this template (really quick) i didn&#8217;t know the limitations/options in WordPress. Now I&#8217;m pretty aware of what&#8217;s going on, so I can afford to do something a little cooky.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xeos Celeres</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-249</link>
		<author>Xeos Celeres</author>
		<pubDate>Thu, 23 Aug 2007 13:01:30 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-249</guid>
		<description>Your post + Kevins comment makes this an interesting topic. It is highly essential that the site looks consistent. And when I say consistent, I also mean the issues like: When you goto another page on the same site, and you notice this 'nudge' or some of the content move.

Remember the old days when there wasn't any CSS ? Oh man. Anyway, I do prefer a fixed layout. Most people with widescreen monitors and high resolutions usually work in window mode anyway. Unless they are doing heavy duty stuff that requires alot of real estate - like 3D, or post production.</description>
		<content:encoded><![CDATA[<p>Your post + Kevins comment makes this an interesting topic. It is highly essential that the site looks consistent. And when I say consistent, I also mean the issues like: When you goto another page on the same site, and you notice this &#8216;nudge&#8217; or some of the content move.</p>
<p>Remember the old days when there wasn&#8217;t any CSS ? Oh man. Anyway, I do prefer a fixed layout. Most people with widescreen monitors and high resolutions usually work in window mode anyway. Unless they are doing heavy duty stuff that requires alot of real estate - like 3D, or post production.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Burt</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-235</link>
		<author>Patrick Burt</author>
		<pubDate>Wed, 22 Aug 2007 13:20:48 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-235</guid>
		<description>Thanks for the lengthy comment Kevin.
Being a Adobe Flash guy myself, I often find it convenient and exponentially easier to design for a fixed layout.

As for site looking the same all the time, for example, if you have a graphical banner, sometimes it's inconvenient to make sure it's left side and/or right side of the graphic can expand as the monitor expands. 

The sites where content is moved based on browser/window size, do you have a link to that resource? I imagine it has to do with Javascript figuring out browser/window size and changing style attributes, eg. changing display from inline to block.

I'm definitely looking forward to CSS 3 spec and agree with the suggestions you mentioned in your final paragraph.

Again, thanks for the comment Kevin, appreciate it buddy. :)</description>
		<content:encoded><![CDATA[<p>Thanks for the lengthy comment Kevin.<br />
Being a Adobe Flash guy myself, I often find it convenient and exponentially easier to design for a fixed layout.</p>
<p>As for site looking the same all the time, for example, if you have a graphical banner, sometimes it&#8217;s inconvenient to make sure it&#8217;s left side and/or right side of the graphic can expand as the monitor expands. </p>
<p>The sites where content is moved based on browser/window size, do you have a link to that resource? I imagine it has to do with Javascript figuring out browser/window size and changing style attributes, eg. changing display from inline to block.</p>
<p>I&#8217;m definitely looking forward to CSS 3 spec and agree with the suggestions you mentioned in your final paragraph.</p>
<p>Again, thanks for the comment Kevin, appreciate it buddy. <img src='http://www.pat-burt.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-216</link>
		<author>Kevin</author>
		<pubDate>Mon, 20 Aug 2007 17:58:51 +0000</pubDate>
		<guid>http://www.pat-burt.com/web-usability/fixed-vs-fluid-website-layouts/#comment-216</guid>
		<description>Line length, font size, and readability are problems I am often faced with. However, I frequently find it easier to code a site for a specific resolution. There is no cut and dry answer, and not all advantages are created equal. That said, I believe that most sites should be liquid (as does Jakob Nielson). Here's why:

Knowing what your site should look like all the time: You should know what it'll look like in different situations anyway, and you can use css to reduce some of the variety.

Preventing long line lengths: This is the biggest problem in my opinion. However, just because a user has a 1920x1200 pixel resolution doesn't mean they are/should be filling the entire thing up with a web page. I believe maximizing everything is primarily a Microsoft Windows behavior. If the line lengths are too long, at least the user has the option of reducing the browser's width with a liquid layout. Liquid is also more accommodating is the site’s visitor is using a larger-than-normal font size.

There are sites that have columns that when there is space available move to the right, reducing the vertical scrolling. Otherwise they place themselves below the regular content. This is in my opinion the ideal situation.

At any rate, many of these line length issues will be solved (or at least delayed) once the CSS 3 spec is finished and implemented on web browsers. The column attribute will allow columns to be implemented easily without javascript hacks to equal out the column height.

In the end however, I believe that choosing one over the other depends on the content of the website. Photo galleries for instance look best with the more space they have. Also, search engine result pages are often superior with long ling lengths so that more results can be fit in vertically. Blogs on the hand look best with reduced widths.</description>
		<content:encoded><![CDATA[<p>Line length, font size, and readability are problems I am often faced with. However, I frequently find it easier to code a site for a specific resolution. There is no cut and dry answer, and not all advantages are created equal. That said, I believe that most sites should be liquid (as does Jakob Nielson). Here&#8217;s why:</p>
<p>Knowing what your site should look like all the time: You should know what it&#8217;ll look like in different situations anyway, and you can use css to reduce some of the variety.</p>
<p>Preventing long line lengths: This is the biggest problem in my opinion. However, just because a user has a 1920&#215;1200 pixel resolution doesn&#8217;t mean they are/should be filling the entire thing up with a web page. I believe maximizing everything is primarily a Microsoft Windows behavior. If the line lengths are too long, at least the user has the option of reducing the browser&#8217;s width with a liquid layout. Liquid is also more accommodating is the site’s visitor is using a larger-than-normal font size.</p>
<p>There are sites that have columns that when there is space available move to the right, reducing the vertical scrolling. Otherwise they place themselves below the regular content. This is in my opinion the ideal situation.</p>
<p>At any rate, many of these line length issues will be solved (or at least delayed) once the CSS 3 spec is finished and implemented on web browsers. The column attribute will allow columns to be implemented easily without javascript hacks to equal out the column height.</p>
<p>In the end however, I believe that choosing one over the other depends on the content of the website. Photo galleries for instance look best with the more space they have. Also, search engine result pages are often superior with long ling lengths so that more results can be fit in vertically. Blogs on the hand look best with reduced widths.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
