Reader Zoom Level Affects Screen Space Needed

I have suggested that properly sizing the Jump Break and Title sections of each post is an important decision, when publishing a post in your blog.

Publishing this blog, using carefully sized post title and jump break sections, allows me to consistently publish posts, with maximum detail visible in main page view - and with the "Read more" link visible.

Potential readers may read a post in this blog - instead of returning to a SERP, and reading another blog. This affects a key reader retention metric, the "bounce rate".

All of that considered, sizing of the introductory post sections won't always produce predictable results.

Reader zoom level is a semi random factor, which makes blog section sizing less predictable than one would wish, when trying to increase reader retention.

I size my posts using "100%" zoom, in the Chrome browser. This may, or may not, produce the same effect, for readers using Edge / Internet Explorer, Firefox, or any other browser. And the differing browser will not be the only varying factor.

All of these details can affect zoom level, screen space requirements, and reader retention - for any different blog. Here it is helpful for the blog owner to know about the typical reader.

• Display screen size.
• Reader age.
• Multi tasking activity.
• Tech interest level.

Display screen size will affect how the blog sections look, to each reader.

Browser choice is not the only variation, that can affect screen space and blog section display sizes.

Reader display screen size used is a detail, that I cannot control. The computer on which I compose most posts has a 6" high screen. A second computer, that I use from time to time, has an 8" high screen. The second computer, even at a 125% zoom level, still displays more post content in one screen page.

This post (in main page view) displayed, at 100% zoom, on an 6" vertical display.



Let's compare this post, displayed at several zoom levels.

Here's this post, in the individual post page display - without Jump Break. See how it looks, zoomed in various font sizes. Note that here I use a maximised browser window, though some readers will resize the browser window to fit the blog content.

This post (in Preview mode) displayed, at 100% zoom, on an 6" vertical display.

This post (in Preview mode) displayed, at 100% zoom, on an 10" vertical display.

This post (in Preview mode) displayed, at 75% zoom level.



Smaller zoom is more likely to be used by people with better eyesight - using better resolution and more expensive computers, and smaller browser windows.

This post (in Preview mode) displayed, at 125% zoom level.



Larger zoom is more likely to be used by people with marginally worse eyesight. This will frequently involve older people.

Older readers will be more likely to use higher zoom levels.

Reader age is another detail which each blog author may consider, in blog design.

Blogs which attract older readers should be designed for displays which use higher zoom levels - or use larger fonts, to begin. Older readers, with marginal eyesight, will be more likely to surf the web with their browsers zoomed higher.

Multi tasking encourages smaller browser windows - and lower zoom levels.

Younger readers, who like to multi task, will probably use low zoom - and size the browser window smaller, so they can have multiple windows, simultaneously visible in large computer displays. Older readers will be more likely to focus on one task at a time - and will maximise the browser window, with higher zoom.

Blog subject may produce readers of differing age and tech interest.

Each blog, depending upon its content, may be more or less likely to interest readers of a given age and / or and tech interest level. People of different tech interest levels may also be more or less likely to use computers with higher resolution, and may multi task using smaller browser windows.

The bottom line.

Each blog owner will have to consider the various issues mentioned above - for each post published - and decide what screen sizes and zoom levels might be preferred by the target reader audience.

Only a blog owner can decide what reader audience may be more interested in each individual post - and may benefit from a specific zoom level. And this affects the proper sizing of the jump break and title section of each post.

---

Several details of a #Blogger blog audience affect what post title and jump break section will be more appropriate, for each individual blog. These details, in turn, can affect bounce rate / retention rate.

You Cannot Fit Your Entire Blog Onto The Main Page

Some blog owners would like their readers to view the entire blog in one page.

A small blog, with very limited size, can theoretically fit on one page. If you intend to publish a blog with any future, and page rank, you will have to publish content periodically - and the size of the blog will increase, steadily.

