Websites/Taskforce/Proposals/Site Checklist: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 9: Line 9:
= Problem  =
= Problem  =


There should be some sort of guideline that new sites follow, and in turn, a set of resources, for new Mozilla related websites. This will help achive an ease of navigation, and movement between Mozilla sites for the end users.  
There should be some sort of guideline that all Mozilla sites follow, and in turn, a set of resources, for Mozilla related websites. This will help achive an ease of navigation, and movement between Mozilla sites for the end users.  


== Related Proposals  ==
== Related Proposals  ==

Revision as of 20:43, 13 January 2011

Working Group

FuzzyFox, Stephen and David

Status

early days / concept

Problem

There should be some sort of guideline that all Mozilla sites follow, and in turn, a set of resources, for Mozilla related websites. This will help achive an ease of navigation, and movement between Mozilla sites for the end users.

Related Proposals

Solution

  • References to existing checklists
  • New content
    • Make sure there is a privacy policy link in the footer of every page
    • Does the site provide a service? If so then don't for get your Terms of Service
    • Life cycle
      • Should this site exist forever or for a certain time?
      • After that time what happens -- retire, archive, turn off...
    • Site development
      • Who is developing this site? What information do they need?
        • Give the developer as much information as you can, idea history, target audience, must have requirements, etc..
      • Do you need a whole new domain? or just a small area that fits with the new domain name strategy?
      • Who will own the site?
      • Does the site duplicate one of the 100+ existing sites in the community?
  • Legal Requirements
    • to come

Considerations