Rise of the Reds Wiki
Advertisement

This page contains the Rise of the Reds Wiki's article layout guideline. It describes how content should be arranged on an article page to be clear and exhaustive.

  • Guidelines describe desired etiquette and common practice in the creation, editing and organization of articles on this wiki.
  • Any registered editor is free to edit this page to improve its readability as long as the essence of the article remains unchanged.
  • If you would like to suggest content changes or propose a new policy or guideline, please use the wiki discussion forum.
  • See the policies and guidelines page for an overview of this wiki's policies and guidelines.

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: Ranger

In general, articles should have the following sections, in the following order (bold elements are a must-have):

  • UnitBox template: Infobox containing key information
  • Introductory sentence: short sentence providing the name, type, affiliation and brief information.
  • Lore: section explaining lore-related stuff
  • Abilities: a list of active abilities possessed by the unit or structure
  • Add-ons: a list of add-ons (individual upgrades) possessed by the unit or structure
  • Overview: strictly gameplay-related section, describing the unit as it actually behaves in the game as well as its tactics and counters, if available
  • Assessment: the unit's pros and cons.
  • Quotes: a list of the unit's quotes; not needed on structures and units that do not speak
  • Gallery: all images related to the unit, such as renders, cut content snapshots, concept art etc. go here
  • Trivia: Miscellanous notes that don't fit anywhere else; to be used sparingly
  • 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
Advertisement