<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Fixing your width: what&#8217;s the optimal size for a site?</title>
	<atom:link href="http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Fri, 21 Nov 2008 12:52:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-705</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 22 Sep 2006 16:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-705</guid>
		<description>Thanks, Tedd - I'm aware of the problem.  I'm using an image replacement technique where the dimensions of the banner area are expresed in &lt;code&gt;ems&lt;/code&gt; - so at small zooms, it disappears.  

Haven't worked out a good solution, yet.

Your comment about handling real estate are right on - using the space available means being flexible, since we have no way of controlling what space that will be.  It's not just about allowing a site to expand to fill larger screens, but making certain it's still usable in smaller ones!</description>
		<content:encoded><![CDATA[<p>Thanks, Tedd - I&#8217;m aware of the problem.  I&#8217;m using an image replacement technique where the dimensions of the banner area are expresed in <code>ems</code> - so at small zooms, it disappears.  </p>
<p>Haven&#8217;t worked out a good solution, yet.</p>
<p>Your comment about handling real estate are right on - using the space available means being flexible, since we have no way of controlling what space that will be.  It&#8217;s not just about allowing a site to expand to fill larger screens, but making certain it&#8217;s still usable in smaller&nbsp;ones!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-704</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Fri, 22 Sep 2006 16:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-704</guid>
		<description>For years now I've done fixed width sites -- like so many billboards, just boring testaments of days gone by before Ladybird's beautification mandate, which predate most of you.

But now, I think the concept of "the medium is the message" is starting to influence web design and user expectations.

I think we collectively are viewing the browser window differently now -- it's not the printed page, as ecommerce is not "brick and mortar". The differences are becoming more apparent, acceptable, and even expected.

What we are faced with now, is how to be best handle real estate. The browser window is not fixed, and our charge is to best use what we are given and to do so to the widest audience possible.

As such, I no longer do "fixed width" but rather different fluid and em based sites with emphases on accessibility. Granted I still have to live with clients who have not seen the light, but that comes with the territory. My charge is to best see to their needs and not to their misconceptions.

tedd
http://sperling.com

PS: On small zooms, your logo banner disappears (Mac OS-X 10.4.7 Safari 2.0.4)</description>
		<content:encoded><![CDATA[<p>For years now I&#8217;ve done fixed width sites&thinsp;&#8212;&thinsp;like so many billboards, just boring testaments of days gone by before Ladybird&#8217;s beautification mandate, which predate most of you.</p>
<p>But now, I think the concept of &#8220;the medium is the message&#8221; is starting to influence web design and user expectations.</p>
<p>I think we collectively are viewing the browser window differently now&thinsp;&#8212;&thinsp;it&#8217;s not the printed page, as ecommerce is not &#8220;brick and mortar&#8221;. The differences are becoming more apparent, acceptable, and even expected.</p>
<p>What we are faced with now, is how to be best handle real estate. The browser window is not fixed, and our charge is to best use what we are given and to do so to the widest audience possible.</p>
<p>As such, I no longer do &#8220;fixed width&#8221; but rather different fluid and em based sites with emphases on accessibility. Granted I still have to live with clients who have not seen the light, but that comes with the territory. My charge is to best see to their needs and not to their misconceptions.</p>
<p>tedd<br />
<a href="http://sperling.com">http://sperling.com</a></p>
<p>PS: On small zooms, your logo banner disappears (Mac OS-X 10.4.7 Safari&nbsp;2.0.4)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-703</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 22 Sep 2006 14:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-703</guid>
		<description>I can see your argument, and I'm willing to buy it about half the time...

Fixed width weblogs fall down in fixed-width when he font-size is increased - resulting in too-short lines.  However, it could be argued that too-short lines are less of a problem then too-long lines.

I go back and forth - what I prefer, in that case, is more of a zoom layout - expanding with the text, giving control of proportions to the designer.</description>
		<content:encoded><![CDATA[<p>I can see your argument, and I&#8217;m willing to buy it about half the time&#8230;</p>
<p>Fixed width weblogs fall down in fixed-width when he font-size is increased - resulting in too-short lines.  However, it could be argued that too-short lines are less of a problem then too-long lines.</p>
<p>I go back and forth - what I prefer, in that case, is more of a zoom layout - expanding with the text, giving control of proportions to the&nbsp;designer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thud</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-701</link>
		<dc:creator>Thud</dc:creator>
		<pubDate>Fri, 22 Sep 2006 13:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-701</guid>
		<description>Fixed-width sites are handy if you have a text-heavy site with simple navigation. Fluid-width sites fail when you don't have the content to support the use of screen real-estate. You end up with long scan lines and a lot of unbalanced white space. So weblogs are a great candidate for fixed-width (he says, even though his own is currently fluid).</description>
		<content:encoded><![CDATA[<p>Fixed-width sites are handy if you have a text-heavy site with simple navigation. Fluid-width sites fail when you don&#8217;t have the content to support the use of screen real-estate. You end up with long scan lines and a lot of unbalanced white space. So weblogs are a great candidate for fixed-width (he says, even though his own is currently&nbsp;fluid).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-631</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Sun, 17 Sep 2006 14:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-631</guid>
		<description>I've also used fixed-width, fixed-heights, etc.  &lt;code&gt;em&lt;/code&gt; based widths aren't something I've explored extensively (although I'm building one right now, as it happens), but I do like the way they maintain proportions.  

Still, assuming a considerate designer, the only reasons for fixed width seem to be designer-focused...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also used fixed-width, fixed-heights, etc.  <code>em</code> based widths aren&#8217;t something I&#8217;ve explored extensively (although I&#8217;m building one right now, as it happens), but I do like the way they maintain proportions.  </p>
<p>Still, assuming a considerate designer, the only reasons for fixed width seem to be&nbsp;designer-focused&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cherim</title>
		<link>http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-630</link>
		<dc:creator>Mike Cherim</dc:creator>
		<pubDate>Sun, 17 Sep 2006 13:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2006/09/fixing-your-width-whats-the-optimal-size-for-a-site/#comment-630</guid>
		<description>I will use fixed width at times (and height on upper elements), especially if image control is important, and sometimes it is: The &lt;a href="http://thompsoncenterassoc.org/" rel="nofollow"&gt;Thompson Center Association&lt;/a&gt; site I built really requires it (760px width with a fixed height masthead). 

My favorite method is the way &lt;a href="http://accessites.org" rel="nofollow"&gt;Accessites.org&lt;/a&gt; is built in that it uses &lt;code&gt;EM&lt;/code&gt;s for width which keeps proportion even better that of fixed-width sites in that the first couple of text enlargements don't have a big effect on the vertical size of elements due to text wrapping, etc. The thing to do is apply &lt;code&gt;max-width&lt;/code&gt; as you noted. &lt;code&gt;Max-width&lt;/code&gt; isn't supported by IE, so to make the whole thing work well in that browser you have to begin with a narrow enough &lt;code&gt;EM&lt;/code&gt;-based width to allow the thing to grow (its two increase sizes) without expanding beyond the viewport width -- at least on 1024x768. Given this, to see it with a horizontal scrollbar the number of variables is increased: It must be IE, &lt;em&gt;and&lt;/em&gt; 800x600 screen resolution or smaller, &lt;em&gt;and&lt;/em&gt; the text must be enlarged. It's not a perfect method, but pretty close simply by limiting the possibilities that someone gets a horizontal scrollbar. If it wasn't for IE, &lt;code&gt;EM&lt;/code&gt;s coupled with &lt;code&gt;max-width&lt;/code&gt; would be just about perfect! Using Accessites as an example, it works and looks good from 640x480 right on up to whatever size in a &lt;code&gt;max-width&lt;/code&gt;-supporting browser. Its keep the design really stable.

Liquid really is best, but only &lt;em&gt;if&lt;/em&gt; the developer develops the site knowing that design control  will be left entirely to the user. This some might say is best, and I won't argue, but sometimes I do want some control. I can't help it.</description>
		<content:encoded><![CDATA[<p>I will use fixed width at times (and height on upper elements), especially if image control is important, and sometimes it is: The <a href="http://thompsoncenterassoc.org/">Thompson Center Association</a> site I built really requires it (760px width with a fixed height masthead). </p>
<p>My favorite method is the way <a href="http://accessites.org">Accessites.org</a> is built in that it uses <code>EM</code>s for width which keeps proportion even better that of fixed-width sites in that the first couple of text enlargements don&#8217;t have a big effect on the vertical size of elements due to text wrapping, etc. The thing to do is apply <code>max-width</code> as you noted. <code>Max-width</code> isn&#8217;t supported by <acronym title="Internet Explorer">IE</acronym>, so to make the whole thing work well in that browser you have to begin with a narrow enough <code>EM</code>-based width to allow the thing to grow (its two increase sizes) without expanding beyond the viewport width&thinsp;&#8212;&thinsp;at least on 1024x768. Given this, to see it with a horizontal scrollbar the number of variables is increased: It must be <acronym title="Internet Explorer">IE</acronym>, <em>and</em> 800x600 screen resolution or smaller, <em>and</em> the text must be enlarged. It&#8217;s not a perfect method, but pretty close simply by limiting the possibilities that someone gets a horizontal scrollbar. If it wasn&#8217;t for <acronym title="Internet Explorer">IE</acronym>, <code>EM</code>s coupled with <code>max-width</code> would be just about perfect! Using Accessites as an example, it works and looks good from 640x480 right on up to whatever size in a <code>max-width</code>-supporting browser. Its keep the design really stable.</p>
<p>Liquid really is best, but only <em>if</em> the developer develops the site knowing that design control  will be left entirely to the user. This some might say is best, and I won&#8217;t argue, but sometimes I do want some control. I can&#8217;t help&nbsp;it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
