Slashdot Mirror
User-Centered URL Design
Adaptive Path has this interesting essay by Jesse James Garrett on user friendly URL design. When websites were just static files, they were often named in a friendly way, just to make it easier for the designer. But today, many dynamic web sites and CMS's are based around extremely long and complicated URLs that are difficult to work with (ever try to read one to someone over the phone?). This essay explores the way some websites use redirects and smart naming schemes to keep URL's easy and friendly.
A good basic guide from the founder of the web is at http://www.w3.org/DesignIssues/Axioms.html. (Note that URI doesn't follow its own advice, heh)
My site is 100% static HTML, but my rules of thumb for URLs include:
- never more than 80 chars, so they can be emailed
without wrapping
- no uppercase, ever (otherwise you'll forget where
the caps were)
- never more than two directories deep (I sometimes
break this due to bad planning)
- if a new page seems likely to grow into many
pages, it should be created as foo/index.html
instead of foo.html (Someone emailed me this
brilliant tip, I forget who though.)
But the bottom line is to arrange directories
and files (and their names) so that you can
remember them without having to doublecheck.
I agree with the general premise of the article, but unfortunately it was vary light on any useful tips or code.
/. is http://developers.slashdot.org/article.pl?sid=02/1 0/02/1946224&mode=flat&tid=95 -- why couldn't it just be http://developers.slashdot.org/thread/02-10-02/194 6224.html ? Or even http://slashdot.org/developers/02-10-02/User_Cente red_URL_Design.html ?
For instance, this thread in
I'd love to have some tips from various folk on how to use Perl and PHP with Apache in fancy ways to simplify and avoid these clunky URLs.
-- Herder Of Cats
Really nifty utility for dealing with sites that choose the long obfuscated URL approach...