Index with Headings

A simple, two column index still looks a bit bland, and it’s difficult for readers to scan through a dense block of items to find what they’re looking for.  So it’s time to start playing with some more options.

First, go back to the index settings page and select:

  • Display alphabetical headings

Save your changes, refresh your index page, and lo and behold, you have an index that is divided into groups according to the letter they start with.

Note that the headings are also links that take you back to the top of the page when clicked.

But there are still a couple of minor cosmetic issues.  First the blog’s theme causes the gap below the headings to be larger than the gap above, which looks a little odd.  Second there is no heading at the top of the second column, which throws the look of the index off a little.

We could solve the positioning of the headings by modifying the CSS stylesheet of the theme or the index, but there is an easier way, as you will see on the next page.

View the index »


No comments yet to

  • Hi everybody,

    I agree with all of you: this is a very Great Plugin! Thanks to Mike .

    Now I need your help (Mike or anybody who could) .

    1- I create an author index on my site . It seem working very well . But how I can group items with the same heading under one main entry without selecting subheadings ? I mean each author name appear only once and when we click on it we’ll see all his post. Please take a look on my page

    2- I have another site (same server, same hosting) but the author index page on this site can’t be read (please click on this link for reading the error message)

    Many thanks in advance

    LW

  • 2- I have another site (same server, same hosting) but the author index page on this site can’t be read (please click on this link for reading the error message)
    Sorry ! I don’t know why the above link is not working .

  • GREAT plugin, thank you!!

    @curtis klope, thanks so much for the tweak, i was experiencing the same issue and was so not looking forward to diving into the code, so was thrilled to find a quick solution!

    i think it is a bug and your fix should be rolled into the next release…