Story archive usability questions: always fun!

Random question in re: story archive design for single-author archives. Um, which is a fancy way of saying "hey, that web site where I sling up all my stories".

With 74 stories to list, the index page begins to be long, and even the series list is long. Is this length still manageable? Do you want serieses broken out onto their own pages, or is keeping them on the index page with all the info in one place better? Do you browse for things you haven't read or instead want to zero in on a specific story?

If you wanted to, say, find all of my Giles/Jenny stories, how would you do so? Is it obvious or not?

I realize you're a bit of a skewed audience, since if you're commenting on this post you're more likely to be a regular reader. The experience of somebody who drops in and wants to find something interesting to read is different.

I need to find a new way to display information in the story header sections. It's absurd to have things like "Date:" there when that's self-explanatory. Some day, some day I will have a reasonable archive design! I have next week off, and I think one thing I'm going to do is write the web app portion of this project. Or at least start it. Right now you don't want to know what I do to inject new stories into the database. (Okay, it's not as bad as it might be: I edit yaml by hand.)
  • Current Music: Red Moon Slide - Original Mix : Nitrous Oxide : Red Moon Slide
I would love summaries like that, if only because my memory for matching stories with titles is terrible and then I tend to lose the one I'm looking for.
I'll do a massive true index next, I think, just to see what it looks like, with all the meta-info about a story in one place. Tags, pairings, summary, title, series, all that jazz. It might be too much.