Citadel Wiki:Style guide
{{AI generated}} from the top.This guide is for anyone who edits the wiki. It says what goes on which page, where on a page it goes, and how to write it. When in doubt, copy a page of the same kind. Where this guide says nothing, follow Wikipedia's Manual of Style. Help:Page layout lists the sections each kind of page has, in order, and Help:Templates lists every template and what it does, stores or shows.
One home for each fact
Every fact has one page that holds it, its home. Other pages show it through a template that reads the home, or say it in a few words and link there. Nobody copies a fact to a second page by hand, because copies drift apart; Wikipedia calls such a copy a content fork. When a fact changes, change it at its home, and every page that shows it follows.
| Fact | Its home | Where else it shows |
|---|---|---|
| What an item's tooltip shows: its type, slot, size, BR, stats and description | The item's infobox | Item tables, through Template:Item list |
| A recipe: the product, the materials per job, the job time, the uses and the highest research tier | The blueprint's infobox | The product's Creation (Template:Creation) and each material's Products (Template:Products) |
| What each research step costs | The blueprint's Research table (Template:Research table) | Nowhere else |
| What an NPC's wreck always holds | The NPC's Drops | The item's Item sources (Template:Drop sources) |
| What a shared loot table can give | The loot table's page, such as Main loot table | The item's Item sources; NPC pages link the table |
| How loot rolls, in words | Main loot table#How loot rolls | Linked from NPC, loot table and item pages |
| A price | The Shop locations table on the page of what is sold | Linked from pages that mention it, such as a hull's page linking its blueprint's |
| How to take on a piece of content, such as a boss, when it has a strategy guide | The guide, a subpage of the content's page, such as The Brood Queen/Strategies | The content's page points to it with Template:Has strategy |
| Where an NPC appears, and how its area scales it | The area's page, such as Kassik's Drift | The NPC's Locations names the areas and links them |
| A rule that many pages use, such as Quality | A page of its own | Linked where it matters |
| A money making method's rates, places, needs and risks | The method's page, in Template:Money making | The table on Money making guide |
A section that sums up a fact another page holds keeps to a sentence or two and links to that page. It never brings a table or a list of numbers across.
Kinds of page
| Kind | What it holds | How it is named |
|---|---|---|
| Item | One item, including modules, resources, consumables, ship hulls and blueprints: what its tooltip shows, how it is made, where it comes from and what it goes into | Its name in the game, in ordinary capitals: Railgun, Railgun Blueprint |
| NPC | One ship the game fields: where it appears, how it fights and what it drops | Its name in the game. One that shares its name with a hull adds (NPC): Orstrog (NPC) |
| Boss | A boss: an NPC page whose strategy guide holds its fight | Its name in the game: The Brood Queen |
| Area | One breach area: getting in, what lives there, its loot and how to leave | Its name in the game: Kassik's Drift |
| Hub | One hub: whose it is, what a pilot can do there and the breaches that start from it | Its name in the game: Greylock |
| Update | One update: its patch notes and announcements as the team posted them, or, when the team posted no notes, when it ran and the changes the wiki records for it | The name it was posted with, in the Update namespace: Update:Beta Patch 3 |
| Loot table | One loot table that many wrecks share: everything it can give | What it holds: Main loot table, Boss loot table |
| Mechanic | One rule that runs through the game | Its name in the game: Quality |
| Strategy guide | How to take on one piece of content, such as a boss or an area: what to bring, how it goes and how to answer what it throws at you | A subpage of the content's page: The Brood Queen/Strategies |
| Money making method | One way to earn | A subpage of the guide: Money making guide/Mining |
| Help and rules | How the wiki works | Help: pages, and Citadel Wiki: pages such as this one |
A thing gets its own page when the game names it and it has facts of its own. Two things with the same name each get a page, with a line at the top of each pointing to the other; a page that only lists what a name can mean is kept for three or more.
Where things go on a page
Every page runs in the same order, top to bottom:
- Notices. Template:AI generated first, then Template:Removed on the page of something the game no longer has, then any other maintenance notice: Template:Cleanup, Template:Incomplete, Template:Outdated, Template:Merge or Template:Delete. A notice about one section goes first in that section instead, and Template:Unverified goes in the text, right after the claim it marks. Citadel Wiki:Maintenance lists them all and what each asks for.
- A pointer to a page with the same name, for a page that has one.
- Template:Has strategy, on a page whose content has a strategy guide.
- The infobox. It holds what the game shows about the thing, and stores it for the pages that show it elsewhere.
- The lead. The name in bold, in the game's capitals, then a sentence or two on what the thing is and what it is for. The lead sums up the page: everything in it is also in the body below, and it holds no strategy and no trivia.
- The body. The sections for the page's kind, in the order Help:Page layout gives. A section with nothing to say is left out. A section that sums up another page links to it.
- Changes. The last section: a table of date, update and change, newest last, with Template:Changes line. Name the update as its page in the Update namespace does, such as Beta Patch 3, so the row links to it.
- The navigation box of related pages: Template:Navbox items on an item page, Template:Navbox NPCs on an NPC page, Template:Navbox loot tables on a loot table page, Template:Navbox breaches on an area page. The first two fill themselves from the infoboxes.
- Categories. The infobox files the page under its own; add any others at the very bottom.
Writing
- Tense and person. Write in the present tense, about the game as it is now. Something the game no longer has keeps its page as a record, in the past tense, under Template:Removed. Articles call the player a pilot; guides and help pages may say you. Never I or we.
- Names. Write every name the game shows as the game shows it, in capitals in the text: RAILGUN, GREYLOCK, HULL BULKHEAD. Titles and links use ordinary capitals, such as
[[Railgun|RAILGUN]]. Use the game's own words for things. - Headings are in sentence case, such as Item sources, and hold no links.
- Links. Link the first mention of anything that has a page, or that should have one: a link to a page nobody has written yet shows red, and tells readers and editors that the page is wanted. Special:WantedPages lists them. Link a name to the title its page would have, such as
[[Calces|CALCES]], or to its section on a page that covers several, such as[[Drone affinity#TITHE PROTOCOL|TITHE PROTOCOL]]. - Numbers. Add a number only when you can see it in the game, in a tooltip, the fitting screen, the HUD, a shop, the forge or another screen, when the team published it in an update's patch notes, or when you can test it yourself in one session: by counting, by timing something with a clock, by comparing two things side by side, or by doing one thing and reading the result. A number worked out from numbers the game shows counts too, such as a boss gun's range: the gun's range in its tooltip, doubled by the TURRET RANGE +100% tag on the boss. Write it exactly as the game shows it, and where the game varies it, give the range you see. Never write about. Drop chances, which take many sessions to count, have their own rule under Drops.
- Facts, not screens. Say what a thing is and does, not where the game shows it: the ACHAMOTH is a HAULER, a CRUISER hull, not a CRUISER hull whose tooltip names its role. Name a screen only to tell a pilot how to do or spot something in play, such as reloading a module from its card on the module bar.
- Mechanics in words. Some numbers the game keeps to itself: chances, multipliers, ranges it does not show. Leave those off the page, apart from drop chances counted as Drops says, and explain what the mechanic does in words instead, such as it fires faster in the OPTIMAL heat zone.
- Drops. List what drops what, and whether it always drops. The game shows no drop chances, so a drop table shows each random drop's chance as Unknown until players have counted it. To give one, count it over many kills, give it as a fraction with the drop line's
chance, such as 1/128, and say on the page's discussion page how many kills and drops you counted, so others can check it and add theirs. A chance from a guess, a few kills or the game's files stays off. Loot odds the team published in patch notes go in the Changes section, with their update. How loot rolls explains how loot works. - Leave out guesses, opinions, a profit an hour, things not yet in the game, and players' names. Trivia goes in only when it is proven, notable and fits nowhere else. Report an exploit or a bug to the team on the Citadel Discord instead of writing it up.
Pages written by AI
Many pages began as drafts an AI wrote. Each starts with the WRITTEN BY AI notice (Template:AI generated) until someone has checked the information and rewritten it in their own words; whoever does that removes the notice. Category:Pages written by AI lists the pages still to check, and taking one on is a good way to start helping.