Websites/Taskforce/Proposals/Site Checklist: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 26: | Line 26: | ||
* New content | * New content | ||
** Make sure there is a privacy policy link in the footer of every page | ** Make sure there is a privacy policy link in the footer of every page | ||
*** [http://www.generateprivacypolicy.com/ Great site to help automate this for the most part] | |||
** Does the site provide a service? If so then don't for get your Terms of Service | |||
** etc. | ** etc. | ||
* Life cycle | * Life cycle | ||
** Should this site exist forever or for a certain time? | ** Should this site exist forever or for a certain time? | ||
** After that time what happens -- retire, archive, turn off... | ** 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 [https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy domain name strategy]? | |||
** Who will own the site? | |||
** Does the site duplicate one of the 100+ existing sites in the community? | |||
== Considerations == | == Considerations == |
Revision as of 22:23, 6 January 2011
Working Group
FuzzyFox, Stephen and David
Status
early days / concept
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.
Related Proposals
- Taskforce/Proposals/CSS_Framework
- Taskforce/Proposals/Common_Footer
- Taskforce/Proposals/Domain_Name_Strategy
- Taskforce/Proposals/Web_Fonts
Solution
Combine existing checklists from Webdev, QA, etc. and add new content as needed.
- Webdev Project Initiation Form
- QA has a checklist? Think sdonner mentioned one
- 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
- etc.
- 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?
- Who is developing this site? What information do they need?