-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Apparently the /banners/ is for people who want to advertise Mozilla
on their sites...
Regarding translations, it would be entirely possible to do a
/{page-name}.html.{language-code}, and this is transparently do-able
in Apache. This is good for a few reasons - its all in one place :-).
So for english we have:
http://www.mozilla.org/organisation/at_a_glance.html.en, for German
we could have
http://www.mozilla.org/organisation/at_a_glance.html.de, and when
refernecing the page you would just say
http://www.mozilla.org/organisation/at_a_glance.html. (then apache
would use the pref. lang which gets sent by the user-agent somewhere
in the HTTP request.)
(escuse my non-american spelling).
Or the other track would be to have a lump translation: eg
http://www.mozilla.org/en/organisation/at_a_glance.html.
http://www.mozilla.org/de/organisation/at_a_glance.html
Personally I don't like the second option...
I presume Netscape-Enterprise/3.6 could do something
similar.....................
Also, I reckon things like editorials, legal, press, roadmap-images,
etc would go nicely in a /organi{s/z}ation/ directory.
E.g. /organisation/editorials/, or /organisation/legal/, or
/organisation/press/, etc.
And for docs that don't fit anywhere, maybe a /misc/ :-), that way
one could really get rid of the /*.html's. (except for index.html).
My NZ 2 cents. (approx 5 cents american.)
- -Patrick.
- ----- Original Message -----
From: "Axel Hecht" <[EMAIL PROTECTED]>
Newsgroups: netscape.public.mozilla.documentation
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 13, 2000 1:56 PM
Subject: Re: New Structure
> Several 2cnts below...
>
> Gervase Markham wrote:
> >
> > OK. Here's my first shot:
> >
> > ( -> indicates a rename). "New directories" which already exist
> > will obviously still contain what's already in them. Obviously
> > each subdir will need a tidy-up inside it, but I'm not thinking
> > about that now :-)
> >
> > New top level dirs Current top level dirs to move inside them
> > ------------------ ------------------------------------------
> > community banners, events, party, school
>
> banners? Is that stuff now under /images/? or something different?
> If those are just graphics for site use, the should IMHO stay in
> /images/
>
> > docs build, classic, hacking, statistics
>
> do we need separate dirs for user and developer docs?
>
> > ports unix
> > projects bugs -> bugzilla, directory, editor, ef, mailnews,
> > msgsdk,
> > rhino
>
> This could get rather crowded, which pages of a project should go
> beneath the projects dir, which should go to docs? Or is projects/
> more of the developer doc hierarchy?
>
> > quality bugs (rest of it)
> > releases (stuff from seamonkey)
> > status
> > tech rdf, scriptable -> xpconnect, wallet, xmlextras -> ?,
> > xpapps,
> > xpfe, js, newlayout -> gecko, oji, performance,
> > profile-manager
> > **** editorials, legal, press, roadmap-images, lots of the
> > docs
> > in the root dir
> >
> > Really Important URLs we can't move:
> > MPL
> > credits
> > keymaster (?)
> > (Are there more of these?)
> >
> > **** - I know these things should be grouped, but I can't think
> > of a good name for the directory they go in.
>
> Where should we have L10N? Do we want translated introductions on
> mozilla.org?
>
> <...>
>
> Axel
>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOjYnz+5gPjuO7VwfEQIU9QCeNckzET47iTFvVvDkn+2jXnheZnoAmQEK
WJbEAQLpOQIGKof82BNz8LXn
=Ah5v
-----END PGP SIGNATURE-----
