NO. Keep the article to one page but move the comments to a second page.
Or just make a two part article, released on different days.
Jaz - 12 years ago
On my train commute I get sporadic 3g coverage. Preferable to load long pages I can spend time scrolling down through.
James W - 12 years ago
For pages with a lot of content, rather wait until a user scrolls to the bottom of the first part of content, then load the rest underneath. This is the same as a twitter feed where more load as you scroll. I often avoid any article that is split up into many pages.
I actually get quite annoyed by articles which make me go to page 2. If you do, please provide an option for reading the entire article on a single page :)
kvd - 12 years ago
We're developpers. We like looooooooooooooooooong pages
Liam - 12 years ago
It takes less than a micro second to move my index finger to scroll. So why would you want to click "page 2" and wait 2-3 seconds before the page loads then have to scroll down to the article?
Nathan - 12 years ago
Translated: "Would you guys be really annoyed if we increased our ad impressions and page views at the sacrifice of readability, convenience and your sanity?"
Multiple pages for an article ABSOLUTELY annoy me! The only benefit (for the site owner) are the increased pageviews. For the user there are none.
tp - 12 years ago
with 1 long page i can push it with 1 click to my eBook reader
Mark Jones - 12 years ago
The only benefit of breaking an article into multiple pages is the ability to bookmark a specific point within the article... but that doesn't really compensate for the annoyance of HAVING multiple pages for a single "piece" of content.
In my opinion; it all depends on how long the article is. If I gotta read like 100 meters down the screen, yeah; then I think separating the article into smaller chunks would be a good idèa.
However, I also think it depends on the website layout.
OkkE29 - 12 years ago
Scrolling is way faster/easier/better than clicking back and forth between 2 pages.
Jesse - 12 years ago
I hate reloading a page more than scrolling down a page.
I can't stress how much I hate paginated articles, often I associate them with cheap websites trying to ramp up ad impressions rather than improve readability.
It's very easy that there's only one page article postings on your blog. Page 2 is very irritating.
Suppose, we are in a later portion of an article, let's say that's on page 2, then if in middle we had to refer to some link/ text/ reference mentioned earlier in the article, we would need to go back to page 1 and see - very inconvenient.
No, cos if you're referencing previous parts of the article, you'll have to click back and forth, rather than scrolling up or down, which in that sense is easier
NO. Keep the article to one page but move the comments to a second page.
Or just make a two part article, released on different days.
On my train commute I get sporadic 3g coverage. Preferable to load long pages I can spend time scrolling down through.
For pages with a lot of content, rather wait until a user scrolls to the bottom of the first part of content, then load the rest underneath. This is the same as a twitter feed where more load as you scroll. I often avoid any article that is split up into many pages.
I actually get quite annoyed by articles which make me go to page 2. If you do, please provide an option for reading the entire article on a single page :)
We're developpers. We like looooooooooooooooooong pages
It takes less than a micro second to move my index finger to scroll. So why would you want to click "page 2" and wait 2-3 seconds before the page loads then have to scroll down to the article?
Translated: "Would you guys be really annoyed if we increased our ad impressions and page views at the sacrifice of readability, convenience and your sanity?"
At least you asked!
Multiple pages for an article ABSOLUTELY annoy me! The only benefit (for the site owner) are the increased pageviews. For the user there are none.
with 1 long page i can push it with 1 click to my eBook reader
The only benefit of breaking an article into multiple pages is the ability to bookmark a specific point within the article... but that doesn't really compensate for the annoyance of HAVING multiple pages for a single "piece" of content.
1 page is best, scrolling is no problem and you can easily find what you're looking for (cmd+f)
In my opinion; it all depends on how long the article is. If I gotta read like 100 meters down the screen, yeah; then I think separating the article into smaller chunks would be a good idèa.
However, I also think it depends on the website layout.
Scrolling is way faster/easier/better than clicking back and forth between 2 pages.
I hate reloading a page more than scrolling down a page.
Scrolling makes long articles easy to read.
I can't stress how much I hate paginated articles, often I associate them with cheap websites trying to ramp up ad impressions rather than improve readability.
J.
It's very easy that there's only one page article postings on your blog. Page 2 is very irritating.
Suppose, we are in a later portion of an article, let's say that's on page 2, then if in middle we had to refer to some link/ text/ reference mentioned earlier in the article, we would need to go back to page 1 and see - very inconvenient.
Regards,
No, cos if you're referencing previous parts of the article, you'll have to click back and forth, rather than scrolling up or down, which in that sense is easier