WebsitePlan: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 20: Line 20:
(caveat #1: this is intended to be the starting point for discussion, not a fully fleshed-out project plan; caveat #2: some of these events can happen concurrently, so the list isn't as linear as it may appear.)
(caveat #1: this is intended to be the starting point for discussion, not a fully fleshed-out project plan; caveat #2: some of these events can happen concurrently, so the list isn't as linear as it may appear.)


* step 1: organize mozilla.org back-end (in progress, complete for May?)
* step 1: organize mozilla.org back-end '''[in progress, complete for May?]'''
** prepare for l10n
** prepare for l10n
** determine which outstanding bugs are relevant, then prioritize and resolve
** determine which outstanding bugs are relevant, then prioritize and resolve
Line 33: Line 33:
** recommendation is to bring in an external IA expert to work with internal teams & community
** recommendation is to bring in an external IA expert to work with internal teams & community
** will need to consider SEO implications as well
** will need to consider SEO implications as well
* step 3: create unifying site elements
* step 3: refine mozilla.org homepage '''[end of May(design); end of June (webdev/qa)]'''
** 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]
** [https://wiki.mozilla.org/Mozilla.org/HomepageRedesign/Brief project brief]
* step 5: make decision on primary name for Firefox product site
* step 4: make decision on primary name for Firefox product site '''[end of May]'''
** mozilla.com? firefox.com? mozilla.org/firefox?
** 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
** 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
* step 5: additional mozilla.org content cleanup
** move "About" content and other [[Mozilla.org/Content_overlap|duplicated pages]] from mozilla.com to mozilla.org
** move "About" content and other [[Mozilla.org/Content_overlap|duplicated pages]] from mozilla.com to mozilla.org
** update additional mozilla.org pages to follow design style of revised homepage
** update additional mozilla.org pages to follow design style of revised homepage
* step 6: 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 7: Firefox product site redesign
* step 7: Firefox product site redesign
** new look & feel for mozilla.com
** new look & feel for mozilla.com
797

edits

Navigation menu