> > ( -> 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
No, the stuff currently in /banners - loads of old and forgotten banners
people can nick to promote Mozilla on their websites.
> > docs build, classic, hacking, statistics
>
> do we need separate dirs for user and developer docs?
Yes. I was merely rearranging the old dirs. I didn't touch on what new
ones we needed.
> > 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?
Good question. I suppose docs not related to a particular project go under
docs (hacking, general building, end-user for the browser suite, etc.),
and project docs in /project/*. Unless you do what someone did, and make
end-user docs a project (/project/user-docs/) but I don't like that.
> > **** - 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?
Hmmm. Good question. See someone else's comment :-)
However, I forgot that www.mozilla.org doesn't run Apache. Does this mean
we can't use mod_rewrite, or is there an equivalent?
Gerv
