I think users quickly respond to standardized index points and the concern you have over items which match the labels, while valid, is less important than it seems at first. Given the two choices, I'll take standardized divisions of the alphabet within the site. This is especially true since it means there's no batching up the output, but I'd prefer it anyway.

As for the splitting specifically on the vowels, I tend to agree that there are probably statistically much better places to divide. One of my nodes in the thread already gets into that. However, that's one choice that's pretty easily changed by tweaking one array in my example. It could be tweaked as the data is updated and measured to fit hacker's specific site, it could be done by frequency analysis of an existing dictionary, it could be done ad-hoc, or there are probably existing works expounding on such matters. It has more to do with the data than the code, and in advance we really don't know how well any particular section breaks will work for hacker, although I have my suspicions that something other than simply the vowels would work better. I'm just not sure what.

In reply to Re^8: Programmatically building named anchors to warp to sections by mr_mischief
in thread Programmatically building named anchors to warp to sections by hacker

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.