Websites/Taskforce/Proposals/Site Checklist: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ryansnyder (talk | contribs) m (→Open Items) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
= Status = | = Status = | ||
Draft | |||
= Problem = | = Problem = | ||
| Line 11: | Line 11: | ||
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. | 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. | ||
= | = Solution = | ||
The proposed solution is to have an open process for adding items to this checklist -- either items that all sites should follow or items that we recommend all sites consider. At each task force meeting we can discuss adding to this list if there are items up for discussion. | |||
*[ | |||
==Approved Items== | |||
These items have been discussed and approved at previous task force meetings. | |||
* All sites should link to Mozilla's [http://www.mozilla.org/about/policies/privacy-policy.html Privacy Policy]. This is usually done in the footer. | |||
==Open Items== | |||
The following are ideas that can be discussed for adding to the approved list of checklist items. | |||
* References to existing checklists | * References to existing checklists | ||
** [https://intranet.mozilla.org/webtools/webdev/project_init Webdev Project Initiation Form] | ** [https://intranet.mozilla.org/webtools/webdev/project_init Webdev Project Initiation Form] | ||
** [https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist Web QA Project Checklist] | ** [https://wiki.mozilla.org/QA/Execution/Web_Testing/Project_Checklist Web QA Project Checklist] | ||
** [[Webdev:Flux:Steward_Guidelines|Webdev Flux Steward Guidelines]] | |||
* New content | * New content | ||
** Does the site provide a service? If so then don't forget your Terms of Service | |||
** Does the site provide a service? If so then don't | |||
** Life cycle | ** Life cycle | ||
*** Should this site exist forever or for a certain time? | *** Should this site exist forever or for a certain time? | ||
| Line 36: | Line 40: | ||
*** Who will own the site? | *** Who will own the site? | ||
*** Does the site duplicate one of the 100+ existing sites in the community? | *** Does the site duplicate one of the 100+ existing sites in the community? | ||
* | * Metrics opt-out | ||
== Considerations == | == Considerations == | ||
= Related Proposals = | |||
*[[Websites/Taskforce/Proposals/CSS Framework|Taskforce/Proposals/CSS_Framework]] | |||
*[[Websites/Taskforce/Proposals/Common_Footer|Taskforce/Proposals/Common_Footer]] | |||
*[[Websites/Taskforce/Proposals/Domain_Name_Strategy|Taskforce/Proposals/Domain_Name_Strategy]] | |||
*[[Websites/Taskforce/Proposals/Web_Fonts|Taskforce/Proposals/Web_Fonts]] | |||
Latest revision as of 16:21, 20 March 2011
Working Group
FuzzyFox, Stephen and David
Status
Draft
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.
Solution
The proposed solution is to have an open process for adding items to this checklist -- either items that all sites should follow or items that we recommend all sites consider. At each task force meeting we can discuss adding to this list if there are items up for discussion.
Approved Items
These items have been discussed and approved at previous task force meetings.
- All sites should link to Mozilla's Privacy Policy. This is usually done in the footer.
Open Items
The following are ideas that can be discussed for adding to the approved list of checklist items.
- References to existing checklists
- New content
- Does the site provide a service? If so then don't forget 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?
- Who is developing this site? What information do they need?
- Metrics opt-out