1,365
edits
Support:PRD: Difference between revisions
Jump to navigation
Jump to search
m
→Content Creation
| Line 60: | Line 60: | ||
New documents | === New documents === | ||
Volunteer writes documents and assigns priority for editor review | Volunteer writes documents and assigns priority for editor review | ||
| Line 66: | Line 66: | ||
Articles are required to be reviewed, before going live. As our community grows, and we have more reviewers, we will have two separate editorial approval processes: content and style (content can be published initially if correct, even if not style guide needs to be implemented) | Articles are required to be reviewed, before going live. As our community grows, and we have more reviewers, we will have two separate editorial approval processes: content and style (content can be published initially if correct, even if not style guide needs to be implemented) | ||
Existing documents / edits | === Existing documents / edits === | ||
Minor (spelling, grammar, etc): Push live | Minor (spelling, grammar, etc): Push live | ||
| Line 73: | Line 73: | ||
Style Guide | === Style Guide === | ||
All Firefox support documents should be written for an audience of a slightly below average internet user (doesn’t read blogs—or at least wouldn’t know one if he saw one) and take the tone of a friendly, helpful community volunteer. | |||
*Develop style guide for How To’s and for Troubleshooting docs | *Develop style guide for How To’s and for Troubleshooting docs | ||
** include requirements for any visuals (screenshots, flash/video, etc) | ** include requirements for any visuals (screenshots, flash/video, etc) | ||
Feedback system | === Feedback system === | ||
All articles will have a poll system to determine if the article is useful to users. Users are strongly encouraged to add comments on why something was not helpful, or what information would help them answer the question. | |||
Recognition of volunteers | === Recognition of volunteers === | ||
If user writes highly-rated article, we want to recognize their success by giving them more power to edit articles without review, and automatically approve articles they have reviewed. | |||
==Technical requirements== | ==Technical requirements== | ||