> We should group the site into modules and give an owner to each module. This
It should definitely be the case that there is someone who oversees each
section of the site. However, they should be very keen to delegate.
> 7. org--This would hold all things relating to Mozilla as an organization.
> The style guide and the website cvs page can go here. Along with
> aboutus.html...
Good choice for the name of my **** directory :-). Anyone else got one?
> Is there any reason why I can't create a redesign directory inside the html
> directory?
Yes, several :-) I'm bashing away with that bug, trying to get Netscape IS
to provide us with some proper play space.
> As for the links in the site, what we must do, weather we like it or not, is
> convert all the links to be document relative (so a link from index.html
> http://www.mozilla.org/build/mac.html becomes build/mac.html) While it might
> be possible to do this with a script, doing it by hand may just be easier
> for everyone and it won't be too much work if we split up the site. Each one
16,000 files? :-) I think the only way we can do this is to move stuff
around, run a script over everything which understands the moving, then
run a link checker which can spot stuff we broke.
> Now, as I sit on the bus back home again, I thought about this some more. I
> also think that each document in the website MUST have a posted owner, so
> that users can contact the owner about problems in the site.
That _should_ already be true. If it's not, I tend to check the CVS logs
to see who checked in last.
> Also, once we have these modules setup, we could have the mozilla.org
> product in bugzilla with a component for each module. This would make an
> individual directly responsible for their section of the site, and make sure
> that things get fixed. A QA contact could make sure that things are actually
> fixed (I would be willing to be the QA contact for this).
Is this not bureaucracy for the sake of it? Do we need to go to that
trouble, or can it be more informal?
> results and suggest more modules as needed. Also, shouldn't we get Dawn
> Endico into this discussion, she is the webmaster for mozilla.org and would
> ultimately be the person to make any decisions.
She's welcome to join in (Dawn, are you reading? :-) but might want to
wait until our plans firm up.
Gerv
