MANUAL OF STYLE
The Manual of Style is the style guide for the DOORS Wiki articles, templates, categories and user pages. This page describes the guidelines that should be followed at all times, especially when there is confusion or doubt on what should be done relating to specific pages, categories, templates and user pages.
The Manual of Style was last revised on 9 July 2025. It is subject to change at anytime.
Orthography
The preferred orthographic (language) variation of English is American English. This applies to the spelling of words (center not centre and favorite not favourite) and grammar of sentences (burned not burnt). Vocabulary differences (such as autumn and fall) can be excused. For more examples refer to this guide on Wikipedia.
Wikitext
This is the markup language that makes up all articles, templates, categories and user pages on Fandom Wiki's, it is a mix of XML and HTML. For help on using Wikitext on the DOORS Wiki please see this article.
Templates
Templates make formatting pages easier, they are located within a separate namespace from the main articles they are being used on, to call a template you utilise two of each of the curly braces/brackets; { and }, you then place the name of the template you are calling between the curly brackets/braces and fill out the required information if the template has parameters.
Infoboxes
Infoboxes (also known as Portable Infoboxes) are specialized templates that display organized content on the right-hand side of a page with important information about the content on the page it's being utilized on, the required formatting for Portable Infoboxes can be seen utilized on this template page.
Documentation
Template Documentation is located on the /doc subpage namespace for a template (Template:Entities/doc not Entities/doc), these articles must always be organized as a "Non-article" template type.
Icons
Icons are a list of small icons, with each appropriate icon being chosen in the template's parameter from said list. They should be shown to the left side of the appropriate text. Additional parameters can manipulate the icon's size, link direct and hover caption. For more information about icons, see the {{Icons}} documentation.
Article Structuring, Titles and Subtitles
This section will go into detail about how articles should be structured and how sections and subtitles are to be properly formatted.
Typefaces
This section will go into detail about the usage of various typefaces. Mentions of typefaces can also be found later into the MoS. Any use that is not included in each typeface should be avoided.
Bold
Bold text ('''Bold''') is reserved for:
- The first mention of the title of an article
Headers are automatically bolded with the wiki's CSS, manually bolding is not necessary.
Italics
Italicized text (''Italics'') is reserved for:
- The name of the game DOORS
- Mentions of the title of an article, excluding the first bolded mention
- The game's soundtracks
Note that only the name of the article should be in italics (ex. Figure's instead of Figure's or the Hotel instead of The Hotel.
Links
To prevent articles from being orphaned and obscure, all mentions of possibly pre-existing wiki articles should be linked to said article to allow for more accessibility through the wiki. The only time where a link shouldn't be used is when a link has already been provided to the same article under the same heading to prevent multiple linking.
External site linking
Providing links to websites outside of FANDOM is heavily discouraged. You should try to look for articles in other FANDOM wikis and provide a link to there via interwiki links. More information about interwiki links can be found here.
Topic naming
The title of the article (hereafter 'topic' for this part) is to be mentioned and bolded in the initial description of the article. Any further uses of the topic's name is to be italicized.
Gallery
Whenever a relevant file is meant to be in an article, a gallery is where we put them in. The usual way of making a gallery is by calling the gallery tag and its intended width with the files inbetween and their respective caption separated with a pipe. The following is an example from a part of the Seek article:
<gallery widths="190"> Seek Eye.png|One of Seek's eyes. Old Seek.png|The old model of Seek. SeekJumpscare.gif|Seek's jumpscare. SeekJumpscare1.gif|Seek's hands grabbing the player. </gallery>
Files should not have File: as usual, they are shown in the gallery regardless. In cases of videos, however, they should be put below the gallery. Galleries do not support any video format.
Lists
When an article needs to show several items (such as trivia, notes or bugs), we use a list. To make a list, use the list tag and add each item one after the other. Here's an example from part of the Seek article:
* ''Seek'' is not an anatomically correct human figure, but rather a mound of black slime that tried taking the shape of one, with one of ''Seek''<nowiki/>'s eyes being planted on the face.
** According to [[RediblesQW]], ''Seek'' would struggle more to turn into objects that are constantly affected by collisions, such as a chair (that wouldn't work, due to it being made of black slime) and a pole, that would probably just fall.{{Cite|https://discord.com/channels/458441314023899159/1006982064458960916/1110151453038886984%7CQ: "Okay so like can Seek can form any shape or form it likes??" A: "well not anything, it still has to make structural sense with being slime, like it couldnt be a chair or something imagine trying to sit on a chair make of playdoh"; "or a pole would probably just flop over"|RediblesQW|Discord}}
** ''Seek'' and the black slime used to be the same model, as was evidenced by the black slime peeking under ''Seek''s feet.
* It may be the case that, canonically, ''Seek'' is constantly stalking the players and their progress.
* ''Seek'''s arms either kill the player by strangling them or pull them out of a window. However, for the latter to be true, the Grand Hallway has to be several yards above ground for fall height to be deadly.
Each list item should have a space between the text and the asterisk(s).
Section Headers
Page titles
Page titles (including infobox titles) are normally written in title case (List of Entities), not sentence case (List of entities) or proper case (List Of Entities). Only the first letter of a major word or proper-noun should be capitalized, unless specifically spelt otherwise in-game (such as Lock Puzzle Solution Paper).
Infoboxes
Depending on the type of page you are creating varies on the type of infobox you require. All values should correspond to one within the required infobox. For example, the Figure page:
{{Entities
|title = Figure
|image = Figure.png
|damage = {{Icons|Instakill}} Instant Death (Jumpscare)
|date_added = August 10th, 2022
|creator(s) = RediblesQW
}}
The title in the infobox must generally be the same as the title of the page, the only exception is when a page has a special character within its name or an underscore. There should be a space before and after each equals sign.
The infobox and its parameters should not be cramped into a single line, instead with each parameter spread out to allow easier reading of parameter values like the example above. A cramped infobox can be seen here:
{{Entities|title = Figure|image = Figure.png|damage = {{Icons|Instakill}} Instant Death (Jumpscare)|date_added = August 10th, 2022|creator(s) = RediblesQW}}
Infoboxes should be kept short, as they should be a brief summary of the article and not contain the majority of the article itself, and infoboxes should pertain the the main game of DOORS, ultimately excluding non-canon floors/events and modifiers as much as possible.
Images
Images featured in an infobox should be a quick overview of the subject of the article. At max, an article's infobox should contain 3 images. An additional image should only be added if the subject has a significant appearance change between the two different forms. Non-current versions of the subject should go in the Gallery section.
Captions of the image should label each image accordingly, and not use unnecessary text such as (Current), (The Hotel), (Old), etc.
Floor infoboxes
Floor Infoboxes should be a brief outline of the floor, containing the main sounds heard throughout the floors. Examples could be doors opening and main background ambience. Other sounds related to this floor should be found in an Audio section, or if the sound is relating to an entity, on their respective page.
Location infoboxes
Location infoboxes should follow the same rules as floor infoboxes, but additionally should not list every possible entity in any other version of the game besides the current cannon version without modifiers. For example, in a Hotel room, Rush should be on the list of entities, but A-60 should not, as it is exclusive to a run with modifiers enabled in the hotel. Also, avoid entities which can spawn in previous rooms. For example, if Sally can't spawn in the room but can come from the previous one, she shouldn't be listed.
Entity infoboxes
Entity infoboxes should be a brief overview of the entities behavior in a normal run of DOORS. This means that any sounds, damage or images from a non-canon event/floor should not be listed in the infobox, and should instead be listed under a heading in the page, or exclusively on the non-cannon event/floor.
As stated above, an entity should only have multiple images in their infobox if they have multiple significant forms. For example, Hide would have two images, as it has a physical appearance in The Mines, and a non-physical appearance in The Hotel.
Headings
Headings (including sub-headings) are to be used the same way as page titles but written in sentence case instead of title case (Related achievements not Related Achievements). They shouldn't be lengthy as they can unnecessarily expand the Table of Contents. Each main heading comes with an icon that should be appropriate to what the heading entails.
Across articles, the order of headings should remain the same for a good consistency throughout the wiki. This standardized order is as follows:
Entity articles
- Appearance
- Behavior
- Notes
- Abilities (optional)
- Strategy (optional)
- Death messages (lethal entities only)
Game mechanics articles
- Overview
- Notes
Items articles
- Appearance
- Usage
- Pros and Cons
- Pros
- Cons
Location articles
- Overview
- Walkthrough (optional)
- Map (optional)
Main Floors articles
- Overview
- Entities and Hazards
- Main Entities
- Recurring Entities
- Miscellaneous Entities
- Hazards
- Limited Entities and Hazards
- Puzzles
- Room Mechanics
- Special Locations
- Doors
- In-game soundtrack
Sub-Floors articles
- Overview
- Entities and Hazards
- Unique Entities
- Non-Exclusive Entities
- Puzzles (optional)
- Room Mechanics (optional)
- Special Locations
- Doors
- In-game soundtrack (optional)
General (after article-exclusive headings)
- Trivia
- Removed Content
- Bugs (optional)
- Related modifiers (optional)
- Related achievements (optional)
- Gallery
- References (optional)
Note that you can add unique headings (such as "Dialogues" in the El Goblino article) between article-exclusive and general headings, and subheadings (such as "Types of containers" in the Containers article) under any heading.
References
References should serve as a source citation to certain details in articles that can be doubted or challenged by others, e.g confirmations by developers. They should be formatted in front of the citated text like one of the following examples:
<ref>[https://twitter.com/DoorsRoblox/status/1566604418761605121 "Ambush ambushes."] – DoorsRoblox, Twitter</ref> {{Cite|https://twitter.com/DoorsRoblox/status/1566604418761605121|"Ambush ambushes."|DoorsRoblox|Twitter}}
If a reference is present without a references header, one should be made below the article gallery like this:
== {{Icons|Gallery}} References ==
{{Reflist}}
The bottom of an article page should also remain the same across articles. Here is how it should be structured:
== {{Icons|Gallery}} References ==
{{Reflist}}
{{Navigation}}
[[Category:Exemple]]
[[Category:Exemple2]]
<!-- Interlanguage links -->
[[ex:Exemple]]
