This is the current proposal for the URI structure of the new Zope-based
www.mozilla.org. Comments welcome. Discussion time period: 1 week, after
which we'll roll the comments in and that'll be that.
Principles of URI design:
A URI is a -permanent identifier-. It should be constant.
The URI structure "should reflect the >>best logical
organization<< of the documents on the server by
exploiting its hierarchical nature."
Thus, there should be "a place for everything and
everything in its place".
The structure should create a coherent organization of
the site's content.
It must be extensible and highly forwards-compatible.
Proposed URI Structure:
mozilla.org/
|
|--about/ - about mozilla.org
| | http://mozilla.org/mozorg.html
| |
| |--community/ - newsgroups, IRC, mailing lists
| | http://mozilla.org/community.html
| |
| |--history/ - a history of mozilla.org
| |
| |--mission/ - mission
| | http://mozilla.org/mission.html
| |
| |--people/ - who we are
| | http://mozilla.org/about.html
| |
| |--sponsors/ - sponsors
| |
| |--credits/ - http://mozilla.org/credits.html
|
|--contribute/ - How to get involved/contribute to Mozilla
| | http://mozilla.org/get-involved.html
| |
| |--advocacy/ - Mozilla advocacy guides
| |
| |--evang/ - Evangelism guides
| |
| |--hacking/ - general rules and guidelines for hacking
| | | Mozilla code
| | | http://mozilla.org/hacking/nutshell.html
| | |
| | |--checkin/ - Checkin rules/process
| | | http://www.mozilla.org/hacking/rules.html
| | | http://www.mozilla.org/hacking/bonsai.html
| | |
| | |--guidelines/ - coding guidelines
| | | http://www.mozilla.org/hacking/best-coding-practices.html
| | |
| | |--write-access/ - getting CVS access
| | | | http://mozilla.org/hacking/getting-cvs-write-access.html
| | | |
| | | |--cvs-form/ - CVS access form
| | |
| | |--review/ -
| | | http://mozilla.org/hacking/reviewers.html
| | |
| | |--guide/ - Reviewer's Guide
| |
| |--qa/ - overall QA stuff
| | | http://mozilla.org/quality/
| | |
| | |--bugs/ - bug writing guidelines and related resources
| | | http://mozilla.org/quality/bug-writing-guidelines.html
| | |
| | |--_?_/ - much of http://mozilla.org/quality/help/ (maybe a
| | triage/ directory?)
| |
| |--tools/ - tools for contributing
| | | http://mozilla.org/tools.html
| | |
| | |--bugzilla/ - for use of Bugzilla
| | | http://mozilla.org/bugs/
| | |
| | |--bonsai/ - for use of Bonsai
| | | http://mozilla.org/bonsai.html (top half)
| | |
| | |--cvs/ - for use of CVS
| | | http://mozilla.org/cvs.html
| | |
| | |--tinderbox/ - for use of Tinderbox
| | | http://mozilla.org/tinderbox.html
| | |
| | |--zope/ - for using Zope
| |
| |--writing/ - document writing/coding/uploading/style guidelines
|
|--dev/ - all development-related information
| |
| |--tech/ - Mozilla technologies
| | |
| | |--xul/
| | |
| | |--js/
| | |
| | |--xpcom/
| |
| |--ports/ - Platform homepages
| | |
| | |--beos/
| | |
| | |--macosx/
| |
| |--_?_/ - Mozilla developers' stuff
| |
| |--web/ - Web Developer info - articles on writing pages for
| | Mozilla, FAQ, show-off section, etc.
| |
| |--embed/ - info for potential embedders of Mozilla tech.
|
|--events/
| |
| |--year/ - all events for year
| |
| |--event_name/ - all files associated with event
|
|--license/ - MPL, NPL, current licensing strategy
|
|--software/ - list of software released by mozilla.org w/ description
| |
| |--mozilla/ - intro & description for all of Mozilla
| | |
| | |--build/ - build instructions
| | | | http://mozilla.org/build/
| | | |--beos/
| | | |
| | | |--mac/
| | | |
| | | |--macosx/
| | | |
| | | |--os2/
| | | |
| | | |--unix/
| | | |
| | | |--win32/
| | |
| | |--distributors/ - link to Mozilla distributors
| | | (e.g. Netscape, Beonex)
| | |
| | |--releases/ - Mozilla release info (one directory per
| | | release)
| | | http://mozilla.org/releases/
| | |
| | |--0.6/ - relnotes and stuff
| |
| |--bugzilla/ - for using Bugzilla on your own system
| | (subdirectory structure similar to mozilla/,
| | above)
| |--etc.,
|
|
|--news/ - news items (may be links to other parts of the site)
| |
| |--year/ - all news items for year
| | |
| | |--month/ - all news items for month (numerical - e.g. 05)
| | |
| | |--article/ - all files associated with the article,
| | directory named after article title
| |
| |--status/
|
|--support/ - links to product-specific info under /software/product
Notes on the URI Proposal:
The creation of /software/mozilla instead of just assuming
/software for mozilla prepares mozilla.org for the
possibility of splitting the application into separate
releases. It also provides a place for any other software
released by mozilla.org.
/contribute details *how* to contribute--code, docs, qa, etc.
Much of http://mozilla.org/quality/ goes under /contribute/
qa/. Testcases can go in their respective /dev directories.
Sections under /contribute link to Get Involved pages for
individual projects. E.g. BugAThon may be linked from
/contribute/qa, but it exists in layout's directory under
/dev.
Splitting away /dev/web allows web-developer content to be
more free-form. Web developers aren't going to view the
separation of, say, the JS engine, the DOM, and the style
system as sharply as we do. Docs for web developers are
integrated. Docs for Mozilla developers are more separated;
they are both organized and written differently, and the
focus and purpose of their content also differs. This is
why web-developer documentation should not be spliced into
the various development directories. However, /dev/web can
still link to docs in those directories!
The use of dates for publications organization ensures a
coherent structure regardless of topic--which is more easily
addressed by an HTML page with descriptions anyway. Articles
will frequently appear in more specific directories rather
than in the /news hierarchy, but will always be linked from
the month's index page.
Key URLs from the old site, such as /MPL and /releases, will
be handled by redirects. Current key URLs are:\
/MPL and friends
/credits.html
/releases and friends/
/mailnews/start.html
/mozorg.html
/news.rdf
Anything that's ever been coded into a release, so:
/quality/help/bug-form.html
/quality/bug-writing-guidelines.html
/quality/smoketests/
Gerv
