Websites/Mozilla.org/One Mozilla
Contents
APRIL 2012 UPDATE
This is the archived One Mozilla page, covering related projects from 2011 and early 2012. For more current information, please visit the One Mozilla wiki.
Goals
Phase 1. The Merge (March 2011 - August 2011)
Bring mozilla.com (Firefox product site), mozilla-messaging.org (Thunderbird product site), mozilla-europe.org, and mozilla.org (community site) together into a single codebase:
- until August 24, 2011, marketing materials directed users to mozilla.org/firefox, which then redirects users to a .com page)
- In this phase we united codebases and rebranded URLs from major Firefox-focused product pages as .org, an effort to bring clarity to the user experience and overall understanding of Mozilla as a non-profit
Phase II. Build Bedrock & Redesign mozilla.org (September 2011 - current)
- build a real One Mozilla, a single platform where Mozilla.org and Mozilla product sites (Firefox, Thunderbirds, Apps, etc.) can co-exist and share code
- refresh the mozilla.org design to better express mobile-first techniques, updated brand messaging, usability improvements
Overview
Why Build a New Platform?
Mozilla.org is a pretty simple static content site (though, we have a lot of it!), but working on the site has become increasingly hard over the past few years. Here are some of our pain points (some might sound all too familiar to you in your job):
- Mobile, we currently don't have framework for handling mobile pages
- Templates, we currently don't have clear separation of templates and code, which is messy, hard to understand
- SVN, we currently use SVN instead of git and SVN doesn't excel when it comes to tracking features and managing rollouts quickly
- (Here's more on our SVN pains: http://jlongster.com/s/git-transition/)
- Libraries, we currently can't leverage popular libraries of optimizations that other mozilla sites use
Why Bedrock
- Mobile, we will have libraries to handle mobile views of pages with a lot of nice features (keeps track of user's preference, uses templates to reuse code, etc)
- Templates, we will have a powerful templating system: jinja2 (http://jinja.pocoo.org/docs/)
- GIT, we will build on top of git instead of SVN, which allows for easy branching and merging for rolling out (until we create a new workflow that the community weighs in on, localizations will still be kept in SVN - eventually though, Bedrock would take the need to know how to code out of the l10n process, which would be glorious!)
- Libraries, we'll be able to benefit from a number of awesome Python libraries:
- django-mobility, mobile detection/redirection, https://github.com/jbalogh/django-mobility
- jingo, jinja2 template integration with django,jingo-minify https://github.com/jbalogh/jingo jingo-minify
- JS/CSS minifier, https://github.com/jsocol/jingo-minify/
- django-waffle, feature flipper for continuous deployment, https://github.com/jsocol/django-waffle
- django-celery, celery (async task manager) integration with django, https://github.com/ask/django-celery
- django-qunit, quint testing integration, https://github.com/kumar303/django-qunit
- django-nose, nose test runner, https://github.com/jbalogh/django-nose
These libraries are currently being used and actively developed on other Mozilla sites.
Most of this and more can be found at "Current Pain Points with Mozilla.com's Architecture/Platform": http://jlongster.com/s/moz-com-dev/
- Why bedrock: http://etherpad.mozilla.com:9000/why-bedrock
- Hacking todo list: http://etherpad.mozilla.com:9000/bedrock-hacking
- Docs (scarce right now): https://github.com/mozilla/bedrock
Goals
To create and maintain a true "One Mozilla" web universe, where our many diverse product sites are connected by common navigational elements, URL structure and visual identity.
The One Mozilla project should feature nothing less than world class design and content on the front end and be built on the very best code and open technology on the back end. It should be a showcase for the modern web, while never deviating from its mission of serving the Mozilla community.
It should be fully accessible across platforms and devices, and inclusive of the many languages and cultures we support. Our process should be disciplined, transparent and open to anyone who wants to participate, and our methods should be a careful mix of data-driven decision making and expert intuition.
Our web universe should reflect the best of Mozilla, and we never stop trying to make it even better.
Phases
Q4 2011
- One Mozilla Visual Design (wiki):
- Design and code a new mozilla.org responsive visual theme
- Implement and test a functional universal tab for /firefox Bug 629699
- Update mozilla.org/about section to better reflect who we are
- One Mozilla Platform, Bedrock:
- Build first version of platform, focus on l10n workflow
- Prioritize content for ongoing migration conducted by webdev (page-by-page):
- /firefox
- Mozilla Europe
- Mozilla.org
- /firefox
- Communications Plan
Q3 2011
Q2 2011
People
Negotiate - these are the project owners, responsible for going to all the meetings and making the final decisions on things
- James, WebDev Lead
- John, Creative Director/Branding
- Sean Martell, Lead Designer/Branding
- Stephanie Schipper, Mozilla Foundation
Consult - the folks will be very involved in the review & feedback process, but aren't considered 'owners' of the project
- Fred
- CB
- David Boswell, Contributor Engagement
- Asa Dotzler, Firefox
- Matej Novak, Mozilla Creative/Branding
Inform - these people will be directly informed of project updates (design reviews, etc) and their opinions will be sought, but are less involved than the people on the consult level
- Ragavan, Apps
- Thunder, Browser ID
- Pascal Finette, webfwd
- Pascal Chevrel, l10n
- Anne-Marie Bourcier, Thunderbird
- Mike Morgan, Web Dev
- Jason Grlicky, UX
- Ryan Merkley, Mozilla Foundation
- Jane Finette, Engagement & Apps
- Stormy Peters, MDN
- Gervase Markham, Community
- fantasai, Community
- Eric Shepherd, Community
Planning Assets
- Complete Content Inventories for:
- Complete Content Stakeholder Interviews for:
- Mozilla-Europe, Pascal, June 7
- Mozilla Messaging, Rafael, June 8
- Mozilla.org, David Boswell, June 9
- Mozilla.com, John Slater
- L10N Team, Stas, June 9
- Complete Technical Specification/Plan for Rebranding
- Mozilla-Europe, James Long, June 16
- Mozilla Messaging, Rafeal Lebron, June 23
- Mozilla.org, No rebranding required
- Mozilla.com, James Long, June 23
Meetings & Notes
- March 08, 2012
- March 01, 2012
- February 23, 2012
- February 16, 2012
- February 09, 2012
- February 02, 2012
- January 26, 2012
- January 19, 2012
- January 12, 2012
- January 5, 2012
- December 15, 2011
- December 8, 2011
- December 1, 2011
- November 17, 2011
- November 10, 2011
- November 3, 2011
- October 27, 2011
- October 20, 2011
- October 13, 2011
- Phase I. Launch day, August 24, 2011
- Meeting Notes, August 18, 2011 (code freeze!)
- Meeting Notes, August 11, 2011
Meeting Notes, August 4, 2011- Meeting Notes, July 28, 2011
- Meeting Notes, July 21, 2011
- Meeting Notes, July 14, 2011
- Meeting Notes, July 7, 2011
Meeting, June 30. 2011(cancelled)- Meeting Notes, June 23, 2011
Meeting, June 16, 2011(cancelled)- "What is Bedrock" meeting, June 15, 2011
- Meeting Notes, June 9, 2011
- Meeting Notes, June 2, 2011
Bugs
Backend:
Frontend:
- 630964 - [One Mozilla] Integrate designs of www.mozilla.com and www.mozilla.org
- 629699 - [Universal Header] Phase 2
for merged mozilla.org site - https://bugzilla.mozilla.org/show_bug.cgi?id=677305
Feature Requests
Follow Along With Blogs & More
- onemozilla.org
- Other blogs etc. go here :-)
