tracking bug

bug opentochoice-l10n

production

http://opentochoice.org (l10n happens here)

stage

http://opentochoice.stage.mozilla.com (for QA)

Localizing & testing

There's a few types of content you'll localize. (If you have to, please prioritize according to the list.)

1. theme strings
2. categories which have descriptions
3. blog posts, organized into categories
4. graphical assets

the theme

• Download and translate choice.pot
• Contact Staś about uploading it to http://opentochoice.org (please don't do this yourself).
• Go to http://opentochoice.org to view your theme translations.
• Go to http://opentochoice.org/wp-admin/ to translate. (Staś, Pascal or Seth can set you up with an account there.)

the categories

• Translate the category names and their descriptions
• Contact Staś about uploading them to http://opentochoice.org
• If needed, ping Staś about any fixes needed.

the blog posts

• Consult the list of posts to localize on the tracking spreadsheet.
• Go to http://opentochoice.org/wp-admin/edit.php to localize the blog posts. (Staś, Pascal or Seth can set you up with an account there.)
• Click on the "Preview" button to preview your work.
• Click on the "Publish" button to save your work as published. It won't show up until the final version of the site is launched on Wednesday.

graphical assets

• Consult the list of graphical assets bugs
• Consult the tracking spreadsheet
• Comment with your translation in every bug in the list
• A designer will put your translation in the assets (PDF and/or PNG)
• Review the localized asset and sign off on them, if they look good
• Upload them to http://opentochoice.org and link in appropriate posts.