And eventually, thanks in part to main page limitation by auto pagination, older posts in your blog will be forced into archive pages.

For a blog with any future, and publishing activity, there are four possibilities for main page size.

• Segment main page, limiting post count.
• Segment your blog, using virtual blogs.
• Use a dynamic template, and "continuous scrolling".
• Use a non dynamic template, and Jump Break - and accept archiving.

Segment main page, limiting post count.

One of the simplest ways to make your blog reader friendly is to limit main page size, using a post count limit. This won't work as a final solution, however, if you're planning to publish the blog with any regularity.

Segment your blog, using virtual blogs.

If you can break your blog into multiple subjects, you can use a Pages tabbed index to access each different subject. You can fit each different subject, possibly using Jump Break, onto one page.

To complement the virtual blogs, you can have a static main page - providing a "welcome" message, and / or indexing the virtual blogs.

Use a dynamic template, and "continuous scrolling".

For public blogs, a dynamic template, with continuous scrolling, may provide a solution. Dynamic templates, unless you a very comfortable with editing the blog template, will never offer the accessory and customisation possibilities of non dynamic templates, however.

With a dynamic template, you won't be able to use Jump Break - though some dynamic views may provide a summarised main page view.

Use a non dynamic template, and Jump Break - and accept archiving.

Careful use of Jump Break will let you limit the size of the main page. If you continue to publish posts - which is necessary for a blog with any future - you will eventually have posts displayed on archive pages.

For best results, design the blog structure - and the posts structure - consistently, and accept archiving and pagination.

---

Some #Blogger blog owners would like to display all post content in one page - and ignore page display size. They do not realise that not all blog readers want to read a blog with an unlimited page size, all at once.

An Expanding Reader Community May Make Your Blog Vulnerable To A Content Warning

Occasionally, we see a report in Blogger Help Forum: Get Help with an Issue, that reflects on the reader audience - not necessarily only the blog content.

Why is my blog behind a Content Warning?

Some readers of this blog have contacted Google because they believe this blog's content is objectionable.

Occasionally, a quick eyeballing of the blog in question may turn up some dodgy content, which may be suggested, in the forum, as problematic.

This story may not end immediately.

But, I've had that picture gallery, for years! Why did I just get the Content Warning?

Here, the blog owner is not considering changing standards - or the possibility that the blog, becoming more popular, may be adding readers who don't appreciate a photo gallery started years ago.

As your blog matures - and when you are successful at encouraging reader and search engine reputation - your reader audience should be increasing.

If your reader population expands, some readers may be less tolerant.

If you are now advertising your blog to a more selective audience, some folks in that audience may object to some blog content, enjoyed or ignored by your earlier audience.

If you spend time perusing your visitor logs - and if you have a more robust visitor log than Stats, you may find some interesting clues. StatCounter (not SiteMeter) shows, among other details, the "Exit Click" for each visitor. If you see any one post abnormally represented, among the "Exit Click" inventory, you may be looking at content that's possibly not appreciated by some portion of the reader community.

Here, I'll note that you won't necessarily see any statistics for a post that is posted entirely on the main page. If your main page is a significant portion of the blog, you may wish to add Jump Break to your posts, to encourage your readers to click to the individual post pages, and read each individual post.

Be aware of your reader population - and consider their needs.

Whatever your strategy for advertising your blog, be aware of changing visitor interest. Don't "spice up" your blog with "eye candy", and expect to remain free of a Content Warning, forever.

Encourage your readers, with informative, interesting, and unique content. Don't abuse them with eye candy, then demand removal of the Content Warning, without compromise.

All "Read More" Solutions Are Not The Same

Auto pagination, and "Jump Break", have been a (controversial) feature in Blogger blogs since 2010.

Oddly enough, not all blog owners yet understand the difference between "Jump Break", and other "Read More" features. And there are more than a couple "Read More" features available, in the Internet - some not so beneficial.

