Websites/Mozilla.org/Roadmap 2011/Q2: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 8: Line 8:
* Create a "why download?" page explaining why people should download and try Firefox
* Create a "why download?" page explaining why people should download and try Firefox
* Add key videos to high traffic pages explaining our brand promise
* Add key videos to high traffic pages explaining our brand promise
* Come up with creative ways to communicate what Mozilla is besides Firefox, and why people should care about Mozilla


= Domain Change  =
= Domain Change  =

Revision as of 22:17, 16 February 2011

Rough list of Q2 projects:

Make our website great

  • Incorporate our new brand promise and brand positioning into all main pages
  • Improve copy to be more readable and scannable
  • Add social proof to key product pages
  • Establish clear differentiators on key product pages
  • Create a "why download?" page explaining why people should download and try Firefox
  • Add key videos to high traffic pages explaining our brand promise
  • Come up with creative ways to communicate what Mozilla is besides Firefox, and why people should care about Mozilla

Domain Change

Planning doc at Mozilla.org/Roadmap 2011/Domain change.

  • change mozilla.com and all subpages to mozilla.org/firefox (and the appropriate subpages)
  • change blog.mozilla.com to blog.mozilla.org
    • bugs:
  • change support.mozilla.com to support.mozilla.org
    • bugs:
  • clean up mozilla.com/mozilla.org duplicate content
    • bugs:

Mozilla.org Redesign

  • bring mozilla.org into greater visual consistency (header, etc) with the Firefox product site
    • Migrate legacy content to allow for redesign and adding of staging site (bug 618077)

Dynamic Content

  • phase 2

Universal Footer

  • joining the sites

Drumbeat & Thunderbird

  • Build out mozilla.org/drumbeat section
  • Start with mozilla.org/thunderbird transition

Regional Community Sites

  • cleanup



Web Team Work Week

Website workweek in Mountain View to gather as a team and tackle such projects as:

  • Work on the domain name change as a group
  • Roadmap planning - architecture and technical assesments
  • Triage the bug backlog - currently 400 open bugs
  • Much, much, more

Either combine or connect this to the all-hands work week in April, depending on how much open work time we'll actually have during that week. Tentative dates for company wide all-hands is: April 4-8 or April 18-22.