Websites/State of Mozilla 2011
This page contains all of the important details for State of Mozilla website project(s).
Contents
Background
Every year, Mozilla releases the yearly financial documents (audited financial statements and form 990). Most of the news stories around these annual reports focused on the financials and the Google relationship and not Mozilla as a whole.
In 2009, for the first time, Mozilla's PR team reoriented the annual report to focus on where we are in the project, on the people that contribute to the project and an update on the products. Visual assets like photos, videos and graphs were incorporated.
The result was very effective and we got positive feedback from both the press and the Mozilla community.
Goals
- Share financial statements and form 990
- Create a microsite that provides context and compelling content about the people contributing to the Mozilla project, the project itself, and an update on the products
- Garner positive press attention from around the world
- Share the report in 7+ languages
Measurements
- Press mentions
- Page views
Overview
- Prod URL: http://www.mozilla.org/en-US/foundation/annualreport/2011/
- Stage URL: https://www-dev.allizom.org/en-US/foundation/annualreport/2011/
- Code Repo: Github TBD
- L10N Repo: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/ab-CD/foundation/annualreport/2011/
- Code: HTML/CSS/JS Python/Django?
Team
- Product Owner: PR; Shannon Prior
- TPM: Christie Koehler
- Dev Team: Websites team, Steven at silverorange; l10n team, Contractor: Good Corp http://www.goodcorps.com/
- QA: Raymond Etornam
- L10N: Pascal Chevrel
- IRC Channel: #www and #spinzone on irc.mozilla.com
Schedule
- 8/23: Mozilla delivers all content to agency
- 8/24-9/23: Agency to create design and layouts (with 2-3 rounds of review/feedback)
- 9/24: Agency delivers layots (PSDs) to Mozilla
- 9/25-10/29: Prelim webdev, including prep for l10n
- 10/4: String Freeze/Communicate to localizers
- 10/5-10/29: L10n
- 10/29: Ready for QA
- 10/30-11/2: QA + updates
- 11/5: Launch
Press Coverage
Designs
Mockups
Wireframes
User Stories
Bugs
Bugs should be filed with normal visibility; Security bugs should be filed with private visibility.