Occasionally, we see the confusion, in Blogger Help Forum: Something Is Broken.

I have 12 articles which must appear on my homepage. Just 10 of the 12 articles are showing up. When I added 2 new articles, another old post disappeared from my homepage.

This blog owner, like many, suffers from the effects of auto pagination.

When I suggested using "Jump Break", to make the posts smaller, I was met with confusion.

Did you not look at the blog? I have "Read More" there, already.

And looking at the blog again, I saw that he was correct.

Examining main page view, and a post in the the blog, I used my browsers HTML viewer.

HTML view shows a post which uses "Read More" - but not "Jump Break". Examining various blogs main page view, as HTML, we can see the difference between "Jump Break", and this "Read More" solution.

With "Jump Break", on the main page, one sees the post summary, followed by a link to the post page. The post page then contains the full post.

With "Read More", on the main page, one simply sees the entire post. The JavaScript code (provided separately in the template) automatically displays the post summary, for each post, consisting of a certain amount of words, followed by a "Read More" button - and hides the remainder of the post, as displayed in main page view.

When clicked, the "Read More" code simply makes the entire post visible. This would be a clever way to display a post summary - if auto pagination was not involved.

Since auto pagination limits the number of posts based on total downloaded content, main page view, using "Read More", is limited by content which is not visible. This causes confusion.

With "Jump Break", each carefully sized post summary, in main page view, downloads only the post summary to the client computer. This makes each individual post relatively small - and allows the main page, even with auto pagination, to include a large number of posts.

Look at main page view for this blog. I display anywhere from 10 to 15 posts, at any time, in main page view. Long ago, you would see this post at the top of the page (but time has passed, and this post is archived). Do you see how small the posts are, as displayed on the main page?

With "Read More", however, even with the post displayed as a summary, the entire post is downloaded. Auto pagination then limits main page view to a handful of posts. Main page view looks smaller than it should - and the blog owner is left, scratching his head.

Only "Jump Break" works properly, with auto pagination. That is the bottom line. Don't settle for less than "Jump Break", if you want your blog, in main page view, to include a predictable number of posts.

Jump Break, Main Page Contents, And Search Engines

The articles in this blog, which discusses production and use of Blogger blogs, are written as posts.

The various posts are combined, using embedded links, in different ways. Each new post appears on the main page, as it is written - and the various posts, appearing together on the main page, create opportunities for confusion, with the readers of the blog.

Long ago, the task of moderating comments was rather depressing to me, as the focus of many of the comments made me think that nobody was actually reading the articles. Maybe, I would write an interesting post about URL availability; but when moderating comments, I would find questions about posting comments on static pages. Or maybe a post about dynamic template concepts would attract complaints about referer spam.

Why should I publish my advice, if nobody cares enough to read the articles and comment relevantly?

Just previous to this post, I wrote about Stats displays, and the contents of the Posts lists.

In the process of writing the latter article, I discovered one obscure benefit of using "Jump Break" - and how "Jump Break" affects main page view, search engine indexing, and finally, relevance of comments to post subject.

A home page, with a variety of posts, naturally produces un focused comments.

Why the apparent lack of focus, of the comments? One reason is that many different posts, published one after the other, appear in sequence, in the blogs main page.

People will read the posts - and the search engines will index the posts - using main page view. Only after newer posts force the older posts, one by one, from main page view, will the individual posts have any significance - to people or search engines.

Using my example above, and looking at my main page when this post was new, one would have found a post about URL availability, published a week after a post about posting comments on static pages. By the time the search engines indexed the latter post, I would have published the former post. The post about URL availability would be visible in main page view, ahead of the post about posting comments on static pages.

Clicking on the link to my blog, attached to a SERP entry referencing static pages, the reader will read my main page from the top, find the previously visible post about URL availability, and the Comments link following the post. Clicking on the first Comments link found, the reader will post his question about static pages, against my post about URL availability.

