<?xml version="1.0" encoding="UTF-8"?>
<page>
  <content>I've always known the main index page to the Notebook (I still dislike the word "Blog") was not very useful.  All it did was display the full text of the most recent five articles that I had posted. What confirmed my belief was that most people arrived to my posts by way of the RSS feed or a Google search.  This means most people rarely even see the index page, and even if they do it is not much use to them because of the sheer amount of scrolling text.

What finally motivated me to make a much needed change was reading a post over on Chris Pearson's blog, "Everything You Think You Know About Blog Architecture Is Wrong":http://www.pearsonified.com/2006/07/why_everything_you_think_you_k.php. I think Chris is dead on with his thinking that the main pages for blog-style websites should be a collection of starting points for readers, not just a chronological listing of content.

So I took about a half hour to turn the index to the MyersDS Notebook into something a bit more useful.

h2. Headlines, Headlines, and more Headlines.

As "CopyBlogger":http://www.copyblogger.com/ has drilled into my head, headlines are important, and probably what most people use in their search for content. It only made sense to make headlines the focus of the index page. Let people explore from there. So I scrapped most of the index page, which was 90% actual article content, and set out from there.

Once I had a bit of a blank slate to work with I realized the most recent post is important, but I need not make it the complete focus.  So after giving myself a refresher course on the Ruby string library I only have the first paragraph of the most recent post show. It's prominent, but not overwhelming.

h2. Let The Readers Decide What Is Good

Next I wanted an easy and self maintaining way to keep the most popular posts on the index. I went with my first instinct and went with a simple ranking. The top five posts with the most views appear on the front page, simple as that. It's live updating through a simple counter on each post so it requires no manual labor on my part to keep track of what people like. I believe it will also prove valuable in choosing what to focus my choice of topics on and give readers what they want. So far this has continued to be a steady stream of tips and tutorials on all things Ruby on Rails. Which is fine by me because I'm happy to help grow the amount of helpful articles out there on the web about my favorite web app framework.

h2. The End Result

The resulting Notebook Index is something I'm fairly happy with for a first draft. It is much more concise and gives people an easy way to find what they want. I'm sure I'll continue to refine it, but for the time being it looks much better than an endless scrolling page of text.
</content>
  <created-on type="datetime">2006-07-17T05:44:17+00:00</created-on>
  <has-changes type="integer">0</has-changes>
  <html>&lt;p&gt;I&amp;#8217;ve always known the main index page to the Notebook (I still dislike the word &amp;#8220;Blog&amp;#8221;) was not very useful.  All it did was display the full text of the most recent five articles that I had posted. What confirmed my belief was that most people arrived to my posts by way of the &lt;span class="caps"&gt;RSS&lt;/span&gt; feed or a Google search.  This means most people rarely even see the index page, and even if they do it is not much use to them because of the sheer amount of scrolling text.&lt;/p&gt;


	&lt;p&gt;What finally motivated me to make a much needed change was reading a post over on Chris Pearson&amp;#8217;s blog, &lt;a href="http://www.pearsonified.com/2006/07/why_everything_you_think_you_k.php"&gt;Everything You Think You Know About Blog Architecture Is Wrong&lt;/a&gt;. I think Chris is dead on with his thinking that the main pages for blog-style websites should be a collection of starting points for readers, not just a chronological listing of content.&lt;/p&gt;


	&lt;p&gt;So I took about a half hour to turn the index to the MyersDS Notebook into something a bit more useful.&lt;/p&gt;


	&lt;h2&gt;Headlines, Headlines, and more Headlines.&lt;/h2&gt;


	&lt;p&gt;As &lt;a href="http://www.copyblogger.com/"&gt;CopyBlogger&lt;/a&gt; has drilled into my head, headlines are important, and probably what most people use in their search for content. It only made sense to make headlines the focus of the index page. Let people explore from there. So I scrapped most of the index page, which was 90% actual article content, and set out from there.&lt;/p&gt;


	&lt;p&gt;Once I had a bit of a blank slate to work with I realized the most recent post is important, but I need not make it the complete focus.  So after giving myself a refresher course on the Ruby string library I only have the first paragraph of the most recent post show. It&amp;#8217;s prominent, but not overwhelming.&lt;/p&gt;


	&lt;h2&gt;Let The Readers Decide What Is Good&lt;/h2&gt;


	&lt;p&gt;Next I wanted an easy and self maintaining way to keep the most popular posts on the index. I went with my first instinct and went with a simple ranking. The top five posts with the most views appear on the front page, simple as that. It&amp;#8217;s live updating through a simple counter on each post so it requires no manual labor on my part to keep track of what people like. I believe it will also prove valuable in choosing what to focus my choice of topics on and give readers what they want. So far this has continued to be a steady stream of tips and tutorials on all things Ruby on Rails. Which is fine by me because I&amp;#8217;m happy to help grow the amount of helpful articles out there on the web about my favorite web app framework.&lt;/p&gt;


	&lt;h2&gt;The End Result&lt;/h2&gt;


	&lt;p&gt;The resulting Notebook Index is something I&amp;#8217;m fairly happy with for a first draft. It is much more concise and gives people an easy way to find what they want. I&amp;#8217;m sure I&amp;#8217;ll continue to refine it, but for the time being it looks much better than an endless scrolling page of text.&lt;/p&gt;</html>
  <id type="integer">45</id>
  <is-post type="integer">1</is-post>
  <is-published type="integer">1</is-published>
  <title>Rethinking the Notebook Index</title>
  <url>notebook/2006/07/17/rethinking_the_notebook_index</url>
</page>
