Marketing:Thunderbird Website: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Update list of active locales)
No edit summary
Line 1: Line 1:
Localization of the site depends on several factors:
1/ possibility to communicate to localizers via the webdashboard, mozillamessaging is now a separate project there so no problem
2/ locale detection and general locale support on mozillamessaging, we have added the minimum requirements for that with the 2.0.0.21 release and the move of the localized start pages from mozilla.com to mozillamessaging, minor releases now happen on mozillamessaging for locales
3/ simplified templates (header/footer) for locales, to be done but shouldn't take me much time,  a day to make and test them
4/ creation of TB3 content for localizers, this is highly dependent on the creation of en-US content that will be used as a basis for translation, essentially:
    - new start page
    - landing page for all locales that serves as a home page as we do on mozilla.com
    - minimum set of pages (essentially features pages) for top locales which will have a more complete set of pages
5/ creation of a simplified landing sub page on mozilla-europe to also propose downloads there
6/ some administrative work as I have to open bugs for all localizers to give them access to mozillamessaging repo
7/ QA
For Thunderbird 3, we need final QAed en-US content to start localization. We will use French as a test locale, it will be done  before others so as to identify potential localization or technical problems with the site.
For Thunderbird 3, we need final QAed en-US content to start localization. We will use French as a test locale, it will be done  before others so as to identify potential localization or technical problems with the site.


Line 24: Line 4:
- start page: all locales
- start page: all locales
- landing page: all locales
- landing page: all locales
- product sub-pages: on a per locale basis depending on the amount of work they represent (localized graphics? amount of text, screenshots...)
- product sub-pages: on a per locale basis depending on the amount of work they represent (localized graphics? amount of text, screen shots...)
- press release: same as sub-pages
- press release: same as sub-pages
- release notes
- release notes


This means we have about 8 weeks to have the site ready in 50+ locales and in good shape for Thunderbird 3 (that includes translation, some webev work, QA...).
This means we have about 6 weeks to have the site ready in 50+ locales and in good shape for Thunderbird 3 (that includes translation, some webev work, QA...).


------
------
Line 34: Line 14:
This is the list to manage web site content in Thunderbird for our 51 lang/locales.  The items to be localized include:
This is the list to manage web site content in Thunderbird for our 51 lang/locales.  The items to be localized include:


* Product localization
- download "landing" page and thank you page: all locales
* Start page
- product page: on a per locale basis depending on the amount of work they represent (localized graphics? amount of text, screen shots...)
* Support page
- start page: all locales
* Product pages
- release notes
- press release: same as sub-pages


We also need to check for account setup -- which email providers are included during account setup.
We also need to check for account setup -- which email providers are included during account setup.
Line 361: Line 342:


<i>Note: time estimates are calculated in uninterrupted hour/days... Better use them for comparing relative effort.</i>
<i>Note: time estimates are calculated in uninterrupted hour/days... Better use them for comparing relative effort.</i>
*****Notes****
Localization of the site depends on several factors:
1/ possibility to communicate to localizers via the webdashboard, mozillamessaging is now a separate project there so no problem
2/ locale detection and general locale support on mozillamessaging, we have added the minimum requirements for that with the 2.0.0.21 release and the move of the localized start pages from mozilla.com to mozillamessaging, minor releases now happen on mozillamessaging for locales
3/ simplified templates (header/footer) for locales, to be done but shouldn't take me much time,  a day to make and test them
4/ creation of TB3 content for localizers, this is highly dependent on the creation of en-US content that will be used as a basis for translation, essentially:
    - new start page
    - landing page for all locales that serves as a home page as we do on mozilla.com
    - minimum set of pages (essentially features pages) for top locales which will have a more complete set of pages
5/ creation of a simplified landing sub page on mozilla-europe to also propose downloads there
6/ some administrative work as I have to open bugs for all localizers to give them access to mozillamessaging repo
7/ QA

Navigation menu