Feed The Beast Wiki:Using the FTB Wiki as an official resource

The Developer-appointed curator program (DACP, da-sap (/deɪ.ˈsæp/) ) is a "program" allowing mod authors to appoint editors to document their mod/mods on the Feed The Beast Wiki. A mod author can be self-promoted, if desired. The developer-appointed mod curator (often shortened to dev appointed mod curator, dev appointed staff, and sometimes mod curator, although the later can refer to any staff documenting a mod) is considered a form of wiki staff.

Why host your documentation here?
Why should you host your documentation here, rather than in a forum post, website, or an independent wiki? There are a few reasons:
 * Forum post: forum posts should have at least some documentation in them, but overall they are nasty as the be-all and end-all form of documentation for medium-sized or large-sized mods. Most forums have size restriction for posts, and using a series of posts generally makes a mess. Also, forum posts usually have restrictions in the forum markup, and are very difficult to navigate.
 * Website: websites aren't easily editable by users/fans. This point can also extended to the forum post. Although a GitHub.io website can be by forking the repository, this is not something that the average contributor would know how to do, or even want to learn how to do.
 * Having your documentation editable by anyone, essentially being a wiki, is about always the best route. Wikis allow anyone to contribute to your documentation, sometimes letting the documentation write itself, and allowing for mistakes to be easily fixed, and for communities to be built. Another point is that wikitext is much simpler then HTML, and allows for more with less.


 * Independent wikis: independent wikis start from the ground-up. Although it may be fun to craft templates and guidelines, the Feed The Beast Wiki already has a very successful system going; you don't need to worry about making new templates, or about a manual of style, you can just jump in and start editing! Additionally, independent wikis, particularly those of less-popular mods, often have issues being maintained- vandalism is not always reverted quickly, if reverted at all. The FTB Wiki Staff is made of multiple users that are always quick to respond to situations (if you want to test us without vandalizing, throw us a message on our noticeboard).
 * Another thing to note is that contributing to the Feed The Beast Wiki is absolutely free; many independent wikis are self-hosted to avoid the Wikia-hell, often costing the owner a few bucks. Although there are many free wiki-hosting platforms, many are slow, have too many ads, or are inflexible.
 * Another point is that a "universal" wiki, which the Feed The Beast Wiki strives to be, allows for easier documentation of addons and crossmod features; rather than linking to other wikis or other sources of information, you can simply point to a page in this wiki.

Moving wikis
If desired, you can move your documentation from an independent wiki, website, forum post, etc, to the FTB Wiki. However, this is not as simple as just copy/pasting information over (or at least when done right). There are a few things needed:
 * You need to have permission to do so. This is the most important part. If it's not written by you, you'll definitely need to ask the writer before moving it over.
 * You need convert the pages' templates (or lack of templates) to the FTB Wiki's templates.
 * You need to make the articles/pages' tone appropriate for the FTB Wiki. This doesn't really apply as much for guides, but regular articles are required to be encyclopedic. The most common example of an article being unencyclopedic is using the word "you" - this can usually just be replaced with "the player" or "a player".

Appointing someone
As a mod author, you can appoint anyone to document your mod here, including yourself. Please make sure this person is someone that you are sure will document and maintain the mod documentation; someone who has some experience with your mod, and maybe experience with wikis and/or documentation, are be preferred. Also keep in mind the FTB Wiki Staff (and you, the mod author) reserve the right to kick the appointee if they don't do anything. If you want to appoint someone, lastly make sure you have their approval, and put a request on the Staff's noticeboard. A basic 3-day vote is required for a user to be promoted to developer appointed staff.

Disclaimer
Using the FTB Wiki as your official wiki does not mean the FTB Wiki Staff will be liable for the documentation of your mod. The FTB Wiki Staff will try their best to maintain your documentation with the current standards of the wiki, and will try their best to undo vandalism and the insertion of false information and the like, and will try their best to assist the appointee as needed, but they are not required to do any of those. The FTB Wiki Staff will try their best to assist with the documentation of your mod, but it is the job of the appointee to update and create the documentation of your mod, not the FTB Wiki Staff.

Current list of developer-appointed mod curators

 * 's mods: ,
 * 's mods:
 * 's mods:
 * 's mods:
 * 's mods:
 * / and :
 * and :
 * 's mods,, and :
 * 's mods,, and :