<?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: Ditching &#8216;Next&#8217; and &#8216;Previous&#8217; for Blog Navigation</title>
	<atom:link href="http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/feed/" rel="self" type="application/rss+xml" />
	<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 02 Mar 2011 12:56:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: bifold doors</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-46161</link>
		<dc:creator>bifold doors</dc:creator>
		<pubDate>Sat, 24 Oct 2009 13:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-46161</guid>
		<description>Great post the older and newer way makes the flow easier.</description>
		<content:encoded><![CDATA[<p>Great post the older and newer way makes the flow easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jOHNSON</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-38460</link>
		<dc:creator>jOHNSON</dc:creator>
		<pubDate>Wed, 04 Mar 2009 06:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-38460</guid>
		<description>@Brian Smith - its very necessary thing as per user perspective and also content spreading. if you add it then user can lead to another section of your media.</description>
		<content:encoded><![CDATA[<p>@Brian Smith &#8211; its very necessary thing as per user perspective and also content spreading. if you add it then user can lead to another section of your media.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Smith</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-23104</link>
		<dc:creator>Brian Smith</dc:creator>
		<pubDate>Wed, 11 Jun 2008 04:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-23104</guid>
		<description>Why put next/previous or older/newer links on individual entry pages at all?</description>
		<content:encoded><![CDATA[<p>Why put next/previous or older/newer links on individual entry pages at all?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Fluther Blog &#187; Blog Archive &#187; &#8220;How&#8217;d they do that?&#8221; Pagination</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-19590</link>
		<dc:creator>The Fluther Blog &#187; Blog Archive &#187; &#8220;How&#8217;d they do that?&#8221; Pagination</dc:creator>
		<pubDate>Fri, 11 Apr 2008 16:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-19590</guid>
		<description>[...] First we had to decide how it should look, and which side would be for &#8220;Newer&#8221; and &#8220;Older&#8221;. This was surprisingly non-obvious. We thought carefully about our UI, discussed this great article by Ephram Zerb, and came up with something we liked. [...]</description>
		<content:encoded><![CDATA[<p>[...] First we had to decide how it should look, and which side would be for &#8220;Newer&#8221; and &#8220;Older&#8221;. This was surprisingly non-obvious. We thought carefully about our UI, discussed this great article by Ephram Zerb, and came up with something we liked. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-11423</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Wed, 19 Dec 2007 08:17:39 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-11423</guid>
		<description>I wrote &lt;a href=&quot;http://justinsomnia.org/2007/12/restoring-the-reverse-chronology/&quot; rel=&quot;nofollow&quot;&gt;Restoring the reverse chronology&lt;/a&gt; with you in mind. You&#039;ll see that I settled on &quot;Older/Newer Posts&quot; for the reverse chronological (i.e. homepage) navigation, and &quot;Next/Previous&quot; for permalink page navigation. 

Because my titles can grow long (and it bothers me polluting Google with post titles on adjacent posts) I opted to just use the words Next and Previous as the link text, which have the added benefit of being a constant width if you&#039;re surfing my archives. This of course is more meaningful if your posts are shorter and the next/prev links are positioned &quot;above the fold&quot;.

I notice that your homepage actually displays all your posts, so I&#039;m curious how you&#039;ll implement this in that context.</description>
		<content:encoded><![CDATA[<p>I wrote <a href="http://justinsomnia.org/2007/12/restoring-the-reverse-chronology/" rel="nofollow">Restoring the reverse chronology</a> with you in mind. You&#8217;ll see that I settled on &#8220;Older/Newer Posts&#8221; for the reverse chronological (i.e. homepage) navigation, and &#8220;Next/Previous&#8221; for permalink page navigation. </p>
<p>Because my titles can grow long (and it bothers me polluting Google with post titles on adjacent posts) I opted to just use the words Next and Previous as the link text, which have the added benefit of being a constant width if you&#8217;re surfing my archives. This of course is more meaningful if your posts are shorter and the next/prev links are positioned &#8220;above the fold&#8221;.</p>
<p>I notice that your homepage actually displays all your posts, so I&#8217;m curious how you&#8217;ll implement this in that context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Hsu</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-3711</link>
		<dc:creator>Joseph Hsu</dc:creator>
		<pubDate>Tue, 14 Aug 2007 16:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-3711</guid>
		<description>While browsing through blogs I have noticed this too. I become reluctant to click either because i&#039;m not sure which direction I am going.
Thanks for sharing!</description>
		<content:encoded><![CDATA[<p>While browsing through blogs I have noticed this too. I become reluctant to click either because i&#8217;m not sure which direction I am going.<br />
Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Artem</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-3286</link>
		<dc:creator>Artem</dc:creator>
		<pubDate>Fri, 03 Aug 2007 18:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-3286</guid>
		<description>The older and newer way is more clear to me since I jump around blogs a lot nad each one is different. Older and Newer makes the flow easier to understand. Having one long page also is not a bad idea but after many months of posts it get&#039;s long and finding specific posts becomes difficult. You should post more often!</description>
		<content:encoded><![CDATA[<p>The older and newer way is more clear to me since I jump around blogs a lot nad each one is different. Older and Newer makes the flow easier to understand. Having one long page also is not a bad idea but after many months of posts it get&#8217;s long and finding specific posts becomes difficult. You should post more often!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramesh</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-2821</link>
		<dc:creator>Ramesh</dc:creator>
		<pubDate>Tue, 17 Jul 2007 06:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-2821</guid>
		<description>Can you pls let me know how to get the actual titles of prev and next posts instead of the &quot;Older post&quot; and &quot;Newer post&quot; defaults which blogger gives?</description>
		<content:encoded><![CDATA[<p>Can you pls let me know how to get the actual titles of prev and next posts instead of the &#8220;Older post&#8221; and &#8220;Newer post&#8221; defaults which blogger gives?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Nicol</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-1956</link>
		<dc:creator>Jonathan Nicol</dc:creator>
		<pubDate>Sat, 23 Jun 2007 22:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-1956</guid>
		<description>I think the solution you have opted for gives the best of both worlds, and leaves little room for misinterpretation. I confess that without checking I was unsure which approach I used on my own blog, but a quick check confirmed that when browsing article abstracts (ie: on the homepage) I am using previous/next, and when reading a full post I have done away with any sort of forward/back navigation altogether (an option you hadn&#039;t considered!). I couldn&#039;t agree more that older/newer is more descriptive than previous/next, and in due course I will amend the wording of the links on my blog.</description>
		<content:encoded><![CDATA[<p>I think the solution you have opted for gives the best of both worlds, and leaves little room for misinterpretation. I confess that without checking I was unsure which approach I used on my own blog, but a quick check confirmed that when browsing article abstracts (ie: on the homepage) I am using previous/next, and when reading a full post I have done away with any sort of forward/back navigation altogether (an option you hadn&#8217;t considered!). I couldn&#8217;t agree more that older/newer is more descriptive than previous/next, and in due course I will amend the wording of the links on my blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephram Zerb</title>
		<link>http://kanevski.org/2007/06/ditching-next-and-previous-for-blog-navigation/comment-page-1/#comment-1923</link>
		<dc:creator>Ephram Zerb</dc:creator>
		<pubDate>Sat, 23 Jun 2007 05:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/06/ditching-next-and-previous-for-blog-navigation/#comment-1923</guid>
		<description>Matt, thanks for the background info.  I have yet to really delve into navigating accross multiple pages, but undoubtedly &quot;older&quot; and &quot;newer&quot; will serve as a starting point for that design decision.</description>
		<content:encoded><![CDATA[<p>Matt, thanks for the background info.  I have yet to really delve into navigating accross multiple pages, but undoubtedly &#8220;older&#8221; and &#8220;newer&#8221; will serve as a starting point for that design decision.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

