<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Blog shakedown cruising</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2008/08/22/blog-shakedown-cruising/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2008/08/22/blog-shakedown-cruising/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Tue, 01 Dec 2009 01:39:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Don Marti</title>
		<link>http://blogs.law.harvard.edu/doc/2008/08/22/blog-shakedown-cruising/comment-page-1/#comment-78410</link>
		<dc:creator>Don Marti</dc:creator>
		<pubDate>Sat, 23 Aug 2008 04:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=897#comment-78410</guid>
		<description>The body copy on useit.com is too wide--it&#039;s like awful default single-spaced word processor layout.  Yeech.

The biggest problem with just plain readability on the web is that older versions of MSIE don&#039;t support CSS max-width, so it&#039;s a challenge to make lines with a comfortable, readable width for all users.  Make a &quot;springy&quot; layout but set max-width in ems (30-45em is good for a blog), and it works for users with a wide variety of browser window sizes and text sizes.

(Quick web design test: resize the browser window to 800 wide and the text to 16pt.  If you can still use all the site&#039;s functionality, you win.)</description>
		<content:encoded><![CDATA[<p>The body copy on&nbsp;<a href="http://useit.com" title="http://useit. " target="_blank">useit.com</a> is too wide&#8211;it&#8217;s like awful default single-spaced word processor layout.  Yeech.</p>
<p>The biggest problem with just plain readability on the web is that older versions of MSIE don&#8217;t support CSS max-width, so it&#8217;s a challenge to make lines with a comfortable, readable width for all users.  Make a &#8220;springy&#8221; layout but set max-width in ems (30-45em is good for a blog), and it works for users with a wide variety of browser window sizes and text sizes.</p>
<p>(Quick web design test: resize the browser window to 800 wide and the text to 16pt.  If you can still use all the site&#8217;s functionality, you win.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harl Delos</title>
		<link>http://blogs.law.harvard.edu/doc/2008/08/22/blog-shakedown-cruising/comment-page-1/#comment-78343</link>
		<dc:creator>Harl Delos</dc:creator>
		<pubDate>Fri, 22 Aug 2008 21:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=897#comment-78343</guid>
		<description>I&#039;m ambivalent about Jakob. 

&lt;i&gt;This&lt;/i&gt; website is highly usable. Jakob&#039;s is not. You seem to understand that &quot;to emphasize everything is to emphasize nothing.&quot; You also make good use of color and typography to keep your site &lt;i&gt;simple&lt;/i&gt;. Jakob&#039;s does not. 

Jakob&#039;s biggest detractors, though, tend to have highly unusable websites. They take forever to load, they have compatibility problems, &lt;i&gt;and they don&#039;t say anything&lt;/i&gt;.

Quick! Does anyone remember what the T in HTML stands for?</description>
		<content:encoded><![CDATA[<p>I&#8217;m ambivalent about Jakob. </p>
<p><i>This</i> website is highly usable. Jakob&#8217;s is not. You seem to understand that &#8220;to emphasize everything is to emphasize nothing.&#8221; You also make good use of color and typography to keep your site <i>simple</i>. Jakob&#8217;s does not. </p>
<p>Jakob&#8217;s biggest detractors, though, tend to have highly unusable websites. They take forever to load, they have compatibility problems, <i>and they don&#8217;t say anything</i>.</p>
<p>Quick! Does anyone remember what the T in HTML stands for?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
