Gervase Markham wrote:
[ snip ]
>>> 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.
Hmm. Could be a pain to update in cvs, since it could trigger two
modules (/docs/user/navigator, /projects/navigator)...
>>> 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.),
I like that.
> 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.
/projects/<product-name>/{user}{dev}/whatever
e.g.
1. /projects/navigator/user/reloading_pages
2. /projects/navigator/dev/reloading_pages
1. Covers hitting CTRL-R, CTRL-Shift-R, etc.
2. Covers what the code does when you hit CTRL-R etc.
>>> **** - 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?
I suggest we postfix all pages with .lang
/projects/navigator/user/reloading_pages.en_uk
/projects/navigator/dev/reloading_pages.de
> Hmmm. Good question. See someone else's comment :-)
But let's not rely on us using .html in the future...
> 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?
Well we need to know what the new site will need in terms of webserver
functionality. I have no experience of Netscape servers, but I wouldn't
be surprised if we were all shouting for Apache to be installed soon.
James Green
