<?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: LA Times redesign doesn’t quite click</title>
	<atom:link href="http://www.ojr.org/p1771/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ojr.org/p1771/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=p1771</link>
	<description>Focusing on the future of digital journalism</description>
	<lastBuildDate>Sun, 07 Apr 2013 15:02:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Tom Grubisich</title>
		<link>http://www.ojr.org/p1771/#comment-2020</link>
		<dc:creator>Tom Grubisich</dc:creator>
		<pubDate>Thu, 27 Aug 2009 13:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2020</guid>
		<description><![CDATA[The procrustean contortions to which the Times submits for its new minimalist design is typified by this prominent teaser on the homepage of the Aug. 27 edition:

&lt;blockquote&gt;&quot;Column: Is Fiorina]]></description>
		<content:encoded><![CDATA[<p>The procrustean contortions to which the Times submits for its new minimalist design is typified by this prominent teaser on the homepage of the Aug. 27 edition:</p>
<blockquote><p>&#8220;Column: Is Fiorina</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick green</title>
		<link>http://www.ojr.org/p1771/#comment-2019</link>
		<dc:creator>nick green</dc:creator>
		<pubDate>Wed, 26 Aug 2009 10:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2019</guid>
		<description><![CDATA[Also have to disagree about the bylines. like he says above &quot;bylines are not essential information to the page-browser and would only add to visual clutter.&quot;

And there is nothing more to say. ]]></description>
		<content:encoded><![CDATA[<p>Also have to disagree about the bylines. like he says above &#8220;bylines are not essential information to the page-browser and would only add to visual clutter.&#8221;</p>
<p>And there is nothing more to say. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 219.80.165.13</title>
		<link>http://www.ojr.org/p1771/#comment-2018</link>
		<dc:creator>219.80.165.13</dc:creator>
		<pubDate>Wed, 26 Aug 2009 06:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2018</guid>
		<description><![CDATA[I agree about the bylines.
]]></description>
		<content:encoded><![CDATA[<p>I agree about the bylines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Grubisich</title>
		<link>http://www.ojr.org/p1771/#comment-2017</link>
		<dc:creator>Tom Grubisich</dc:creator>
		<pubDate>Fri, 21 Aug 2009 16:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2017</guid>
		<description><![CDATA[Jay, you&#039;re right about Georgia bold.  It&#039;s too much. I hope it won&#039;t be too long before the Times can find (or develop on its own) a bold version that doesn&#039;t deliver sledgehammer impact.

Tim, some bylines are brands (to use Jay&#039;s characterization).  Why doesn&#039;t it make business sense to give them at least 6-point type mention in the promo?]]></description>
		<content:encoded><![CDATA[<p>Jay, you&#8217;re right about Georgia bold.  It&#8217;s too much. I hope it won&#8217;t be too long before the Times can find (or develop on its own) a bold version that doesn&#8217;t deliver sledgehammer impact.</p>
<p>Tim, some bylines are brands (to use Jay&#8217;s characterization).  Why doesn&#8217;t it make business sense to give them at least 6-point type mention in the promo?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Windsor</title>
		<link>http://www.ojr.org/p1771/#comment-2016</link>
		<dc:creator>Tim Windsor</dc:creator>
		<pubDate>Fri, 21 Aug 2009 13:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2016</guid>
		<description><![CDATA[I disagree about the bylines. Bylines are not essential information to the page-browser and would only add to visual clutter.

I think the LAT did a great job with this redesign. And if you want an idea how this grid could go wrong, you need look no further than other Trib sites which use the very same bones.

]]></description>
		<content:encoded><![CDATA[<p>I disagree about the bylines. Bylines are not essential information to the page-browser and would only add to visual clutter.</p>
<p>I think the LAT did a great job with this redesign. And if you want an idea how this grid could go wrong, you need look no further than other Trib sites which use the very same bones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Small</title>
		<link>http://www.ojr.org/p1771/#comment-2015</link>
		<dc:creator>Jay Small</dc:creator>
		<pubDate>Fri, 21 Aug 2009 10:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1771#comment-2015</guid>
		<description><![CDATA[Tom,

I agree with your remarks about the pieces of information left out on teasers to the Times&#039; primo work -- especially bylines where the writers are name brands.

Give the LATimes.com designers a break on use of the Georgia typeface, though.

Until all the various forms of custom font embedding being considered by Web standards bodies and programmers shake out, Georgia and Times New Roman remain the only two &quot;Web-safe&quot; serif font families. That&#039;s because they&#039;re the only two that are almost always resident on almost all versions of Microsoft Windows and Mac OS X.

So why not use more Georgia Bold? Well, have you seen Georgia Bold? For all the practical beauty that is Georgia, the Bold version looks too expanded, too filled-in, too different.

The best way to use Georgia in Web design is to apply sufficient contrast in size, not in weight. So there I agree with you, the site could use a touch more size contrast. At the same time, default body text is a tad too small for my eye, at least.

On balance, I think the redesign is a win. Usually, when I see user comments 50/50 or better favorable on a redesign, that looks like gold to me, and this one appears to get quite a few compliments.

(Incidentally, the designer of Georgia considers it a &quot;brother&quot; to Verdana, but not the &quot;serif version of Verdana.&quot; The two families have very different characteristics, beyond just that one is serif and one is sans serif.)
]]></description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>I agree with your remarks about the pieces of information left out on teasers to the Times&#8217; primo work &#8212; especially bylines where the writers are name brands.</p>
<p>Give the LATimes.com designers a break on use of the Georgia typeface, though.</p>
<p>Until all the various forms of custom font embedding being considered by Web standards bodies and programmers shake out, Georgia and Times New Roman remain the only two &#8220;Web-safe&#8221; serif font families. That&#8217;s because they&#8217;re the only two that are almost always resident on almost all versions of Microsoft Windows and Mac OS X.</p>
<p>So why not use more Georgia Bold? Well, have you seen Georgia Bold? For all the practical beauty that is Georgia, the Bold version looks too expanded, too filled-in, too different.</p>
<p>The best way to use Georgia in Web design is to apply sufficient contrast in size, not in weight. So there I agree with you, the site could use a touch more size contrast. At the same time, default body text is a tad too small for my eye, at least.</p>
<p>On balance, I think the redesign is a win. Usually, when I see user comments 50/50 or better favorable on a redesign, that looks like gold to me, and this one appears to get quite a few compliments.</p>
<p>(Incidentally, the designer of Georgia considers it a &#8220;brother&#8221; to Verdana, but not the &#8220;serif version of Verdana.&#8221; The two families have very different characteristics, beyond just that one is serif and one is sans serif.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>