The Fedora Project Wiki has a very low barrier to entry for editors. (For more about wikis and the Fedora Project Wiki in particular, see the Wiki page.) However, there can be a small learning curve when beginning to use wiki, and we have a number of guidelines that all editors should follow. This page provides those guidelines and a few tips to help you get going.
This document is divided in three parts: gaining edit access, basic wiki editing, and more advanced editing.
獲得編輯權限
為了避免惡意用戶損壞 Fedora 專案維基，我們不得不限制一些編輯權限。要獲得編輯維基的權限，您必須按照幾個簡單的步驟。 任何人都可以得到編輯權限。
- 自己熟悉這個頁面上的資訊和這個網頁連結到哪。在這整個維基應該遵循涵蓋基本準則。不遵守這些準則將造成其他志願者不必要的工作，並可能導致撤銷編輯權限。
- 透過 Fedora 帳號系統 完成貢獻者許可協議。 在我們的 自由授權 簽署 CLA 協議賦予 Fedora 專案能夠許可您對於維基的貢獻。這樣確保了您的貢獻將繼續永遠免費為社群使用，修改，和重新發佈，就像 Fedora 發行一樣。參考我們的 法律 條文以獲得更多資訊。依據在 Infrastructure/AccountSystem/CLAHowTo 的說明。
可從 Writing for DocBook using the wiki 得到編寫正式 Fedora 文件的資訊。
Etiquette guidelines
Refer to Help:Wiki rules and etiquette for some general etiquette guidelines on editing the Fedora wiki.
Creating pages
The Fedora Project Wiki is large, and so there is a need to maintain a proper hierarchy and organization. The best way to learn about these is to review Help:Wiki structure and Help:Categories, and then to review the existing layout of the wiki. Our guidelines will help you name your pages in a way that will help them be more readable, translatable, and easier for search engines to find and promote.
Editing with Mediawiki
Refer to Help:Wiki syntax and markup for basic information on how to write in MediaWiki syntax. It's really easy, and the wiki makes it easy for you to create a beautiful page with almost no markup at all.
Getting Help
If ever you have questions about editing the Fedora Project wiki, or if you need help, please feel free to contact the Websites team. They have an IRC channel (#fedora-websites on freenode) and a mailing list (fedora-websites-list) that are both effective for getting the answers you need.
If you would like to do a lot of editing on the wiki, you should consider joining the Websites team.