A New Way Of Doing Archives?
I've been working on Hi, Mike for the past 5 days or so, and it's coming along 10x faster than I thought it would. It looks really tight, and in my opinion, I think lots of people will love it. But anyway, this post is about how to display information on a weblog, because I'm not totally convinced that we're all doing it the correct way.
The Elusive Entry
I'd guess that 99% of my readers who have weblogs have a separate "archives page" or group of pages on their site (Adam's the only one that comes to mind that's opposite ...... got any other examples?) that link to either months, or categories, or some other combination of blog entries grouped by metadata. It's a fact that weblog templates start you off in this mode — the idea that the recent entries are on the homepage and older ones are in a different part of the site is one that's perpetuated by almost all of the main blog applications. Okay, it's a majority thing, but should it really be that way? Have there been usability studies done with bloggers that asked them how they actually use weblogs, or find older entries, etc.? I'm not aware of any, but I could be wrong.
Anyway though, is the separate archives section such a great idea? To me, it's worthless, and I'll tell you why: I don't use archives or search. That's right, I've never liked archives, or the idea of a search, in any weblog that I read. The reason is because if I thought a weblog post was good enough to warrant a second look, then I bookmark it. Or I remember the title, and just Google it. I think Kottke has the right idea in the way he does archives, but it's not absolutely perfect. Either way, if a post is important enough to me it'll stick in my mind. Has this ever happened to you?
"Oh man, there was a blog post on that cool new comment bubble icon like two weeks ago but I have no clue what weblog it was on. Now I need some inspiration for ________ and I wish I could find it, but I don't know where to look!"
It happens to me a lot. Weblogs are becoming very anonymous now because I read them all through Bloglines and all the content mashes together so I don't know who writes what anymore. All I know is that 1) I remember a recent post about something that is now very interesting to me, and 2) finding it would kick ass, but 3) I don't know who wrote it, so I don't even know where to start. In this case, blog archives don't work because I don't know which weblog posted it, and also, blog search boxes are useless because again, I don't know which weblog posted it. By now I usually turn to Google, start piecing together what I remember of the post, and then through backlinks I usually find what I'm looking for. So long story short, I don't use blog archives much because if I'm looking for something I just use Google anyway.
Show Readers What They Want
Weblogs are interesting from an information display point of view because entries are categorized both temporally (when they were posted) and categorically (Design, Cats I Like, Family, etc.) and both are important factors when reading a post. If I'm reading about a new Flickr feature, I want to know if this post is dated 1 hour ago, or 4 months ago, because the older one I probably already know about. Or if I'm at a designer's site, and the past 10 posts are all about their new home, I want to skip ahead and read the cool Photoshop tutorials which are all part of the same category.
So because of this, I think I'm going to get rid of the typical archives section on Hi, Mike.
Weblog posts will have more associated data listed alongside the content. Stuff like "Here are 4 more entries that are also about Mac OS X" or "Here are the latest entries that have the most comments" or "These 5 entries have the most inbound hits from Google queries." It'd be cool if I could read a post, then see 5 more posts that are on similar topics that I might like to read. Think Amazon and their "related books" page sections. Instead of lumping all archives together in one section, I want to make it more organic by distributing relevant archive sections on each page where they are within context. So if you're on an individual entry page, you'll see a listing of posts that are related to this one, or were written in a similar timeframe. To me this seems more logical and user-centric, but I could be wrong. Does this sound like a good idea?
Reader Comments
I've said this before, but I'll continue saying it until the day I retire (like 5 years from now *crosses fingers*): reader comments are the most important thing on a weblog. Someone, somewhere, thought your words were important enough to put his or her life on pause and write something that will appear on your website. They put down their phone, stopped IMing for a second, stopped paying attention to music, put down their book or magazine, paused their lunch, just so they could give you feedback and let you know what they thought. I think that reader comments should be given a lot of visual weight in the design of a weblog, and himike.org will do just that, more-so than my other designs.
Design Inspiration And Sneak Peek
I've been told that some of my sites look similar, and that I have my own personal style, which I definitely agree with. I've also been told (recently by a potential client) that he didn't think I was capable of branching outside of my portfolio and doing something different than my usual work. I'm not totally sure how sites like To-Done, BusinessLogs, or TCB all give off the same design aura, but regardless, my new site looks nothing like anything I've done before. And to prove it, here's a sneak peek :)


I visit the