<?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: The Holy Grail of Blog Design</title>
	<atom:link href="http://themeshaper.com/the-holy-grail-of-blog-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://themeshaper.com/the-holy-grail-of-blog-design/</link>
	<description>Experiments in Theme Design</description>
	<pubDate>Sat, 05 Jul 2008 17:40:12 +0000</pubDate>
	
		<item>
		<title>By: Ian Stewart</title>
		<link>http://themeshaper.com/the-holy-grail-of-blog-design/#comment-485</link>
		<dc:creator>Ian Stewart</dc:creator>
		<pubDate>Fri, 07 Mar 2008 23:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://themeshaper.com/the-holy-grail-of-blog-design#comment-485</guid>
		<description>It's really a tough call, James. You should know that I consider advertising-supported content a necessary evil and something I feel really conflicted about. That drives a lot of my thinking about ad/content placement. But I suspect that a layout that gives precedence to content &lt;em&gt;at the expense of ads&lt;/em&gt; would turn out in the long run to be more successful. It shows trust on your part and breeds loyalty. Loyal readers may click on ads less, and you may be unable to charge a top rate based on position, but loyal readers &lt;em&gt;are glad&lt;/em&gt; to click on ads.

… in my opinion, anyway. And again, this isn't an article about how to determine ad placement. It's about content placement.

I hope that helps get inside my head, James. :)</description>
		<content:encoded><![CDATA[<p>It&#8217;s really a tough call, James. You should know that I consider advertising-supported content a necessary evil and something I feel really conflicted about. That drives a lot of my thinking about ad/content placement. But I suspect that a layout that gives precedence to content <em>at the expense of ads</em> would turn out in the long run to be more successful. It shows trust on your part and breeds loyalty. Loyal readers may click on ads less, and you may be unable to charge a top rate based on position, but loyal readers <em>are glad</em> to click on ads.</p>
<p>… in my opinion, anyway. And again, this isn&#8217;t an article about how to determine ad placement. It&#8217;s about content placement.</p>
<p>I hope that helps get inside my head, James.&nbsp;:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Joyner</title>
		<link>http://themeshaper.com/the-holy-grail-of-blog-design/#comment-445</link>
		<dc:creator>James Joyner</dc:creator>
		<pubDate>Thu, 06 Mar 2008 17:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://themeshaper.com/the-holy-grail-of-blog-design#comment-445</guid>
		<description>Ian,

I'm not a designer but I'm not sure what I'm supposed to do with this information.

The reason two sidebars with content in the middle became the Holy Grail is that it allows more ads above-the-scroll.  Going to two columns, with the content on the left, leaves only one column for ads above-the-scroll AND it takes away one of the hot spots from the well-known Google heat chart you include above.

Most of the ads on my site are impression based rather than click based. Still, I can sell ads in that left column for more than I could in the right.</description>
		<content:encoded><![CDATA[<p>Ian,</p>
<p>I&#8217;m not a designer but I&#8217;m not sure what I&#8217;m supposed to do with this information.</p>
<p>The reason two sidebars with content in the middle became the Holy Grail is that it allows more ads above-the-scroll.  Going to two columns, with the content on the left, leaves only one column for ads above-the-scroll AND it takes away one of the hot spots from the well-known Google heat chart you include above.</p>
<p>Most of the ads on my site are impression based rather than click based. Still, I can sell ads in that left column for more than I could in the&nbsp;right.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
