| |||||||||||||||||||||||||||||||||||||||
| This page contains the Command & Conquer Wiki's article layout guideline. It describes how content should be arranged on an article page to be clear and exhaustive.. | |
 |
|
On structure[]
One of the most important parts of wiki editing is how to structure an article. Structure dictates what information the reader reads and when he or she reads it. It can influence what people contribute, where they put it and how it is written. Good structure is likely to produce high quality articles.
Organize sections in an article in a hierarchical structure like you would an outline. Try using a shallow structure rather than a deep one. Having too many nested sections usually leads to a confusing or unreadable article.
Unit and building articles[]
- Example: Rifleman squad (Tiberium Wars)
In general, unit and building articles should have the following sections, in the following order (bold elements are a must-have):
- Games template: provides a quick visual overviews of games in which the object is featured and/or mentioned
- UnitBox template: Infobox containing key information; abilities and upgrades should feature their icons, standardized to 20 pixel (20px) width
- Introductory sentence: short sentence providing the name, type, affiliation and game in which the object appears.
- Background: section explaining the history, equipment, weapons and all other lore-related stuff is explained.
- Game unit/building/effect: strictly gameplay-related section, describing the object as it actually behaves in the game, noting advantages, weaknesses etc.
- Abilities: any user-controlled abilities, together with their icons (standardized to 60px width).
- Upgrades: any applicable upgrades, together with their icons (standardized to 60px width).
- Appearances: section for any significant appearances the object has made in the campaigns. They may include when the object is first introduced to the player, or first buildable by the player or enemy.
- Notes: miscellaneous notes that do not fit anywhere else; to be used sparingly.
- Behind the scenes: section for noting cut content, changes that occurred during development etc.
- Gallery: all images related to the object, such as renders, cut content snapshots, concept art etc. go here.
- Videos: all videos related to the object go here.
- References: the references heading, together with the <references/> tag should be placed at the end of the article if any <ref> tags are used.
- Navbox: any applicable navboxes go at the end of the article, but before categories.
- Categories: to be placed at the end of the article; see this guideline for details on categorizing articles.
Character articles[]
- Example: Kane
- Games template: provides a quick visual overviews of games in which the character is featured
- CharBox template: Infobox containing key information about the character
- Introductory sentence: short sentence providing the name, affiliation, and role of the character
- Background: section detailing the character's background and motivations
- Biography: section detailing the biography and character development
- Personality: section detailing the character's personality
- Selected quotes: list of notable quotations by the character
- Behind the scenes: section for noting the character's actor/actress, cut content, changes that occurred during development etc.
- Notes: miscellaneous notes that do not fit anywhere else; to be used sparingly.
- Gallery: all images related to the character go here
- Videos: all videos related to the character go here
- References: the references heading, together with the <references/> tag should be placed at the end of the article if any <ref> tags are used
- Navbox: any applicable navboxes go at the end of the article, but before categories
- Categories: to be placed at the end of the article; see this guideline for details on categorizing articles
Mission articles[]
- Example: Lone Guardian
- Games template: provides a quick visual overviews of games in which the mission is featured
- WarBox/MissionBox template: Infobox containing key information and metacampaign; the WarBox template should be used for main entry games in which the mission is part of a story-driven campaign, while Infobox mission may be used for missions from mobile games and tutorial missions
- Introductory sentence: short sentence providing the name, player faction, order and game in which the mission is featured in
- Briefing: official mission briefing provided in the game
- Background: description of the events leading up to and the causes of the mission
- Key units: Units (or superweapons) that are key throughout the mission; this may include controllable units that are introduced to the player; in Red Alert 2 and Generals, they are the units presented in the loading screen of a mission
- Events: description of the events that occurred in the mission
- Aftermath: description of the events that occurred as a result of this mission
- Walkthrough: a walkthrough on completing the mission; be sure to be succinct on details
- Notes: miscellaneous notes that do not fit anywhere else; to be used sparingly
- Gallery: all images related to the mission, such as cut content and screenshots, go here
- Videos: all videos related to the mission, such as briefings and cinematics, go here
- References: the references heading, together with the <references/> tag should be placed at the end of the article if any <ref> tags are used
- Navbox: any applicable navboxes go at the end of the article, but before categories
- Categories: to be placed at the end of the article; see this guideline for details on categorizing articles
Mod articles[]
- Example: Twisted Insurrection
- Games template: provides a quick visual overview of the game that the modification is of
- GameBox template: Infobox containing key information on the mod
- Introductory sentence: short sentence providing the name and what game is the mod is of
- Overview: section providing a general description of the mod
- Gameplay: section explaining the gameplay of the mod
- Plot/Synopsis: description of the mod's story
- Development: section detailing the development of the mod
- Notes: miscellaneous notes that do not fit anywhere else; to be used sparingly
- Gallery: all images related to the mod, such as screenshots and promotional artwork, go here
- Videos: all videos related to the mod, such as trailers, go here
- References: the references heading, together with the <references/> tag should be placed at the end of the article if any <ref> tags are used
- Mods navbox: to be placed at the end of the article, but before categories
- Categories: to be placed at the end of the article; see this guideline for details on categorizing articles
Transcripts[]
- Example: Transcript:Lone Guardian
- Games template: provides a quick visual overviews of games the transcript is for
- TranscriptBox template: provides a quick visual overview of the subject matter being transcribed
- Introductory sentence: short sentence providing the cutscene or mission being transcribed and what game is it from
- Introduction: this section includes the transcript of the introductory cutscene
- Mission selection/Loading screen: includes the text present on mission selection or loading screen segments
- Briefing: includes the text briefing
- Mission script: includes the transcript of the in-game dialogue and text present
- Completion: includes the transcript of the cutscene that occurs upon mission completion
- Debriefing: includes the text debriefing
- Ending: if the mission is the final one of the campaign, this section includes the transcript of the ending cutscene
- Transcript: for pages exclusive to cutscenes, this section includes the whole transcript of the cutscene
- References: the references heading, together with the <references/> tag should be placed at the end of the article if any <ref> tags are used
- Navbox: any applicable navboxes go at the end of the article, but before categories
- Categories: to be placed at the end of the article; see this guideline for details on categorizing articles