L10n:Web parts/mozilla.org: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(→Mozilla.org website l10n implementation (PRD): Wikify everything except tables) |
||
| Line 2: | Line 2: | ||
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. | 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. | ||
{| cellspacing="1" cellpadding="1" border="1" style="width: 493px; height: 122px;" | {| cellspacing="1" cellpadding="1" border="1" style="width: 493px; height: 122px;" | ||
| Line 19: | Line 17: | ||
| Milos Dinic<br> | | Milos Dinic<br> | ||
|} | |} | ||
For the l10n implementation, we're using current mozilla-europe.org l10n system. After that, we'll have a composite and robust l10n system. | 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: | There are two major things we want to make sure we get: | ||
# Rewrite website to have the same look and feel, but have a back-end that will provide us with functionality we need | |||
# 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 === | === Technical requirements === | ||
| Line 45: | Line 41: | ||
|} | |} | ||
=== 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). | |||
<table cellspacing="1" cellpadding="1" border="1" style="width: 566px; height: 190px;"> | <table cellspacing="1" cellpadding="1" border="1" style="width: 566px; height: 190px;"> | ||
<tr> | <tr> | ||
<th bgcolor="#cccccc" align="center" scope="col"> Tasks<br /> | <th bgcolor="#cccccc" align="center" scope="col"> Tasks<br /> | ||
| Line 76: | Line 69: | ||
<td bgcolor="#00cc33"> Create a `kildare` theme for the new system <br /> | <td bgcolor="#00cc33"> Create a `kildare` theme for the new system <br /> | ||
</td></tr></table> | </td></tr></table> | ||
==== Phase 2 ==== | |||
* The overall goal is to get the website working well. | |||
* All pages must be fully functional, and structure must be solid. | |||
* Make sure we have all the mozilla.org functionality implemented in the system before moving on. | |||
* Pages must be clear and easy to translate, without much php/javascript in them. | |||
* Move all the code into a respective page includes. | |||
<table cellspacing="1" cellpadding="1" border="1" style="width: 572px; height: 154px;"> | <table cellspacing="1" cellpadding="1" border="1" style="width: 572px; height: 154px;"> | ||
<tr> | <tr> | ||
<th bgcolor="#cccccc" scope="col"> Tasks<br /> | <th bgcolor="#cccccc" scope="col"> Tasks<br /> | ||
| Line 107: | Line 97: | ||
<td bgcolor="#00cc33"> Optimize pages for localization<br /> | <td bgcolor="#00cc33"> Optimize pages for localization<br /> | ||
</td></tr></table> | </td></tr></table> | ||
==== Phase 3 ==== | |||
<table cellspacing="1" cellpadding="1" border="1" style="width: 572px; height: 109px;"> | <table cellspacing="1" cellpadding="1" border="1" style="width: 572px; height: 109px;"> | ||
<tr> | <tr> | ||
<th bgcolor="#cccccc" scope="col"> Tasks<br /> | <th bgcolor="#cccccc" scope="col"> Tasks<br /> | ||
| Line 127: | Line 116: | ||
<td bgcolor="#ff9900"> Fix style to follow mozilla.org current overall look<br /> | <td bgcolor="#ff9900"> Fix style to follow mozilla.org current overall look<br /> | ||
</td></tr></table> | </td></tr></table> | ||
Revision as of 06:01, 19 February 2011
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:
- Rewrite website to have the same look and feel, but have a back-end that will provide us with functionality we need
- 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).
| Tasks |
|---|
| 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
- The overall goal is to get the website working well.
- All pages must be fully functional, and structure must be solid.
- Make sure we have all the mozilla.org functionality implemented in the system before moving on.
- Pages must be clear and easy to translate, without much php/javascript in them.
- Move all the code into a respective page includes.
| Tasks |
|---|
| Modify all existing pages to work with the new system |
| Have a few locales have most important pages translated |
| Make header and footer localizable |
| Remove legacy pages we're going to either archive or move to MDN |
| Optimize pages for localization |
Phase 3
| Tasks |
|---|
| Add RTL support |
| Optimize pages for localization |
| Add a few more working locales |
| Fix style to follow mozilla.org current overall look |