For reference, all of the content in the js directory can be browsed at: http://mxr.mozilla.org/mozilla-org/source/html/js/
Yes, just redirecting http://www.mozilla.org/js/spidermonkey/ to https://developer.mozilla.org/en/SpiderMonkey would be a welcome first step.
> http://www.mozilla.org/js/spidermonkey/ > to > https://developer.mozilla.org/en/SpiderMonkey Done in r88524. For next steps, I recommend archiving the rest of the js directory and then migrating pages over to MDN or elsewhere as needed. This would mean that any page currently in www.mozilla.org/js would automatically get redirected to the version on the archive site. So: http://www.mozilla.org/js/UnicodeIdentifiers.html would take people to http://www-archive.mozilla.org/js/UnicodeIdentifiers.html If there are no objections soon, I'll go ahead and do that. We need to get legacy pages off of www.mozilla.org because of the upcoming mozilla.org/.com merge.
I took one more look at the content in the mozilla.org/js directory and it seems like most relevant content has redirects to MDN already in place and the remaining content is historical and can be archived. For instance, see this LiveConnect page last updated in 2000 (not counting formatting changes). http://www.mozilla.org/js/liveconnect/ Unless there are objections, I'm going to archive the remaining content this week. Keep in mind that after content is archived it is still easily migrated if needed.
No objections here.
I archived the remaining /js content and moved all redirects into the main .htaccess file in r91288. If anyone notices any issues with redirects or with any pages that need to be migrated from the archive site, feel free to reopen.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.