Use of Jump Break gives a home page that can be easily read, top to bottom.

So, what effect does the use of "Jump Break" have on this problem? Using "Jump Break" on all main page posts makes it more likely that a potential reader of the blog, following a home page link to the blog, has more chance to see all recent posts, with their summaries.

The reader is more likely to scan down the page, see a summarised relevant post, click on "Read more" - and read the relevant post, on the individual post page, before commenting.

Use of Jump Break gives more weight to the individual posts, as indexed.

Additionally, with the posts summarised in main page view, the search engines will find less content on the main page. The full posts will be indexed as individual post pages, more than as part of the main page. This gives more weight to the individual posts, and less weight to the main page.

When indexed using an automatically generated, robust sitemap (2014), the posts will appear individually in SERP lists, decreasing reader main page confusion. Each SERP entry, pointing to an individual post, will be more relevantly focused - giving it more weight than a SERP entry, pointing to main page view.

Use of Jump Break, consistently, produces a win-win-win scenario.

In summary, careful and consistent use of "Jump Break" leads to:

• Better focus on individual and relevant blog articles, by the search engines.
• Less confusion to the blogs readers, when accessing the blog using SERP hit lists.
• Less frustration for the blog owner, when moderating comments.

It's really a win-win-win, when used consistently. And, it's so simple to apply, on a post by post basis. Check it out, in action.

Stats Not Displaying Newer Posts, In "Posts" Lists

The problem of last week, with Stats, was fixed late yesterday, and our Stats displays once again are showing Posts pageview counts and enumerating individual Posts. Now, we have a perceived problem, being reported by newer blog owners.

My Stats display does not show my newer posts!

This concern is visually valid - but it's not real. It's most common with blogs that have just over 10 posts, which are owned by people who are not aware of the Stats display limitations, as we have explored.

The Stats Posts displays enumerate the 10 most popular posts, for any given time period. Newer posts will seldom appear in the Posts lists, for many blogs.

• The "Posts" lists enumerate individual posts, and shows pageview counts for posts viewed in single post view. Newer posts will be displayed in their entirety on the main page, and read as main page views.
• The lists show only the 10 most popular posts. Newer posts, not yet indexed by the search engines, or linked by your readers, won't have as many inlinks - and the post page URLs won't get as much traffic from other blogs and websites.

Owners of newer blogs will not be aware of these details - and with just over 10 posts, may not see the significance, in their Stats displays. These owners will simply see, from time to time, posts that don't appear in the lists.

If you look at the main page, for this blog, you'll see use of "Jump Break" in my newer posts. Each of these posts, to be read in their entirety, can only be read using the "Read more" link - and from the individual post page. Look at the address window above.

http://blogging.nitecruzr.net/2011/10/stats-not-displaying-newer-posts-in.html

Since you're viewing these words, this post is being counted in Posts, as a pageview. Thus the Posts lists, for this blog, will enumerate this post, sooner.

Here, we see another benefit of using "Jump Break" over other auto summarisation techniques. The "Jump Break" links directly to the single post view of each post - and it uses HTML, which makes it search engine friendly. Some previous auto summarisation techniques used JavaScript to hide the full post content, preventing search engines from indexing the full post text.

Besides encouraging the post content to be read as a post page, the search engines will index post content in the post pages. The archive retrievals, and main page, will only list the partial content of each post - and search engine hit lists will contain more relevant content.

>> Top

Making Jump Break Work For Blogs With Older Templates

The new Blogger solution for auto summarised posts, also known as "Read More" or "Jump Break", is becoming increasingly popular in Blogger blogs, for several reasons.

• Auto Pagination resulted in display segmentation, caused by the perceived need to publish hundreds of posts on the main page.
• Desire to display a dynamic index of posts as the main page.
• Desire to simply make the main page and / or archive retrieval displays smaller.

