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

m
No edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Working Group  =
= Working Group  =


[http://www.wduyck.com FuzzyFox]  
[http://www.wduyck.com FuzzyFox], Stephen and David


= Status =
= Status =


early days / concept
Draft


= 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 ==
= 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.


*[[Websites/Taskforce/Proposals/CSS Framework|Taskforce/Proposals/CSS_Framework]]
* 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.
*[[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]]


= Solution  =
==Open Items==


Combine existing checklists from Webdev, QA, etc. and add new content as needed.
The following are ideas that can be discussed for adding to the approved list of checklist items.


* [https://intranet.mozilla.org/webtools/webdev/project_init Webdev Project Initiation Form]
* References to existing checklists
* QA has a checklist?  Think sdonner mentioned one
** [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]
** [[Webdev:Flux:Steward_Guidelines|Webdev Flux Steward Guidelines]]
* New content
* 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 forget 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 [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?
* 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]]
1,241

edits