GuildWiki:No original builds

The Build: namespace of GuildWiki is used to document Flavor of the Month (FotM) PvP builds and easily verifiable PvE running and farming builds. All 'original' builds must reside in the user name space, and will be treated like anything else in the user name space.

Reasoning:
 * If it works and is worth it, it's been done already
 * No popular build has ever originated from GuildWiki. Popular builds are formed elsewhere.
 * A wiki is best used for documenting

The build namespace

 * The build namespace is there to document popular builds, not to be a bed for development.
 * 'Original' builds will be moved to userspace, where the author is in charge of it.
 * The author can put a tag on their build to attract people to test it and give feedback.
 * No voting will take place in the build name space and builds will not be evolved there; The builds section is pure documentation of popular builds.

Advantages

 * No poor builds in the build name space
 * No voting
 * Reduces violations of GW:NPA
 * Enhances the wiki's reputation as a documentation site

Allowed in builds section
Guild Battles: Deemed popular and successful with observer mode. A full team build of 8 players or a working smaller part of a team.

Heroes' Ascent: Deemed popular and successful with Hall of Heroes observer mode and top 100 observer mode (for Global Tournament). A full team build of 6 players or a working smaller part of a team.

Team Arenas and Alliance Battles: Deemed popular and successful by playing in the Team Arenas/Alliance Battles. A full team build of 4 players or a working smaller part of a team.

PvE farming and running: Deemed successful and optimal for the task.

'Original' builds, not allowed in builds section
Random Arenas and Competitive Missions: These will be considered 'original' builds, and will be moved to the user name space, aside from obvious FotM builds (eg. Touch Rangers).

General PvE: These will be considered 'original' builds, and will be moved to the user name space.

Builds in the user name space may be tagged with the tag, which is used to categorise the builds to approppriate categories. Even though the builds exist in the user name space, the template may not be abused to place the builds in unsuitable categories to advertise the build.

Guides, allowed in the main name space
Profession guides: Guides for specific professions and their usual roles.

Role guides: Guides for specific roles in the game such as 55hp tanking, trapping and minion masters. The roles are rarely profession specific.

Build and guide names
Builds should be named according to the name which is used in the game. If no well known name exists, the name must include an important skill or skill combo of the build in question. The profession of the character is placed in front of the name, or in the case of team it is marked accordingly.

Guide names must reflect the profession or role discussed in the article. The guide should be named according to the name used in game.

Examples:

 * Build:N/Me SS
 * Build:Mo/any 55hp tank
 * Build:Team - Underworld duo trap


 * 55hp tank guide
 * Minion master guide
 * Trapping guide