Agreed!<\/p>\n
People read from one line to the next. If you can’t read the line above the line you’re reading, it feels odd, and you can lose track of the narrative. When you’re reading a book, it’s almost instantaneous to flip a page, but with a website, the time taken to click on the “next” link and wait for the page to reload is much longer. What’s more, all that finding the link and clicking takes you out of the narrative — and, of course, makes it much more likely that you’ll disappear off somewhere else entirely, just like newspaper readers generally fail to read beyond the jump.
\nThe multiple-pages problem is so annoying, indeed, that many bloggers, including myself, make it a point to always link to a “single-page format” or “print version” of the article instead. That’s not always possible, however, and what’s more the print version often lacks important navigation, multimedia, and other hypertext components.
\nMost annoying, for a blogger, is when you’re quoting a bit of an article which is on, say, page three. Do you link to page three, or to page one? Neither is particularly pleasant.
\nEvery time I go to a website like the NYT or The Big Money, the need to hunt around for the “single page” button and click on it and wait for the page to reload makes me hate the site just a tiny bit. For really gruesome offenders like Time, I simply don’t read a lot of their listicles, no matter how good they are, because the multiple-page format makes them all but unreadable. Now that the need to maximize inventory has disappeared, maybe this whole annoying thing will go away.
\nHow the Ad Recession Could Improve the Web – Finance Blog – Felix Salmon – Market Movers – Portfolio.com<\/a>.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"Agreed! People read from one line to the next. If you can’t read the line above the line you’re reading, it feels odd, and you can lose track of the narrative. When you’re reading a book, it’s almost instantaneous to flip a page, but with a website, the time taken to click on the “next” … <\/p>\n