Mozilla.org:Archiving Suggestions

If you would like to suggest a page on www.mozilla.org for archiving, please add a link to this page.

Stuff Not to Remove

Don't remove the following pages:

 * /hacking
 * /editorials
 * /about
 * /contribute
 * /foundation
 * Anything linked from /about/history

Archiving Suggestions

mdc:MDC:Needs_Redirect has a list of pages to be redirected and some pages to be deleted too

projects/xpcom/

http://www.mozilla.org/projects/xpcom/style-guide.html

Not relevant, since we're moving documentation to MDC where formatting rules are different. No point in archiving. Suggest marking as "gone". --Nickolay 16:29, 17 September 2007 (PDT)

http://www.mozilla.org/projects/xpcom/doc/

There's no content here. Click on the links and you get empty pages. The entire projects/xpcom/doc directory should be deleted. --jorendorff (copied from MDC:Needs_Redirect. Again, no point in archiving --Nickolay 16:29, 17 September 2007 (PDT))

http://www.mozilla.org/projects/xpcom/mozIRegistry.html

This was actually migrated to mdc:mozIRegistry but I don't see any point in keeping this. --Nickolay 16:29, 17 September 2007 (PDT)

...

xpfe/

http://www.mozilla.org/xpfe/issues.html

gone - obsolete, and nothing links here --Jorend (copied from MDC:Needs_Redirect.)

docs/

http://www.mozilla.org/docs/web-developer/css1technote/css1tojs.html

Cross-Browser DHTML TechNote: Code Generator for Setting CSS1 Properties from JavaScript

That document is clearly outdated, obsolete. Some code examples are wrong, use invalid markup code or will not even work in Firefox 1.0. It would require much more work to update it than to rewrite it from scratch. I already said so in [1]--Gérard Talbot 14:29, 29 April 2008 (EDT)

http://www.mozilla.org/docs/codestock99/

Slides from CodeStock '99

and its related documents:

http://www.mozilla.org/docs/codestock99/html40/index.htm http://www.mozilla.org/docs/codestock99/xbdhtml/index.htm http://www.mozilla.org/docs/codestock99/css/index.htm etc.

Those documents are clearly outdated, rely on frames (with NORESIZE and SCROLLING="NO" specified!), rely on javascript support enabled (onclick to move to next or previous slide), have validation markup errors, are difficult to use (accessibility). We already have tutorials on HTML 4, CSS1 & 2, DOM 1, etc. at MDC which are all better suited. See [2] --Gérard Talbot 14:29, 29 April 2008 (EDT)

[add link here]