<?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: To Split or not to Split</title>
	<atom:link href="http://webgrrrl.net/archives/to-split-or-not-to-split.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://webgrrrl.net/archives/to-split-or-not-to-split.htm</link>
	<description>I blog for the same reason I breathe -- because if I didn't, I would die. - Isaac Asimov + me@webgrrrl.net</description>
	<pubDate>Sun, 23 Nov 2008 10:51:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: ritchie</title>
		<link>http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-831</link>
		<dc:creator>ritchie</dc:creator>
		<pubDate>Fri, 22 Jun 2007 08:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-831</guid>
		<description>I fully disagree that it's better to either use the more tag always or never. Gotta get the readers used to their clickpath.</description>
		<content:encoded><![CDATA[<p>I fully disagree that it&#8217;s better to either use the more tag always or never. Gotta get the readers used to their clickpath.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorna</title>
		<link>http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-820</link>
		<dc:creator>Lorna</dc:creator>
		<pubDate>Tue, 19 Jun 2007 22:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-820</guid>
		<description>Wow, if I had a post that's 3000+ words long, it's definitely a no-brainer for me -- I'll have to use the MORE tag. I find it great that you would take into equation your mobile phone users. I'm embarrassed to admit that most of the time I've taken the selfish approach by setting my blog the way I like it. To each her/his own, I guess. Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Wow, if I had a post that&#8217;s 3000+ words long, it&#8217;s definitely a no-brainer for me &#8212; I&#8217;ll have to use the MORE tag. I find it great that you would take into equation your mobile phone users. I&#8217;m embarrassed to admit that most of the time I&#8217;ve taken the selfish approach by setting my blog the way I like it. To each her/his own, I guess. Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnorb</title>
		<link>http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-819</link>
		<dc:creator>Gnorb</dc:creator>
		<pubDate>Tue, 19 Jun 2007 20:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://webgrrrl.net/archives/to-split-or-not-to-split.htm#comment-819</guid>
		<description>This is an issue I wrestled with for a long time. For a while, I had a mix going, where short posts were all in the front page and long posts were split. What I found was that the long posts weren't getting read!

I then decided to do a full frontal, and just put the posts in the front. Problem was that some of my posts were 3000+ words long, making it almost impossible to make it to the bottom of the page without a Sherpa or an oxygen tank. (I even broke a few mouse wheels trying to get to the bottom of the page!) This was especially annoying to cell phone users who browsed the page, since they would either have to wait a long time to download the entire page, or simply not get everything. Finally, it also annoyed readers in countries where 56K was the fastest regularly available speed.

Finally, I decided to crop ALL of my posts with the MORE tag, unless they're quite literally one paragraph long. Those which are one paragraph or less make it to the asides area and not to the main area. Everything that makes it to the main floor (so to speak) has a MORE tag to it. This way I've created an expectation in my readers that to read the full content they should always click the more tag if they want to read it. (If they don't, they don't have to keep scrolling down to find the next article.) Additionally, it shortens the page, which is great for quick browsers as well as mobile phone users. Finally, it forces me to improve my first paragraph enticement skills by giving them a reason to click. 

Using this third method has increased my pageviews, increased my readership, helped me improve my writing, and created a page that's small enough to be enjoyed by almost every type of user. Overall, I found it to be one of my best decisions.</description>
		<content:encoded><![CDATA[<p>This is an issue I wrestled with for a long time. For a while, I had a mix going, where short posts were all in the front page and long posts were split. What I found was that the long posts weren&#8217;t getting read!</p>
<p>I then decided to do a full frontal, and just put the posts in the front. Problem was that some of my posts were 3000+ words long, making it almost impossible to make it to the bottom of the page without a Sherpa or an oxygen tank. (I even broke a few mouse wheels trying to get to the bottom of the page!) This was especially annoying to cell phone users who browsed the page, since they would either have to wait a long time to download the entire page, or simply not get everything. Finally, it also annoyed readers in countries where 56K was the fastest regularly available speed.</p>
<p>Finally, I decided to crop ALL of my posts with the MORE tag, unless they&#8217;re quite literally one paragraph long. Those which are one paragraph or less make it to the asides area and not to the main area. Everything that makes it to the main floor (so to speak) has a MORE tag to it. This way I&#8217;ve created an expectation in my readers that to read the full content they should always click the more tag if they want to read it. (If they don&#8217;t, they don&#8217;t have to keep scrolling down to find the next article.) Additionally, it shortens the page, which is great for quick browsers as well as mobile phone users. Finally, it forces me to improve my first paragraph enticement skills by giving them a reason to click. </p>
<p>Using this third method has increased my pageviews, increased my readership, helped me improve my writing, and created a page that&#8217;s small enough to be enjoyed by almost every type of user. Overall, I found it to be one of my best decisions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
