Help:Page layout
{{AI generated}} from the top.The sections each kind of page has, in order. Citadel Wiki:Style guide says what goes on which page, what comes before the sections and how to write them, and Help:Templates lists every template named here. Leave out a section with nothing to say. A section a page needs that is not listed here goes after the lead, before the listed ones. After Changes, every item, NPC, loot table and area page ends with its navigation box: Template:Navbox items, Template:Navbox NPCs, Template:Navbox loot tables or Template:Navbox breaches.
Items
An item page, such as Railgun or Veskar, has:
- Template:Infobox Item, filled in from the tooltip. An item with quality shows a tab for each quality, opening on STANDARD.
- A lead: what the item is and what it is for.
- Stats and Ability, for a module: what quality changes, and its battery ability.
- Using it, for a consumable: what it does to each thing it can be used on.
- Creation:
{{Creation}}, which shows each blueprint that forges it. - Item sources:
{{Drop sources}}, which lists every page that drops it and whether it always does, then a sentence for each other source, then a Shop locations table: Seller, Location, Price, Notes. - Products, for a material:
{{Products}}, which lists what it goes into. - Variants: artifacts and other items built on it.
- Changes: Template:Changes head, one Template:Changes line for each change, oldest first, and Template:Changes bottom.
New item pages from the Main Page start with these sections.
Ships
A hull's page, such as Seraph or Praetor, has an item page's sections, with Fitting grid (Template:Fitting grid) after the lead, and Quality after Item sources. A hull and an NPC ship that share a name get a page each, such as Orstrog and Orstrog (NPC), with a line at the top of each pointing to the other.
Blueprints
A blueprint's page, such as Railgun Blueprint, has:
- Template:Infobox Item with
type = blueprintand the recipe: the product, each material and how many one job spends, how long a job takes, the uses and the highest research tier. The infobox shows the product's picture. - A lead: what it forges and how a job runs. The infobox already gives the numbers.
- Research: Template:Research table, with what each tier step costs.
- Item sources: Shop locations, then Drops (
{{Drop sources}}). - Changes.
NPCs
An NPC's page, such as Hornet, has:
- Template:Infobox NPC, with what a pilot can see of it: where it is found, when it comes back and the loot tables it draws from. The game shows no NPC's HP or speed as a number, so the infobox gives none.
- A lead: who flies it and what it does.
- Locations: a table of Breach (Breach or war zone when it appears in CLOUD WAKE or THE GALLOWS), Tier and How it appears, and when it comes back.
- Combat: its weapons, defences and behaviour.
- Drops: Always, a table of what its wreck always holds (Template:Drops head, one Template:Drops line with
always=yesfor each, and Template:Drops bottom), then Random loot: which shared loot tables its random loot comes from, linked, and what is special about its loot, such as a small budget or a boss's loot class, in words. The tables' own pages list what they hold. - Changes.
Bosses
A boss's page, such as The Brood Queen, starts with Template:Has strategy and has an NPC page's sections without Combat: its strategy guide holds the fight. A boss without a guide yet, such as Shield of Amnion, keeps the fight in Fighting it, after Locations.
Hubs
A hub's page, such as Greylock, has:
- A lead: whose hub it is and what a pilot does there.
- Getting there: how a pilot reaches it, and who may dock.
- Services: the stash, forge, research, refit terminals, recycler, merchants and quartermasters, and what each does differently here.
- Breaches: Template:Breaches from, which lists the areas breached from it.
- NPCs: the ships that fly there.
- Fighting other pilots: duels.
- Changes.
It ends with Template:Navbox breaches and files itself under Category:Hubs.
Areas
An area's page, such as Kassik's Drift, has:
- Template:Infobox Breach.
- A lead: where it is, what it looks like and what lives there.
- Getting in: who can breach into it, from where, and what it needs.
- Time: when it resets and what a reset changes.
- Leaving: how to extract.
- NPCs: how its tier scales them, a table of Where, NPCs and Returns after, and its vaults.
- Loot: what is special about its loot, its ore and its breach modifiers.
- Fighting other pilots: its rules for fights between pilots.
- Changes.
Loot tables
A loot table's page, such as Turret loot table, has a lead saying which wrecks draw from it, then its drop table: every item it can give, with a note on any that drop only from stronger NPCs or from a set breach tier up. A table made of sections, such as Main loot table, gives each its own heading. The main loot table also explains, before its sections, how loot rolls, without numbers.
Mechanics
A mechanic's page, such as Quality, has a lead saying what the rule is, then a section for each part of it, then where each value comes from.
Strategy guides
A strategy guide is a subpage of the content it covers, such as a boss or an area, and that page starts with Template:Has strategy. A guide, such as The Brood Queen/Strategies, has:
- A lead: what the guide is for, and the tier its numbers are for.
- Requirements: what a pilot needs to get there.
- Recommended setup: damage types, defences and modules that help.
- The content itself, in the order a pilot meets it. A boss's guide gives its parts, such as Her mounts: what can be hit and what breaking each does; then The fight: how it starts, then one heading for each phase; then its weapons and its adds, each under its own heading.
- Tips.
Updates
An update's page, such as Update:Beta Patch 3, lives in the Update namespace under the name the team posted it with, and holds its patch notes as posted. Every update that reached players has a page, so together they tell the game's whole history. A page has:
- Template:Update, with the date it reached players, its kind, a sentence's summary and where the notes were posted.
- The notes, with their headings and lists as posted, thanks lines included, each under the change it follows. Times are given in UTC. Only pings, links, link previews and deploy countdowns are left out. Each change in the notes also goes in its subject's Changes section.
- Announcements, when the team posted any about the update apart from its notes, such as a playtest's schedule or a delay: each under its title, or its day if it had none, with its date and where it was posted.
- For an update the team posted no notes for, such as Update:Alpha, a sentence on when it ran, its announcements if it had any, and Changes with Template:Update changes, which lists what the articles record it changed.
- References:
<references />.
Money making
A method's page, such as Money making guide/Mining, starts with Template:Money making, whose box the table on Money making guide lists. Then a lead, then sections for how it works and how fast the game lets it go, where it is done, what boosts it, and Risks last.