<?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: Pagination: Common Problems</title>
	<atom:link href="http://blog.twigkit.com/pagination-common-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.twigkit.com/pagination-common-problems/</link>
	<description>A blog about search, user experience, and development.</description>
	<lastBuildDate>Mon, 10 May 2010 12:14:33 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sjors</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-18</link>
		<dc:creator>Sjors</dc:creator>
		<pubDate>Mon, 14 Dec 2009 16:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-18</guid>
		<description>just came across this post, also a nice attribution</description>
		<content:encoded><![CDATA[<p>just came across this post, also a nice attribution</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nano-cart</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-17</link>
		<dc:creator>nano-cart</dc:creator>
		<pubDate>Mon, 14 Dec 2009 14:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-17</guid>
		<description>Tyler,
Great write up.. ! I cannot say how many times I&#039;ve ranted (ok, more like a heckling-vent) when it comes to the pagination encounter on a day to day basis. For the life of me, I cannot see why ANYONE would not provide the &#039;prev&#039; and &#039;next&#039; links, and make them prominent while they&#039;re at it. We&#039;re not talking an &#039;alpha&#039; bar where you may know which alphabetical letter you wish to review,.. so, the most common use of pagination is going to be &#039;next&#039; or &#039;prev&#039;. If the user wants to find a specific page that&#039;s more the job of the searching/filtering/sorting functionality of the app, and shouldn&#039;t be put off on the pagination to handle. 

All in all, I think you put it well when you stated,. &quot;pagination .... helping users move from highly relevant results to less relevant results in a proper progression&quot;.

It&#039;s great to see a thoughtful write up on the main issues with how pagination is implemented.. now, we&#039;ve just got to get those lazy coders/designers who think pagination is a search feature, over to this article :D  - Great work !

** I know I tweeted you to let you know (and thanks for popping by the temp page to have a look),.. but our new &#039;light-commerce&#039; engine is using your 1kb grid throughout and it&#039;s almost ready for the lime light.. thanks again for the slick work on the CSS grid.. it&#039;s really handy! **</description>
		<content:encoded><![CDATA[<p>Tyler,<br />
Great write up.. ! I cannot say how many times I&#8217;ve ranted (ok, more like a heckling-vent) when it comes to the pagination encounter on a day to day basis. For the life of me, I cannot see why ANYONE would not provide the &#8216;prev&#8217; and &#8216;next&#8217; links, and make them prominent while they&#8217;re at it. We&#8217;re not talking an &#8216;alpha&#8217; bar where you may know which alphabetical letter you wish to review,.. so, the most common use of pagination is going to be &#8216;next&#8217; or &#8216;prev&#8217;. If the user wants to find a specific page that&#8217;s more the job of the searching/filtering/sorting functionality of the app, and shouldn&#8217;t be put off on the pagination to handle. </p>
<p>All in all, I think you put it well when you stated,. &#8220;pagination &#8230;. helping users move from highly relevant results to less relevant results in a proper progression&#8221;.</p>
<p>It&#8217;s great to see a thoughtful write up on the main issues with how pagination is implemented.. now, we&#8217;ve just got to get those lazy coders/designers who think pagination is a search feature, over to this article :D  &#8211; Great work !</p>
<p>** I know I tweeted you to let you know (and thanks for popping by the temp page to have a look),.. but our new &#8216;light-commerce&#8217; engine is using your 1kb grid throughout and it&#8217;s almost ready for the lime light.. thanks again for the slick work on the CSS grid.. it&#8217;s really handy! **</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler Tate</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-15</link>
		<dc:creator>Tyler Tate</dc:creator>
		<pubDate>Mon, 14 Dec 2009 10:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-15</guid>
		<description>Those are two excellent examples of good v. bad pagination. Thanks Andy!</description>
		<content:encoded><![CDATA[<p>Those are two excellent examples of good v. bad pagination. Thanks Andy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Shaw</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-14</link>
		<dc:creator>Andy Shaw</dc:creator>
		<pubDate>Mon, 14 Dec 2009 10:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-14</guid>
		<description>Pagination at the top of listings is just silly, worse still when its only at the top.

If you have been to Kanye West&#039;s blog (yes I&#039;m a fan), you will see the &quot;next&quot; link has been replaced by a &quot;last&quot; link?! Which I&#039;ve mistakenly clicked more than once before. http://www.kanyeuniversecity.com/blog 

One of my favourite examples of pagination (how geeky does that sound) is at http://minimalissimo.com/page/2/ I love the simplicity of it, yet it keeps all of the relevant functionality.</description>
		<content:encoded><![CDATA[<p>Pagination at the top of listings is just silly, worse still when its only at the top.</p>
<p>If you have been to Kanye West&#8217;s blog (yes I&#8217;m a fan), you will see the &#8220;next&#8221; link has been replaced by a &#8220;last&#8221; link?! Which I&#8217;ve mistakenly clicked more than once before. <a href="http://www.kanyeuniversecity.com/blog" rel="nofollow">http://www.kanyeuniversecity.com/blog</a> </p>
<p>One of my favourite examples of pagination (how geeky does that sound) is at <a href="http://minimalissimo.com/page/2/" rel="nofollow">http://minimalissimo.com/page/2/</a> I love the simplicity of it, yet it keeps all of the relevant functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler Tate</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-12</link>
		<dc:creator>Tyler Tate</dc:creator>
		<pubDate>Mon, 14 Dec 2009 09:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-12</guid>
		<description>I haven&#039;t done tracking myself, but you brought up an excellent point. This type of thing could be easily measured. In addition to your predictions, I would guess that pagination at the bottom of the page would receive more clicks than pagination at the top of the page, and that the link to the last page of results would get hardly any clicks. Good thought!</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t done tracking myself, but you brought up an excellent point. This type of thing could be easily measured. In addition to your predictions, I would guess that pagination at the bottom of the page would receive more clicks than pagination at the top of the page, and that the link to the last page of results would get hardly any clicks. Good thought!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sjors</title>
		<link>http://blog.twigkit.com/pagination-common-problems/comment-page-1/#comment-11</link>
		<dc:creator>Sjors</dc:creator>
		<pubDate>Mon, 14 Dec 2009 09:45:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=22#comment-11</guid>
		<description>Nice article, do you have some tracking set up? My best guess is that next get&#039;s the most clicks, 2 will be second and previous will get the lowest amount of clicks. Would be interested how this turns out in reality</description>
		<content:encoded><![CDATA[<p>Nice article, do you have some tracking set up? My best guess is that next get&#8217;s the most clicks, 2 will be second and previous will get the lowest amount of clicks. Would be interested how this turns out in reality</p>
]]></content:encoded>
	</item>
</channel>
</rss>
