<?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: IA for beginners: long pages work.</title>
	<atom:link href="http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work/feed" rel="self" type="application/rss+xml" />
	<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work</link>
	<description>Peter Van Dijck's weblog</description>
	<pubDate>Sun, 08 Nov 2009 11:28:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kathleen</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140764</link>
		<dc:creator>Kathleen</dc:creator>
		<pubDate>Thu, 06 Sep 2007 14:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140764</guid>
		<description>I've been told over and over that long pages don't work. Notoriously recalcitrant, I persist in publishing them, often arcane, technical or dense material.

20-25% of my 5,000+ daily visitors spend an hour or more on site. The average visit is over 6 minutes.
'nuff said.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been told over and over that long pages don&#8217;t work. Notoriously recalcitrant, I persist in publishing them, often arcane, technical or dense material.</p>
<p>20-25% of my 5,000+ daily visitors spend an hour or more on site. The average visit is over 6 minutes.<br />
&#8217;nuff said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Nemeth</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140689</link>
		<dc:creator>Adam Nemeth</dc:creator>
		<pubDate>Fri, 31 Aug 2007 16:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140689</guid>
		<description>Well, it depends. As for data, yes. But reading a long _story_ 20 pages long just makes the reader tired. Web is a fast medium. No matter how long your page is, they'll spend as much time as they think it's worth for your content. Not a second more.

So, long pages probably work, but concise composition is still unevitable and necessary for good web experience.</description>
		<content:encoded><![CDATA[<p>Well, it depends. As for data, yes. But reading a long _story_ 20 pages long just makes the reader tired. Web is a fast medium. No matter how long your page is, they&#8217;ll spend as much time as they think it&#8217;s worth for your content. Not a second more.</p>
<p>So, long pages probably work, but concise composition is still unevitable and necessary for good web experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt K</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140688</link>
		<dc:creator>Matt K</dc:creator>
		<pubDate>Fri, 31 Aug 2007 14:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140688</guid>
		<description>We're talking about articles and other information content, right?  The work done to date on this topic indicates that the answer very much depends.  If your visitors are looking to do some reading and have found their way to some good content then the answer is probably yes - the long page works, but only if it's well written and clearly structured.  

Good navigation, visual structure, and content make or break it.  I've been involved in user research where the participant says "I don't like scrolling" but what they really mean is that they don't like struggling because the information sucks and the page is impossible to scan.

If we're talking about something like a home page the same principles apply, but you better believe the stuff on the top is going to get clicked through first - especially when the navigation is poor and nothing stands out.  They'll click the stuff on the top first and if you're lucky they'll come back. 

There are lots of good articles on this topic - read more than one and form your own ideas - then watch someone try to use your app/product.
Some additional reading:
&lt;a href="http://www.uie.com/brainsparks/2006/12/26/408/" rel="nofollow"&gt;http://www.uie.com/brainsparks/2006/12/26/408/&lt;/a&gt;&lt;a href="http://psychology.wichita.edu/surl/usabilitynews/41/paging.htm" rel="nofollow"&gt;http://psychology.wichita.edu/surl/usabilitynews/41/paging.htm&lt;/a&gt;&lt;a href="http://www.usabilitynews.com/news/article4104.asp" rel="nofollow"&gt;http://www.usabilitynews.com/news/article4104.asp&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>We&#8217;re talking about articles and other information content, right?  The work done to date on this topic indicates that the answer very much depends.  If your visitors are looking to do some reading and have found their way to some good content then the answer is probably yes - the long page works, but only if it&#8217;s well written and clearly structured.  </p>
<p>Good navigation, visual structure, and content make or break it.  I&#8217;ve been involved in user research where the participant says &#8220;I don&#8217;t like scrolling&#8221; but what they really mean is that they don&#8217;t like struggling because the information sucks and the page is impossible to scan.</p>
<p>If we&#8217;re talking about something like a home page the same principles apply, but you better believe the stuff on the top is going to get clicked through first - especially when the navigation is poor and nothing stands out.  They&#8217;ll click the stuff on the top first and if you&#8217;re lucky they&#8217;ll come back. </p>
<p>There are lots of good articles on this topic - read more than one and form your own ideas - then watch someone try to use your app/product.<br />
Some additional reading:<br />
<a href="http://www.uie.com/brainsparks/2006/12/26/408/" rel="nofollow">http://www.uie.com/brainsparks/2006/12/26/408/</a><a href="http://psychology.wichita.edu/surl/usabilitynews/41/paging.htm" rel="nofollow">http://psychology.wichita.edu/surl/usabilitynews/41/paging.htm</a><a href="http://www.usabilitynews.com/news/article4104.asp" rel="nofollow">http://www.usabilitynews.com/news/article4104.asp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien Couvreur</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140681</link>
		<dc:creator>Julien Couvreur</dc:creator>
		<pubDate>Thu, 30 Aug 2007 16:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140681</guid>
		<description>I also disapprove of articles that are broken over multiple pages for no good reason. 
The good news is that can be fixed: you can write Greasemonkey scripts for the sites that you care about, which loads the next pages, extracts the body and injects it into the first page.
I've done that for a couple of sites (IGN, ArsTechnica, ACMQueue) and more are available on http://userscripts.org.</description>
		<content:encoded><![CDATA[<p>I also disapprove of articles that are broken over multiple pages for no good reason.<br />
The good news is that can be fixed: you can write Greasemonkey scripts for the sites that you care about, which loads the next pages, extracts the body and injects it into the first page.<br />
I&#8217;ve done that for a couple of sites (IGN, ArsTechnica, ACMQueue) and more are available on <a href="http://userscripts.org" rel="nofollow">http://userscripts.org</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maetl</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140680</link>
		<dc:creator>maetl</dc:creator>
		<pubDate>Thu, 30 Aug 2007 14:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140680</guid>
		<description>It also works better with keyboard scrolling - pgdn or apple+arrow keys jumps directly to the foot of a longer page without needing to scroll, which is much more effective than clicking and loading. Enabling such long pages was the whole purpose of the #fragment identifier in URLs, so this stuff goes right back to the original design of the web.</description>
		<content:encoded><![CDATA[<p>It also works better with keyboard scrolling - pgdn or apple+arrow keys jumps directly to the foot of a longer page without needing to scroll, which is much more effective than clicking and loading. Enabling such long pages was the whole purpose of the #fragment identifier in URLs, so this stuff goes right back to the original design of the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor Lombardi</title>
		<link>http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140679</link>
		<dc:creator>Victor Lombardi</dc:creator>
		<pubDate>Thu, 30 Aug 2007 12:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://poorbuthappy.com/ease/archives/2007/08/30/3804/ia-for-beginners-long-pages-work#comment-140679</guid>
		<description>Amen, brother. Until navigation is faster than visually scanning, putting everything in front of the eyes is better.</description>
		<content:encoded><![CDATA[<p>Amen, brother. Until navigation is faster than visually scanning, putting everything in front of the eyes is better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