The "Jump Break" feature itself is reasonably easy to use, when you are using the New Post Editor, and with blogs that use a template released after Jump Break was released - apparently in September 2009. If your blog was created before then, you may need to add a critical bit of code to the post template.

The simplest way to add the necessary code would be to refresh the post template.

If you have customised your post template, this won't be a good idea. If you want to keep the current post template, and add the critical bit of code, you're going to have to edit the template HTML, and you're going to have to Expand Widget Templates when you edit the HTML.

Instruction from Blogger, in Creating 'After the jump' summaries is pretty simple

After backing up your template, then click the Expand Widget Templates checkbox, and scan your HTML for the following snippet:

<data:post.body/>

Once you've located that code, paste the following snippet directly below it:

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if >

After you've pasted in the code, click Save and then you're done!

It's possible that such simple instruction may be slightly misleading.

Here's the snippet in question, as seen in the template in my newest test blog, "Chuck's Jump Break Test", with surrounding code to provide a contextual reference.

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>  
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

If you read the above instructions literally, Blogger would have us take an older template

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Add the recommended snippet to produce

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

I suspect that the update may be much more correctly installed as

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"'><data:post.jumpText/></a>
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

Or possibly, you may even want the full, original snippet

<div class='post-header'>
<div class='post-header-line-1'/>
</div>

<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
</div>

<b:if cond='data:post.hasJumpLink'>
<div class='jump-link'>
<a expr:href='data:post.url + "#more"' expr:title='data:post.title'><data:post.jumpText/></a>
</div>
</b:if>

<div class='post-footer'>
<div class='post-footer-line post-footer-line-1'>
<span class='post-author vcard'>
<b:if cond='data:top.showAuthor'>
<data:top.authorLabel/>
<span class='fn'><data:post.author/></span>
</b:if>
</span>

So, what is "expr:title='data:post.title'"? Look at my demonstration, hover the mouse cursor over "Read more »", and see.

If you just added the Jump Break to your blog after following the instructions from Blogger, and you followed their instructions literally, you may be observing odd details. It's possible that reports of post / sidebar alignment problems, and odd problems with photos and jump break, may be related to this confusion. You may do well to modify their instructions, when you update your template.

>> Top

Auto Pagination And Read More Solutions

Possibly the hottest issue this week, in Blogger Help Forum: Something Is Broken, is the Auto Pagination feature, which was introduced last week. Auto Pagination automatically helps people to limit the sizes of their archive / label / main pages, as downloaded from Blogger servers.

Before the Blogger post editor "Jump Break" solution was provided, there were at least 3 known variants, for auto summarising posts. One was provided in Blogger Help: How can I create expandable post summaries?; and at least 2 others were provided as third party suggestions. It's possible that any of these 3 variants are present in some blogs, where the owner has not seen fit to remove them, in favour of deploying the "Jump Break" in new post editor.

Cloud Strife, in Blogger Help Forum: Problem Rollup: Auto Pagination for blogs with Layouts templates suggests an obvious solution - replacing use of all early "Read More" variants, with the new post editor "Jump Break".

The problem as I explained earlier is that with the older solution, the blog post still had all the content sent to the viewers' browser while just making the post look smaller by not showing all the content. This will solve the aesthetics problem but not the slow-ness problem. The perceived slowness differs much more to the person who has cached everything in the browser (mostly us who view our own blog) than those who view it first time or rarely.

The new feature which is as simple as adding an extra <!-- more --> in the HTML or rather simply using the new editor, keeps the look and feel as good and makes your website much faster to load. Which I am sure your readers will appreciate. And once the site loads faster for your viewers they are more likely to visit the pages you have there.

I'll add the advice that adding the "Jump Break" option to your posts will have to be done on a post by post basis, but the individual post update is fairly simple to do. And, taking the advice from Cloud Strife

with the older solution, the blog post still had all the content sent to the viewers' browser while just making the post look smaller by not showing all the content

