<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Black and Brown and 960 all over</title>
	<atom:link href="http://www.zeldman.com/2006/09/15/blackandbrown/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zeldman.com/2006/09/15/blackandbrown/</link>
	<description>Web design news and insights since 1995</description>
	<lastBuildDate>Wed, 17 Mar 2010 03:24:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan Nicol</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3520</link>
		<dc:creator>Jonathan Nicol</dc:creator>
		<pubDate>Sat, 30 Sep 2006 10:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3520</guid>
		<description>The Brown University homepage is certainly impressive, but it doesn&#039;t hold up so well if you increase your browser&#039;s font size. Long text &#039;teasers&#039; disappear out the bottom of their containers. Of course this won&#039;t affect IE users, as fonts are sized using - *cough* - pixels. Am I being bitchy?</description>
		<content:encoded><![CDATA[<p>The Brown University homepage is certainly impressive, but it doesn&#8217;t hold up so well if you increase your browser&#8217;s font size. Long text &#8216;teasers&#8217; disappear out the bottom of their containers. Of course this won&#8217;t affect IE users, as fonts are sized using &#8211; *cough* &#8211; pixels. Am I being bitchy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mediabistro.com: UnBeige</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3510</link>
		<dc:creator>mediabistro.com: UnBeige</dc:creator>
		<pubDate>Sat, 30 Sep 2006 00:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3510</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] It&#039;s one legend on another legend. Magazine Master Roger Black, who we&#039;ll be having Cheerios with on October 20, launched his new blog and Web Master Jeffrey Zeldman gives it the once over: Black&#039;s back! Black blogs! Site design by Rob Hunter. Love the &quot;simplify&quot; button. Red-and-black visual joke works, but shade of red needs fine-tuning. Having to employ drop-shadows on every character of body text (only Safari supports this) should be clue, if one were needed, that the background color doesn&#039;t work.     Posted by Alissa &#124; 07:26 PM &#124; web [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] It&#8217;s one legend on another legend. Magazine Master Roger Black, who we&#8217;ll be having Cheerios with on October 20, launched his new blog and Web Master Jeffrey Zeldman gives it the once over: Black&#8217;s back! Black blogs! Site design by Rob Hunter. Love the &#8220;simplify&#8221; button. Red-and-black visual joke works, but shade of red needs fine-tuning. Having to employ drop-shadows on every character of body text (only Safari supports this) should be clue, if one were needed, that the background color doesn&#8217;t work.     Posted by Alissa | 07:26 PM | web [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KeithB</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3349</link>
		<dc:creator>KeithB</dc:creator>
		<pubDate>Tue, 19 Sep 2006 20:23:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3349</guid>
		<description>rogerblack.com - falls apart on an iBook with 1024 by 768. I&#039;m obviously below this gentleman&#039;s threshold.

960px looks ok but remember that education uses computers that are 3 to 5 years old. Lots of 800 by 600 monitors floating round. We just upgraded &lt;em&gt;to&lt;/em&gt; Winders XP as we could find the money to replace the &lt;em&gt;really&lt;/em&gt; old computers this year.

I went for a liquid design on the personal blog  -and using a dl on the front page listing title and excerpt has increased the &#039;life&#039; of blog posts by a factor of two according to the logs. Most people can scan 5 stories above the fold rather than reading one in full.</description>
		<content:encoded><![CDATA[<p>rogerblack.com &#8211; falls apart on an iBook with 1024 by 768. I&#8217;m obviously below this gentleman&#8217;s threshold.</p>
<p>960px looks ok but remember that education uses computers that are 3 to 5 years old. Lots of 800 by 600 monitors floating round. We just upgraded <em>to</em> Winders XP as we could find the money to replace the <em>really</em> old computers this year.</p>
<p>I went for a liquid design on the personal blog  -and using a dl on the front page listing title and excerpt has increased the &#8216;life&#8217; of blog posts by a factor of two according to the logs. Most people can scan 5 stories above the fold rather than reading one in full.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: squareman</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3346</link>
		<dc:creator>squareman</dc:creator>
		<pubDate>Tue, 19 Sep 2006 17:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3346</guid>
		<description>Regarding RogerBlack.com:

I&#039;ve used the Safari-only drop shadows in a layout before too; but not because the foreground-backround contrast was too low. I did it because I found that Safari in some instances would annoyingly &quot;bloat&quot; or fuzz out some white text on backgrounds (like ink that was laid on too heavy to borrow a print metaphor). I couldn&#039;t quite track down what the issue was, but adding the drop shadows enhanced the readability in Safari while the readability was fine everywhere else.</description>
		<content:encoded><![CDATA[<p>Regarding RogerBlack.com:</p>
<p>I&#8217;ve used the Safari-only drop shadows in a layout before too; but not because the foreground-backround contrast was too low. I did it because I found that Safari in some instances would annoyingly &#8220;bloat&#8221; or fuzz out some white text on backgrounds (like ink that was laid on too heavy to borrow a print metaphor). I couldn&#8217;t quite track down what the issue was, but adding the drop shadows enhanced the readability in Safari while the readability was fine everywhere else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Ruby</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3304</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Sun, 17 Sep 2006 05:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3304</guid>
		<description>&lt;a href=&quot;http://blogs.msdn.com/rssteam/archive/2005/08/03/446904.aspx&quot; rel=&quot;nofollow&quot;&gt;Microsoft&lt;/a&gt;, &lt;a href=&quot;http://nick.typepad.com/blog/2006/05/pick_a_format_a.html&quot; rel=&quot;nofollow&quot;&gt;FeedDemon&lt;/a&gt;, &lt;a href=&quot;http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=cce109de-de25-4852-a8cf-319ccbf0013d&quot; rel=&quot;nofollow&quot;&gt;Bloglines&lt;/a&gt;, and others would prefer that you only provide one.

After all, do you provide XHTML and HTML versions for each of your pages?

But, if you wish to provide multiple feeds, all with the same content, simply pick the template over the plug-in.

My only additional suggestion is that you stick with x.0 formats, like RSS 1.0, RSS 2.0, and Atom 1.0.</description>
		<content:encoded><![CDATA[<p><a href="http://blogs.msdn.com/rssteam/archive/2005/08/03/446904.aspx" rel="nofollow">Microsoft</a>, <a href="http://nick.typepad.com/blog/2006/05/pick_a_format_a.html" rel="nofollow">FeedDemon</a>, <a href="http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=cce109de-de25-4852-a8cf-319ccbf0013d" rel="nofollow">Bloglines</a>, and others would prefer that you only provide one.</p>
<p>After all, do you provide XHTML and HTML versions for each of your pages?</p>
<p>But, if you wish to provide multiple feeds, all with the same content, simply pick the template over the plug-in.</p>
<p>My only additional suggestion is that you stick with x.0 formats, like RSS 1.0, RSS 2.0, and Atom 1.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Zeldman</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3303</link>
		<dc:creator>Jeffrey Zeldman</dc:creator>
		<pubDate>Sun, 17 Sep 2006 01:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3303</guid>
		<description>Sam:

&lt;blockquote&gt;
&lt;a href=&quot;http://benjamin.smedbergs.us/wordpress-atom-1.0/&quot; rel=&quot;nofollow&quot;&gt;The [Atom 1.0] plugin replaces all WordPress feeds. RSS will no longer be available...&lt;/a&gt;
&lt;/blockquote&gt;

Say what?</description>
		<content:encoded><![CDATA[<p>Sam:</p>
<blockquote><p>
<a href="http://benjamin.smedbergs.us/wordpress-atom-1.0/" rel="nofollow">The [Atom 1.0] plugin replaces all WordPress feeds. RSS will no longer be available&#8230;</a>
</p></blockquote>
<p>Say what?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Sweeting</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3297</link>
		<dc:creator>Brian Sweeting</dc:creator>
		<pubDate>Sat, 16 Sep 2006 15:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3297</guid>
		<description>The Brown University site is definitely innovative, but I don&#039;t like that the section expands on mouseover.  If you try to click on one of the links on the right side to go directly to that section, and you have a section that is already expanded above it, the section you mouseover expands up, and then you have to reaquire the target link.</description>
		<content:encoded><![CDATA[<p>The Brown University site is definitely innovative, but I don&#8217;t like that the section expands on mouseover.  If you try to click on one of the links on the right side to go directly to that section, and you have a section that is already expanded above it, the section you mouseover expands up, and then you have to reaquire the target link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Ruby</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3296</link>
		<dc:creator>Sam Ruby</dc:creator>
		<pubDate>Sat, 16 Sep 2006 14:07:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3296</guid>
		<description>You might be interested in an Atom 1.0 &lt;a href=&quot;http://www.snellspace.com/wp/?p=404&quot; rel=&quot;nofollow&quot;&gt;template&lt;/a&gt; or &lt;a href=&quot;http://benjamin.smedbergs.us/wordpress-atom-1.0/&quot; rel=&quot;nofollow&quot;&gt;plugin&lt;/a&gt; for WordPress.</description>
		<content:encoded><![CDATA[<p>You might be interested in an Atom 1.0 <a href="http://www.snellspace.com/wp/?p=404" rel="nofollow">template</a> or <a href="http://benjamin.smedbergs.us/wordpress-atom-1.0/" rel="nofollow">plugin</a> for WordPress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TextDrive Community Forum / Brown University</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3294</link>
		<dc:creator>TextDrive Community Forum / Brown University</dc:creator>
		<pubDate>Sat, 16 Sep 2006 13:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3294</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Zeldman agrees Way to go, man!  Blog: http://blog.jimvanfleet.com   Online &#160; [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Zeldman agrees Way to go, man!  Blog: <a href="http://blog.jimvanfleet.com" rel="nofollow">http://blog.jimvanfleet.com</a>   Online &nbsp; [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Zeldman</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3290</link>
		<dc:creator>Jeffrey Zeldman</dc:creator>
		<pubDate>Sat, 16 Sep 2006 11:10:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3290</guid>
		<description>&lt;blockquote&gt;
What is your take Mr. Z?
&lt;/blockquote&gt;

My take on 1024 vs. 800 is that it depends on the audience and the design. My take on fixed vs. liquid, likewise.</description>
		<content:encoded><![CDATA[<blockquote><p>
What is your take Mr. Z?
</p></blockquote>
<p>My take on 1024 vs. 800 is that it depends on the audience and the design. My take on fixed vs. liquid, likewise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3288</link>
		<dc:creator>patrick</dc:creator>
		<pubDate>Sat, 16 Sep 2006 05:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3288</guid>
		<description>And so the fixed vs. fluid debate continues.

Other than rubbing Jeremy Keith the wrong way (or some poor Windows using soul, still confined to the 800 x 600 purgatory), I see no harm in a fixed width site.  However, I really like the flexible option, such as the one that Dan Cederholm outlined in his book, Bulletproof Web Design.

The fact of the matter is, most web designers have a background in traditional design and they have a hard enough time getting over the fact that your final XHTML file might not match their design comp, pixel for pixel or the fact they are restricted to a limit number of fonts for body copy. 

It&#039;s the itchy tag of a new tee shirt, poking her in their neck - &#039;why doesn&#039;t this font look EXACTLY the same on the web as it does on my comp?&#039;

Perhaps pushing for fluid layouts across the board at this point is too much. I have just gotten my designers used to relative font sizing - they just don&#039;t see the value. *sigh*

It&#039;s looking more and more to me that the flexible width layout is the solution that lots of people can be happy with.</description>
		<content:encoded><![CDATA[<p>And so the fixed vs. fluid debate continues.</p>
<p>Other than rubbing Jeremy Keith the wrong way (or some poor Windows using soul, still confined to the 800 x 600 purgatory), I see no harm in a fixed width site.  However, I really like the flexible option, such as the one that Dan Cederholm outlined in his book, Bulletproof Web Design.</p>
<p>The fact of the matter is, most web designers have a background in traditional design and they have a hard enough time getting over the fact that your final XHTML file might not match their design comp, pixel for pixel or the fact they are restricted to a limit number of fonts for body copy. </p>
<p>It&#8217;s the itchy tag of a new tee shirt, poking her in their neck &#8211; &#8216;why doesn&#8217;t this font look EXACTLY the same on the web as it does on my comp?&#8217;</p>
<p>Perhaps pushing for fluid layouts across the board at this point is too much. I have just gotten my designers used to relative font sizing &#8211; they just don&#8217;t see the value. *sigh*</p>
<p>It&#8217;s looking more and more to me that the flexible width layout is the solution that lots of people can be happy with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mau</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3286</link>
		<dc:creator>Mau</dc:creator>
		<pubDate>Sat, 16 Sep 2006 01:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3286</guid>
		<description>Layouts:  I think that, even when they are harder to get right at first, the fluid layouts are the fittest solution... but I also agree that in a few years, the fittest solution will change.  

Here, the only constant &lt;em&gt;is change&lt;/em&gt;.

But, what is your take Mr. Z?</description>
		<content:encoded><![CDATA[<p>Layouts:  I think that, even when they are harder to get right at first, the fluid layouts are the fittest solution&#8230; but I also agree that in a few years, the fittest solution will change.  </p>
<p>Here, the only constant <em>is change</em>.</p>
<p>But, what is your take Mr. Z?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; Brown University</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3284</link>
		<dc:creator>Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; Brown University</dc:creator>
		<pubDate>Fri, 15 Sep 2006 23:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3284</guid>
		<description>[...] Brown University is valid XHTML 1.0 Strict and CSS. Try it with and without JavaScript enabled, nice work. (via Zeldman) [...]</description>
		<content:encoded><![CDATA[<p>[...] Brown University is valid XHTML 1.0 Strict and CSS. Try it with and without JavaScript enabled, nice work. (via Zeldman) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; Optimal Width For 1024</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3283</link>
		<dc:creator>Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; Optimal Width For 1024</dc:creator>
		<pubDate>Fri, 15 Sep 2006 23:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3283</guid>
		<description>[...] Optimal Width For 1024 is 960 which is very close to the number I&#8217;ve been finding best (without the math). Kind of interesting. (via Zeldman) [...]</description>
		<content:encoded><![CDATA[<p>[...] Optimal Width For 1024 is 960 which is very close to the number I&#8217;ve been finding best (without the math). Kind of interesting. (via Zeldman) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; RSS 2 And Atom Compared</title>
		<link>http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3282</link>
		<dc:creator>Pig Pen - Web Standards Compliant Web Design Blog &#187; Blog Archive &#187; RSS 2 And Atom Compared</dc:creator>
		<pubDate>Fri, 15 Sep 2006 23:03:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/2006/09/15/blackandbrown/#comment-3282</guid>
		<description>[...] RSS 2 And Atom Compared (via Zeldman) [...]</description>
		<content:encoded><![CDATA[<p>[...] RSS 2 And Atom Compared (via Zeldman) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
