On May 3, 2006, at 4:17 PM, Allen Gilliland wrote:
The above is what is currently proposed on the wiki and is a viable
option, but after a discussion with some of the guys from
Technorati and poking around a bit on the web I think there are
some good alternatives to consider.
/<weblog>/entry/<YYYYMMDD>/<anchor>
/<weblog>/entry/<YYYYMMDD>/?category=<cat>&page=1
/<weblog>/entry/<YYYYMM>/?category=<cat>&page=1
/<weblog>/entry/<YYYY>/?category=<cat>&page=1
The structure shown above seems to be used on a number of sites and
has some noticeable advantages and disadvantages. MT (typepad,
livejournal) and blogger use this except they omit the day from the
url and only support YYYY/MM.
pros:
- date becomes part of the standard link, which makes it easy for
users to hack at the url and know what to expect.
- we can actually calculate next/prev year, month, and day from the
url.
cons:
- if someone modifies the pubtime of an entry then the permalink
changes :(
- we have to additionally validate that the url date matches the
entry date for permalinks.
I'm don't like using the word "entry" in the URL to a page that will
include a page-able collection of entries. I guess we could use the
word "archive" or "blog" instead, since it does not imply singularity
or plurality. Maybe "entry" and "entries" is the ticket; that's what
I used in the Atom protocol URLs.
Also, I don't understand why we need a date in the entry permalink.
So, why not do something like this:
/<weblog>/entry/<anchor>
/<weblog>/entries/<YYYYMMDD>/?category=<cat>&page=1
/<weblog>/entries/<YYYYMM>/?category=<cat>&page=1
/<weblog>/entries/<YYYY>/?category=<cat>&page=1
Then use a similar structure for "custom" pages, since they also need
date, category, etc.
/<weblog>/page/<page-link>?category=<cat>&page=1
/<weblog>/page/<YYYYMMDD>/<page-link>?category=<cat>&page=1
/<weblog>/page/<YYYYMM>/<page-link>?category=<cat>&page=1
/<weblog>/page/<YYYY>/<page-link>?category=<cat>&page=1
- Dave
