Participation/Projects/Leadership toolkit/Content Development Standards: Difference between revisions
< Participation | Projects | Leadership toolkit
Jump to navigation
Jump to search
(Created page with " Please find the most recent copy of standards, workflow and templates for content development [https://docs.google.com/document/d/1bH75guW0A-CQMNKjKHURFI1Ehl62JKIWp7PijLlzSNs...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Please find the most recent copy of standards, workflow and templates for content development [https://docs.google.com/document/d/1bH75guW0A-CQMNKjKHURFI1Ehl62JKIWp7PijLlzSNs/edit# in this document]. | Please find the most recent copy of standards, workflow and templates for content development [https://docs.google.com/document/d/1bH75guW0A-CQMNKjKHURFI1Ehl62JKIWp7PijLlzSNs/edit# in this document]. | ||
=== Workflow === | |||
# Mozilla team requests skill resource. | |||
# An issue is opened on Github. | |||
# Github issue is assigned to content developer, who then proposes learning outcomes and other details via content template. | |||
# Mozilla team reviews proposed content & approves or returns with feedback for another iteration. | |||
# Content is developed using best practices, and submitted for QA review. | |||
# Content is approved and posted to website, but website administrator. | |||
Revision as of 22:28, 14 December 2016
Please find the most recent copy of standards, workflow and templates for content development in this document.
Workflow
- Mozilla team requests skill resource.
- An issue is opened on Github.
- Github issue is assigned to content developer, who then proposes learning outcomes and other details via content template.
- Mozilla team reviews proposed content & approves or returns with feedback for another iteration.
- Content is developed using best practices, and submitted for QA review.
- Content is approved and posted to website, but website administrator.