Confirmed users
693
edits
WebsitePlan: Difference between revisions
Jump to navigation
Jump to search
→Rethinking the Mozilla Web Universe
| Line 7: | Line 7: | ||
'''How to fix it:''' | '''How to fix it:''' | ||
*think about our sites as components of a larger network rather than a bunch of individual pieces. | |||
*tell our story effectively by making sure each site has a clear role and distinct focus. | |||
*group related content together so it’ll be where users can find it. | |||
*connect sites more effectively through cross-linking, UI elements, visual palette, etc. | |||
More details: | '''More details:''' | ||
*[http://www.intothefuzz.com/2010/02/11/starting-the-discussion-how-to-make-mozillas-websites-better/ Blog post] | *[http://www.intothefuzz.com/2010/02/11/starting-the-discussion-how-to-make-mozillas-websites-better/ Blog post] | ||
*[http://www.slideshare.net/intothefuzz/rethinking-the-mozilla-web-universe Slides] | *[http://www.slideshare.net/intothefuzz/rethinking-the-mozilla-web-universe Slides] | ||
'''Plan of attack:''' | |||
* step 1: organize mozilla.org back-end | |||
** prepare for l10n | |||
** prioritize and resolve outstanding bugs | |||
* step 2: create Mozilla web universe site map | |||
** recommendation is to bring in an external IA expert to work with internal teams & community | |||
** will need to consider SEO implications as well | |||
* step 3: create unifying site elements | |||
** could include a common footer (with cross-links between the most central sites as identified during step 2), header elements, etc | |||
** again, recommendation is to bring in external firm to work with internal teams & community | |||
* step 4: refine mozilla.org homepage | |||
** [https://wiki.mozilla.org/Mozilla.org/HomepageRedesign/Brief project brief] | |||
* step 5: make decision on primary name for Firefox product site | |||
** mozilla.com? firefox.com? mozilla.org/firefox? | |||
** ultimately, given that we can have multiple URLs pointing to the site, the name probably isn't as relevant as the decision to make it a fully focused Firefox product site. But, it's still a key decision point for everything that follows | |||
* step 6: additional mozilla.org content cleanup | |||
** move "About" content from mozilla.com to mozilla.org | |||
** update additional mozilla.org pages to follow design style of revised homepage | |||
* step 7: Firefox product site redesign | |||
** new look & feel for mozilla.com | |||
** need to confirm with stakeholders as to the full scope (should include related sites that use the same design, like SUMO and blog.moz) | |||
* step 8: Firefox product site testing | |||
** allow time to test and tweak the new design - only show to small % of users until we're convinced it's equaling or outperforming the current version | |||
* step 9: create style guides | |||
** visual and copy guides for mozilla sites | |||
* step 10: integrate add-ons into Firefox product site | |||
** scope and methods TBD | |||