Jump to content

Elite Dangerous Wiki:Manual of Style: Difference between revisions

From Elite Dangerous Wiki
Content deleted Content added
Localise template catalogue and editorial guidance for the independent wiki
 
Reconcile Elite Dangerous community rules and Wikipedia-derived editorial guidance for the independent wiki; retain local layout
 
Line 11: Line 11:


[[Project:Editorial guidance|Editorial guidance directory]]
[[Project:Editorial guidance|Editorial guidance directory]]

== Lore, gameplay and player material ==
Distinguish in-universe lore from out-of-universe explanations of the game. Use official names and dated sources for canon. Label player terminology and attributed interpretations. Do not write a faction article in its recruitment voice or present a commander's role-play as the game's history.

Identify Live, Legacy, expansion, platform or test-build differences where they affect the reader. A historical statistic should retain its date rather than silently replacing a current value. Follow [[Project:Future content]] for unreleased features and [[Project:Squadrons]] for player organisations.


[[Category:Guidelines]]

Latest revision as of 19:24, 31 October 2026

Manual of Style provides local editorial guidance for the independent Elite Dangerous Wiki. Apply it alongside community standards and existing local policies.

Names and language

Use the game's established names for ships, modules, systems and features. Follow Project:Spelling and local article conventions. Use sentence case for ordinary headings and preserve the capitalisation of proper names. Prefer a clear explanation to jargon that a new player cannot understand.

Article structure

Begin with a concise definition and the subject's relevance to Elite Dangerous. Group related information under descriptive headings. Keep infobox fields consistent with the article and omit unknown values rather than guessing. Use tables for comparable values and prose for explanations. See Project:Article titles.

Versions, figures and accessibility

Identify historical and platform-specific behaviour explicitly. Include units, dates and a source for changing statistics. Give informative images useful captions and alternative text. Do not convey meaning through colour alone. Preview tables on narrow screens. Separate trivia, speculation and player advice from documented mechanics.

Editorial guidance directory

Lore, gameplay and player material

Distinguish in-universe lore from out-of-universe explanations of the game. Use official names and dated sources for canon. Label player terminology and attributed interpretations. Do not write a faction article in its recruitment voice or present a commander's role-play as the game's history.

Identify Live, Legacy, expansion, platform or test-build differences where they affect the reader. A historical statistic should retain its date rather than silently replacing a current value. Follow Project:Future content for unreleased features and Project:Squadrons for player organisations.