fantasai wrote:

> I agree with you, and this is why the mozilla-reorg project exists. But
> right now the mozilla.org hierarchy is a mess, so we need to have something
> like /docs or /catalog up so people can find the documentation they need.

"mozilla.org is a mess, so right now we need to...er...do something 
else.  That will make it worse."

We're going down endless paths of a) deciding the final final best final 
URN for the re-org, when something will do b) development of some new 
platform we're not all convinced about.

I've seen the hierarchy suggestions here - yours, in particular. 
They're good.  Let's do it.  This is how I see it:

1) Fix the structure
* Get a copy of the site (from CVS or not)
* Shuffle it around by hand, based on the suggestions in this newsgroup, 
to get the structure right.  Don't fuss.  No final final best final best 
URNs or anything - allow a lot of short term reshuffling.  If it looks 
wrong when you actually see it in place, why not fix it?
* Do a good ONE PAGE site map that reflects the great new structure (one 
page like /docs, good hierarchy like /catalog, but not so deep)
* Delete /docs and /catalog
* Delete as much as possible actually - Less is more.  There's lots of 
duplication, lots of stuff so outdated as to be irrelevant, lots of cruft.

2) Fix the wrapper
* Do a good top navigation bar (home | download | sitemap | search)
* Do a good left-hand-side navigation tree for each major section
* Do a decent stylesheet that actually...includes...some styling.  Only 
apply styles chosen by user nothin'.  C'mon, it's a /web browser/, 
layout is what it's for, surely the site should set styles.
* Combine these into a wrapper.

3) Make everyone like it
* Put it all up at alternate site (not moz.zope) so people can see it & 
be convinced that it's better & be excited by the idea.

4) Fix the details
* Like making it valid HTML, Latin1 etc etc.  Don't be too concerned 
about style.

Then all that's left is
4) Get CVS access, check it in.

Heyhey.  Not bad.  A new site...
--
Luke


Reply via email to