Participation/Projects/Leadership toolkit/Content Development Standards

From MozillaWiki
Jump to: navigation, search

Please find the most recent copy of standards, workflow and templates for content development in this document.


  1. Mozilla team requests skill resource.
  2. An issue is opened on Github.
  3. Github issue is assigned to content developer, who then proposes learning outcomes and other details via content template.
  4. Mozilla team reviews proposed content & approves or returns with feedback for another iteration.
  5. Content is developed using best practices, and submitted for QA review.
  6. Content is approved and posted to website, but website administrator.
  7. Content is tested by working group team member in their community.
  8. Content is iterated-on based on feedback from initial testing, and assessment + surveys built into content.