Contact sheppy, our Developer Documentation team lead, to let him know you're starting a new localization. You don't need his permission or anything, but he likes to know who you are.

Add a row for your language to the table above, and include anyone else who is planning to work on it.

Create a bug in Bugzilla requesting that your language be added to the list of languages supported by MDN. This bug should be in the "Mozilla Developer Network" > "Localization" category. It will be automatically assigned to the correct person.

Wait while the MDN team handles your request. If your bug isn't responded to within three or four days, please add a comment to the bug asking for an "ETA" for completion.

Once the locale has been added to MDN, you can use the Verbatim tool to translate the user interface strings for the site, and you can begin translating articles on the wiki.

What should a localized MDN look like?

The basic structure of each of the localized wikis should be essentially the same. In general, you should try to maintain the same hierarchy of pages, so that each page on each language corresponds to a similar page in each locale.

You are welcome to link to external local pages, write your own articles, and translate everything from the English wiki. If you do decide to write your own articles, it would be helpful if you could provide an English translation for the English wiki so it can then get translated into all of the other localized wikis.

Adding local resources you should keep NPOV rule. No links to commercial sites (like paid courses, web design companies, etc.). You should promote Open Standards and cross-browsing web coding over closed or proprietary methods wherever possible.

Note: Team leads are encouraged to monitor their locale's content for spam and other inappropriate materials and take steps to get them removed or corrected.

How do I organize a localization project?

There are lots of great tips from various existing translation teams; you should feel free to adopt any of these ideas you choose. In addition, please feel free to add your own suggestions as well. See this template in the Spanish wiki for an example.

Use a template to identify articles that are in the process of being translated. The template should provide an information box that includes a link to the original version of the article. The template should also add the article to a "Need translation" category. This helps track articles that are in the process of being translated.

Use a template to include articles that need to be translated in article lists with a flag or marker next to them indicating that the article hasn't been translated yet. This is a way to advertise important articles in need of translation. See this template in the Spanish version of MDN for an example.

Make use of the "Needs technical review" and "Needs editorial review" tags, to mark articles that have been translated but should be double-checked for technical and grammatical accuracy.

Use a "Trash" template to mark pages that need to be deleted. Since only admins have access to delete articles, this provides a way to mark that an article is obsolete until the admins get the page deleted.

Be sure to include translations of these MDN "how to" pages, and include additional pages as necessary to explain your localization team's policies and practices.

Per-language RSS feeds

You can monitor RSS feeds for each language, so that you are alerted to changes on a given language's contents: