This attitude is merely eccentric, except in cases like the current controversy about Auto Pagination.
I have chosen to display 12 posts, because mine is a listing of twelve exact posts which i update daily. I now have only nine of the posts showing regardless of how many - 12 or 50 or 500 - that I preset to display. I need them all to show, because I daily print out this entire list in an MS Word booklet format - and without having the entire blog display, I can no longer do this.This is merely one example of the bloggers who are having trouble accepting the reality of Auto Pagination, and the consequently segmented archives, labels, and / or main page displays.
Let's look at how web sites are setup, for background.
The smallest unit of content in a web site is a page. Pages are structured hierarchically, where the main page indexes child pages, and the various child pages index other child pages. Each page in a web site is built statically - both content and links never change.
In the above example, the blogger wishes to display the 12 posts as one static page. Now, let's look at how blogs are setup.
The smallest unit of content in a blog is a post. Pages are structured based upon relationships of the various posts, on the pages, to each other. Each page in a blog is built dynamically, and is based upon the relationship of the posts being displayed in the page. Both content and links are dynamic, and change as the nature of the retrieval changes.
Posts are associated with other posts by date, and by subject. Posts associated by date are displayed in archive / main page retrievals, and posts associated by subject are displayed in label retrievals. Even when displayed by date or by subject, specific posts may or may not be displayed on the same physical page. Displays are segmented, and various posts are displayed on different pages, when the amount of physical information in a given retrieval exceeds a given size.
This post, Auto Pagination And The Difference Between Blogs And Static Web Sites, may be part of a dynamic retrieval for Archive: March 2010, for a Label such as Auto Pagination, or Blogger, or maybe New Blogger Experiences, or - well, it was for a while - as part of the main page.
As I published a few more posts, this post dropped off the main page. That's a dynamic main page - you showcase your most current posts, archive your older posts, and keep the main page brief and clean. All of your posts are indexed, and can be found by your readers, using any index, or hyper text links, such as links in this post.
That's how blogs work best.
- Brief and clean main page display.
- Dynamic retrieval of all posts, as relevant and needed.
- Showcasing of new posts.
Auto Pagination moderates peak resource use, caused by excessively large archive, label, and main page displays. When appropriate, Auto Pagination segments large displays, and simply requires the blog reader to use the "Newer Posts" / "Older Posts" links to move between display segments. As implemented a month ago, it's been quite effective.
There are several issues, which are causing some confusion and ill will.
- Blogs with classic templates
can't use "Newer Posts" / "Older Posts" links(This issue was resolved on 2010/04/12).
- Some blogs appear smaller than actual page size, because the posts use "Read More" code which reduces visual page size, yet does not reduce content downloaded to the client computer.
- Some blogs appear smaller than actual page size, because the posts contain meta code created by MS Word.
- Search engine indexing of posts won't be consistent. Not all post content will be indexed, because of segmentation. Some posts that are indexed may be present on segmented pages, which will cause SERP entries that lead to non visible content.
Besides these issues, the bloggers who design their blogs with static displays may need to rethink their actual needs. Some bloggers may be happier hosting their web sites with services outside Blogger - services that display content as static web site pages, instead of dynamic blog pages.