Something we've been kicking around lately has been the customization of our 404 error.  As you can see,  it doesn't get more simple than that.  However, it's not really user friendly is it.  As long as it still returns the http 400 status code for the engines to know that the page isn't found and shouldn't be indexed, we can make her pretty for the user by adding our nice header and footer.  Moreover, we're going to see if it's feasible to offer suggestions based on the URL entered. 

Who knows if anyone is typing Botw.org/top/Arts/Music/ into their browser...  Well, probably nobody.  It's that "top" that kills us, but we made that bed a long long time ago when we were using classic ASP and we needed the "top" to differentiate a category for the URL rewriter from a standard non-rewritten web page.  Now asp.net lets us make all kinds of groovy http modules and handlers that can intercept the request in the pipeline and determine what to do with it.    It would be a pretty huge change and scary to boot to tinker with the core code in order to remove the TOP.  after all, we'd want existing links with "top" in it to still work...  Well, perhaps someday. 

Anyway, just food for thought.  We've been trying to beef up the usability on botw in general.  "What would I want to see if I were surfing Best of the Web?", is usually a good place to start.