it appears that not all "Read More" solutions actually reduce page size when loading.

The bottom line - if you replace the old "Read More" with the new "Jump Break", your readers will see a significantly faster main page download. Or, if you wish, you will be able to load more (abbreviated) posts total, and stay within Auto Pagination induced page sizes.

As Blogger continues to resolve the problems associated with Auto Pagination, its not a certainty that all 3 earlier used variants of "Read More" will continue to operate. If your blog uses an out of date "Read More" variant, and you're unable to replace it with the recommended "Jump Break", you might want to watch the display of your blog carefully, during the next week or so.

>> Top

The New Post Editor And Read More

One problem which we seem to see, pretty consistently, in Blogger Help Forum, is where the posts and a sidebar end up in one long column, with one above the other.

Reports like

My posts have vanished!

and

My sidebar (my archives, my Followers, my profile gadget, ...) have dropped to the bottom of the page!

are seen a lot in the forum. Generally, it's caused by trying to put too much in one place.

Recently, though, a few bloggers report the dropped sidebar symptom, after they try the new post editor, and the Blogger "Read More" option (called by Blogger, "Jump Break").

The "Read More" feature in Blogger blogs has been a long needed option.

Before the new post editor, Blogger, and at least 2 other bloggers, had their own competing, and mutually incompatible, procedures for making your blog show, and execute, a "Read More" link. All 3, to my knowledge, had drawbacks. One of the most obvious was that each different version was added by editing the post HTML, and the HTML was complex, and messy.

The "Jump Break" option, in the new post editor, is easy to add.

1. Add a New Post, or edit an existing post, in Compose mode.
2. Position the cursor after the words that you want to be always shown.
3. Hit the "Jump Break" button, in the editor toolbar.
4. The jump break is inserted into the post editor window.
5. When you publish the post, you'll see the words that you want to be shown, followed by the link "Read More".
6. What could be simpler?

---

(Update 2010/04/17): It's possible that the above instructions from Blogger, if you follow their complete instructions and add Jump Break to an older template, may be slightly misleading. Read their instructions, then read mine, please.

---

In rare cases, the "Jump Break" button in the toolbar may not work. If you have that problem, go into the "Edit HTML" mode, and insert

<!-- more -->

right where you need your jump break.

For all the simplicity in adding this (either in Compose or "Edit HTML" mode), it's not producing simple results.

There appear to be at least two scenarios where a blog, with one or more posts published with jump breaks, would have a dropped posts or sidebar section.

1. When the blog displays more than 10 posts in main page view, each post with a jump break, the 11th post will cause this problem.
2. If the jump break is inserted into the middle of a section of text with formatting implemented using a "<div> ... </div>", a "<div>" section broken by a jump break will cause this problem.

The workarounds to prevent these scenarios are obvious.

1. Reduce your main page size.
2. Don't add jump breaks in the middle of "<div> ... </div>" sections.

---

One possible cause of code containing lots of "<div> ... </div>", a "<div>" would be content composed in Microsoft Word, or another external word processor / desktop layout program. Another, as noted above, may be slightly misleading instructions.

Also, watch out for the third party gadget "Related Posts" LinkWithin. You need this gadget ahead of the "Read More" break (you want your readers to see it without having to display the entire post), but be careful and don't put the "Read More" break in the middle of the LinkWithin code!

---

But those workarounds may not be popular, or easy to implement.

1. Some bloggers like to publish blogs with 15, 20, or more posts in the main page.
2. Blogger who like this new, shiny feature may not be aware of when their posts include "<div> ... </div>" sections. How can they avoid breaking a section that they can't see?

---

(Update 2010/02/22): This week, we are seeing an incompatibility problem between the new Auto Pagination feature, and the older "Read More" variants. This is resulting in greatly reduced main page and archives page height. It appears that the proper solution is to replace all old "Read More" variants with the new "Jump Break" solution.

---

>> Top