1) I have a strong opinion on these bits:
/contribute/community/ not /about/community/
/contribute/documentation/ not /contribute/writing/
/news/events/ not /events/
/develop/ not /dev/
/develop/build/ not /software/mozilla/build/
(How many non-developers really build Mozilla? I sure don't.)
2) My main problem: I don't like the /software/ hierarchy. It's trying
to do 2 things at once.
The 2 meanings of the word "software" are being blurred.
1 - /software/mozilla/ = here's the software (i.e. the actual files)
to download & build
2 - /software/bugzilla/ = everything about bugzilla, the project
i.e. a category for dividing the site
I'd do one hierarchy for downloading Mozilla
/download/
/releases/
/nightlies/
/distributions/
and another for other software projects: the non-browser projects
currently listed waay down the bottom of the /projects/ page (or not).
/software/ or /projects/ or even /othersoftware/
/bonsai/
/bugzilla/
/tinderbox/
/grendel/
/vixen/
/rhino/
3) I love how /dev/tech/ stuff has finally been grouped together sensibly.
4) Should /develop/web/ be a separate hierarchy maybe? Isn't /develop/
for developing Mozilla itself - not developing sites for Mozilla?
/web/? /webdev/? OK so I'm crazy. Ignore this one if you like.
5) Where do theme developers go? is /develop/tech/xul/themes/ too deep?
6) I'm into redirects where possible.
At the end of the day...
- All this talk about URIs being static for eternity is bollocks. Great
idea, but don't sweat it too much, or we'll keep moving too slow.
(newsgroup hierarchy?)
- It's the navigation hierarchy & content that really matters. Making
the information easy to find, even if you start at the top. I'd be less
concerned about what happens if someone has done deep bookmarks all over
the place.
- And then, of course, there's the content. Less is more. Waiting for
Zopot...
My 3c...
Luke
--
[EMAIL PROTECTED]
