1,365
edits
(fix my sumo contact address) |
(add different ways to contribute) |
||
| Line 3: | Line 3: | ||
# Go to the [http://support-stage.mozilla.org/ staging site], and create an account. | # Go to the [http://support-stage.mozilla.org/ staging site], and create an account. | ||
# Go to the [[Support:Alpha_Article_Tracking|Alpha Article Tracking page]], where you can find a list of articles, we'd like created for the first alpha version of the knowledge base. | # Go to the [[Support:Alpha_Article_Tracking|Alpha Article Tracking page]], where you can find a list of articles, we'd like created for the first alpha version of the knowledge base. | ||
== Ways to Contribute == | |||
=== Creating content === | |||
# If you find an article on the list, that has not been assigned, you can write it yourself. | |||
# Once you've decided on an article you'd like to create, assign the article to your self, by putting your name and email address beside the article, under the "Assigned-to" column. | # Once you've decided on an article you'd like to create, assign the article to your self, by putting your name and email address beside the article, under the "Assigned-to" column. | ||
# Read the [[Support:Best_Practices_for_Support_Documents|best practices for support documents page]] and [[Support:Style_Guide|style guide]], for a good understanding of how to approach the article. The title of the article is up to you. | # Read the [[Support:Best_Practices_for_Support_Documents|best practices for support documents page]] and [[Support:Style_Guide|style guide]], for a good understanding of how to approach the article. The title of the article is up to you. | ||
# Once you've started working on the article, update the status column of of that article, on the article tracking page. | # Once you've started working on the article, update the status column of of that article, on the article tracking page. | ||
# When you've completed the article, submit the article for review. | # When you've completed the article, submit the article for review. | ||
=== Review accuracy of information === | |||
Go through articles that have already been created, and review the information in them to make sure it is accurate. | |||
=== Review compliance with best practices guide === | |||
The [[Support:Best_Practices_for_Support_Documents|best practices for support documents page]] was created to help make all support articles as user-friendly as possible. You can go through the articles already created, and make sure they comply with the Best Practices for Support Documents guide. | |||
=== Proofreading === | |||
Even if you don't know much about Firefox, you can help by proofreading the articles already created, focusing on grammar, spelling, punctuation, etc., in accordance with our [[Support:Style_Guide|style guide]]. | |||
=== Marking up articles with tikiwiki code === | |||
A lot of contributors may not know tikiwiki markup, at first, which means that many article submissions will not be written in tikiwiki format. Anyone who is familiar with tikiwiki, regardless of Firefox knowledge, can help out, by going through submitted articles, and marking them, to work in tikiwiki. | |||
=== Create screenshots for articles === | |||
Screenshots always help users understand articles better; however people who write articles may not know how to create a screenshot. If you know how to create a screenshot, you can go through the articles already created, and add screenshots, where you feel is most helpful. | |||
== Joining the community == | == Joining the community == | ||
edits