L10n:Web parts/mozilla.org
Mozilla.org website l10n implementation (PRD)
The mozilla.org website is currently not localizable, in sense that we need to change static content if we want to point to localized pages. All links need to be hard-coded.
| Role |
Name |
|---|---|
| Plan supervisor |
David Boswell |
| L10n supervisors |
Pascal Chevrel & Seth Bindernagel |
| Development |
Milos Dinic |
For the l10n implementation, we're using current mozilla-europe.org l10n system. After that, we'll have a composite and robust l10n system.
There are two major things we want to make sure we get:
1. Rewrite website to have the same look and feel, but have a back-end that will provide us with functionality we need 2. Don't change the localization process most of our web l10n localizers are used to, so we don't lose time on educating our contributors on how to localize the mozilla.org website
Technical requirements
This summarizes our technical requirements for the creation phase:
| Requirements |
|---|
| Create a branch |
| Create a staging website |
| Grant commit access to those who will be working on it |
| Have a caching system(TBD) |
Development phases
Phase 1
We want to create a new system with very few pages available, just to make sure we have major functions covered(page redirection 404 errors redirect).
| TODO |
|---|
| Install the system |
| Create the directory structure |
| Add home page for 3 locales(en-US, fr and hr) |
| Create sidebars as we go - move sidebar parameters(as in: anchors, link titles) from static pages to backend |
| Make 404 error(Document not found) redirects to a current locale |
| Create a `kildare` theme for the new system |
Phase 2
| Tasks |
|---|
| Modify all existing pages to work with the new system |
| Have a few locales have most important pages translated |