Page Organization
This article outlines the structuring the pages on this wiki should follow. Exceptions must only be made after careful consideration and conversation with the community. At all times, this article should be referenced as a guide when solving editing disputes.
An article is a main namespace or category page explaining the content of, or closely related to Deltarune. All main namespace pages are considered articles with the exception of the Main Page.
The first paragraph (introduction) of an article should be a short description of its topic, stating what it and its role in Deltarune is. Empty sections are to be omitted from the article. The first mentioning of the article's topic is always written in bold.
If applicable, the following is always defined at the top of the article's source. There is a line break between the article header and the page body.
- DISPLAYTITLE
- DISPLAYTITLE is a magic word used to change the title that is displayed on the article from the actual article name.
- For
{{for}}template is used for simple disambiguations. It must always be placed above infoboxes.- Infoboxes
- Infoboxes are templates used in articles to outline important information about a topic. They are put on the top of the article, below other templates and magic words, or on the top of an article section if the article also covers some sub-topics. Some infoboxes auto-add categories to articles, these categories should not be assigned in an article's source if such an infobox is already present. A line break must be put after the closing tags of an infobox.
The page body is the main content of the article, containing all the relevant information about the topic of the article. Sectioning of the page body is done depending on the type of page. More information can be found below.
The following is always defined at the bottom of the article's source. There is an empty line between the page body and article footer.
- Trivia
- Trivia sections are bullet-point lists located at the end of the main content of an article containing interesting, little-known facts that cannot be incorporated into an article effectively. Trivia takes the lowest priority, meaning any information should be attempted to be added to the page body before being placed in trivia. If several trivia points can be lumped into a category, do it. (ex: if Jevil's trivia mentions there is a connection to Knight 3 times, add "Knight" to Relationships). Trivia must be true, and speculation must be avoided. Try to keep assumptions as close to the truth as possible.
- Version history
- For any article that describes in-game content, a Version history section can optionally be placed below the Trivia section to document any published changes that the article's subject has undergone throughout different game versions. The Version history section should solely consist of a table that follows the structure of the Example Version History Table below. Some early editions of the game may not have version tags available, and versions may be tagged differently on different platforms. When possible, use the version tags and platform names from the Version differences article.
Example Version History Table Game Edition Version Tag Changes Chapter 1 Demo Example change during the first released demo. Chapter 1 Demo (Console) Example change during the first released demo on console. Chapter 1&2 Demo v1.002 Example change that was released in v1.002 of the Chapter 1 & 2 Demo. - v1.003 (Windows/Mac)
- v1.00 (PlayStation)
Example change that was released in v1.003 on Windows/Mac and v1.00 on PlayStation, of the Chapter 1 & 2 Demo. Full Release - v1.20 (Windows/Mac)
- v1.10 (PlayStation)
Example change that may be released in a theoretical v1.20 on Windows/Mac and v1.10 on PlayStation after chapters 3 & 4 release. - References
- References and citations are placed at the end of an article, above navboxes but below Trivia. Between the references, trivia and navboxes are empty lines.
- Navboxes
- Navboxes are templates used for navigation. They contain links to articles related to the article they are placed on, and very often auto-add categories to the articles. Navboxes are meant to be placed below all sections. Above the list of navbox definitions is an empty line.
- Translation links
- Translation links are links to the same article translated into other languages. They are put below the navbox but above categories of the article.
- Categories
- Categories are displayed at a bottom bar on pages and are useful for grouping information as well as navigation. Note that some templates auto-add categories to an article, so additionally adding categories to an article is unnecessary. Adding irrelevant categories to articles is prohibited by the wiki policy.
- Other magic words
- Other magic words, such as
__NOTOC__should be at the very bottom of an article.
Character pages should use the {{Infobox character}} template as an infobox and {{Navbox characters}} as a navbox. Character pages must be categorized in the characters category or in one of the subcategories of the characters category, but the category must not be explicitly defined if already done so by another template on the article. A {{quote}} template may be suffixed to a Character article's header, given that the quote paints a clear picture of the character's speaking traits.
A regular character page body should be structured according to this template:
- Introduction
- Profile
- Appearance
- Personality
- Etymology
- Main story
- History
- Chapter X
- Relationships
- Creation and development
- Outside of Deltarune
- In battle
- Spells
- Gallery
A regular enemy page body should be structured according to this template:
- Introduction
- Profile
- Appearance
- Personality
- Etymology
- Main story
- History
- Chapter X
- Relationships
- Creation and development
- Outside of Deltarune
- In battle
- Appears with
- Attacks
- Strategy
- Quotes
- Flavor text
- Gallery
The In Battle sub-section can be omitted if the character does not appear in battle. An empty line should be added above a header to prevent it from directly following a paragraph.
A brief description of the character, stating what they are and their role in Deltarune is.
A description of the physical characteristics of the character, including their clothes.
Traits and qualities of the character, this may include their likes and interests.
Any information related to the etymology of the character's name. Not all characters have a name with meaningful origins, and this section should be omitted in those cases. Name origins that are obvious to most who speak the wiki's language don't qualify as "meaningful". For example, Queen does not need an etymology section to explain the word "queen".
If there's information relevant to the character's profile, but not applicable to any of the two subsections, it should be put in the top-level of Profile (after Profile and before Appearance).
Summarized narration of the plot without much detail and closely related to the character in question. Should be written as a narrative (rather than a walkthrough) and use past tenses where applicable.
A summary of the events that occurred before the beginning of Chapter 1 of Deltarune.
A summary of the events that occur for each chapter that the character influences the story of, where X is the number of the Chapter in question. Should be omitted if there are no other sections in the Main story section.
This section should list and describe the relevant relationships of the character in question, divided into subsections per each character. This description should involve the article's overall dynamic with the character of its subsection, and the impact the two have on one another. A one-term summary of each relationship should be present in the article's infobox, should it exist.
For a character article to have a relationship subsection for a particular character, the two characters must have noteworthy interactions or relevance to one another, involving just those characters. For example:
- Good: section lists the growth of the characters' relationship throughout the Chapters, as well as the development made between the two.
- Bad: section lists a character's opinion of another character that they have little to no interactions with, and the characters barely have any relevance to one another.
Relevant information pertaining to the character's creation and development, outside of the game's narrative. Creation refers to the real-world circumstances that led to the character's creation, including known design intentions by the author. Development includes any changes the character underwent pre-release, as well as major changes to the character post-release. Use the Version history section for a full list of post-release changes that were actually published as game versions.
If the character also makes an appearance in Undertale, or makes an official (endorsed by the Deltarune team) appearance in third-party content, that appearance can be briefly described here. In the former case, this section should generally start with a {{main}} template linking to the Undertale Wiki's article on this character, if it exists.
Depending on the length of this section, it may be forked into a sub-page. In battle sub-pages follow the same standards and organization as their sub-section counterparts. In battle should be structured according to this template:
- Spells
- Appears with
- Attacks
- Strategy
- Quotes
- Pre-battle (if applicable)
- Battle (if applicable)
- Post-battle (if applicable)
- Flavor text
A shopkeeper may have a "Shop dialogue" sub-section, structured similarly to the Quotes sub-section.
The Spells sub-section should only be present if the character can be controlled by the player as a party member.
The Quotes sub-section always consists of a bullet-list of quotes in italic font, followed by the context of said quote in square brackets in bold.
The Flavor text sub-section is structured similarly to the Quotes sub-section.
The gallery sub-section contains a <gallery> of images depicting the character or other content closely related to the character. Please note that galleries are NOT image dumps, and that they must be treated as such. Only upload images to galleries for the purpose of documenting the appearance and other traits of the character.
Item pages should be categorized in the items category or subcategories of that category, and should use {{Infobox item}} as an infobox and {{Navbox items}} as a navbox. The article's source should not contain a Category tag for Items if another template on the article already categorizes it as such.
An item page body should be sectioned in the following way:
- Introduction
- Additional uses
- Flavor text
- Etymology
- Creation and development
States what type of item it is, where is it found, and (if applicable) its counterparts. Any special effects of its intended use that may not be clear from the item's infobox should go here as well.
This section should list in bullet list format, the special uses an item may have, and their effect(s).
This section should list in bullet list format, all the flavor text shown in-game when interacting with the item in various ways.
Any information related to the etymology of the item's name. Not all items have a name with meaningful origins, and this section should be omitted in those cases. Name origins that are obvious to most who speak the wiki's language don't qualify as "meaningful". For example, Manual does not need an etymology section to explain the word "manual".
Relevant information pertaining to the item's creation and development, outside of the game's narrative. Creation refers to the real-world circumstances that led to the item's creation, including known design intentions by the author. Development includes any changes the item underwent pre-release, as well as major changes to the item post-release. Use the Version history section for a full list of post-release changes that were actually published in game versions.
The {{Infobox music}} template should be used as an infobox. Documentation for this template can be seen here. All soundtrack pages should be categorized according to the albums in which they are present. In addition, soundtrack pages must use the corresponding navbox.
Soundtrack pages do not have a correct sectioning, which means any section can be added between the Trivia and introduction section as long as it contains enough information in it.
Location pages should be categorized in the locations category or subcategories of that category, and should use {{Infobox location}} as an infobox and {{Navbox locations}} as a navbox. The article's source should not contain a Category tag for Locations if another template on the article already categorizes it as such.
A location page body should be sectioned in the following way:
- Introduction
- Etymology
- Main story
- History
- Chapter X
- Geography
- Sublocations
- Creation and development
- Gallery
The Introduction of a location page clarifies what the location's role in Deltarune is, and holds a small summary of the location. The Introduction can also note any plot-vital points located within the location in separate paragraphs.
Any information related to the etymology of the location's name. Not all locations have a name with meaningful origins, and this section should be omitted in those cases. Name origins that are obvious to most who speak the wiki's language don't qualify as "meaningful". For example, Forest does not need an etymology section to explain the word "forest".
Summarized narration of the plot without much detail and closely related to the location in question. While this section can be used to incorporate information for walkthrough purposes, it should be written as a narrative, and use past tenses where applicable. When writing information for walkthrough purposes, do not forget that addressing the protagonists or player as "you" is incorrect terminology and violates the Manual of Style.
A summary of the events that occurred before the beginning of Chapter 1 of Deltarune.
A summary of the events that occur for each chapter that the location influences the story of, where X is the number of the Chapter in question. Should be omitted if there are no other sections in the Main story section.
A broad description of the location as a whole. This should include any common elements throughout the location. This may be omitted if the location is not large enough to warrant this section.
A list of summaries of sublocations located within the location, separated by level 2 sub-headers. The top level of this sub-section (Between == Sublocations == and the following sub-header) should not contain any text paragraphs, but may contain a bullet-list of minor sub-locations that are not noteworthy enough to have their own sub-header.
Relevant information pertaining to the location's creation and development, outside of the game's narrative. Creation refers to the real-world circumstances that led to the location's creation, including known design intentions by the author. Development includes any changes the location underwent pre-release, as well as major changes to the location post-release. Use the Version history section for a full list of post-release changes that were actually published as game versions.
The gallery sub-section contains a <gallery> of images depicting the location or other content closely related to the location. Please note that galleries are NOT image dumps, and that they must be treated as such. Only upload images to galleries for the purpose of documenting the appearance and other traits of the location.
All files on the wiki need to have a proper description, licensing information, categories, etc. added to them. This can be achieved using the {{file}} template. All file names must be structured according to this guide:
- Characters: <Name> <"face"/"battle"/"overworld"> ["unused"] ["static"/"idle"/action]
- Battle: Sprites seen during an encounter
- Overworld: Sprites seen in the overworld (Game-overworld, not plot "overworld")
- Face: All other usages for faces (dialogue, (party) menu, etc.)
- Unused: Indicates that this sprite is unused in the final released version of the game.
- Static: Only used to differentiate this image from an animated counterpart
- Idle: Only used to differentiate this image from a static counterpart, the character must not be performing any action and is thus "idle"
- Action: The action the Character is performing in the image
- Locations: <Name> <"location"/"map"> [location description]
- Location: A screenshot/image of a location
- Map: An accurate map built from clean sprites
- Location Description: What part of the location is shown in the image, if multiple images of this location exist
- Items: <Name> "item" [additional information]
- Name: Name of the item
- Additional Information: Optional description of the image to differentiate it from others
- Attacks: <Name> "attack" <description>
- Name: The name of the enemy whose attack is shown in the image
- Description: A short (1-5 words) name of the attack
- Soundtrack: <Name> "soundtrack"
- Name: The name of the track that plays at the point of the game where the screenshot was taken
- Other Screenshots: <Subject> "screenshot" [Action]
- Subject: A very short (1-5 words) description of the subject of the screenshot
- Action: A short description of the action the subject is taking in the screenshot
If only using {{file}} on a file page provides a sufficient description, licensing information and author, please do not fill in the other parameters. Otherwise, consult the template documentation for how the template should be used.
All templates on the wiki must also have standards. Every template needs to contains a brief documentation on how to use it, along with some samples and full documentation of its parameters. Documentation should be on a separate page in the template namespace, suffixed with /doc, so if the original template was located on Template:A its documentation would be located on Template:A/doc page.
All templates are categorized in one of the subcategories of the templates category. Template documentation pages are categorized under the template documentation category.
Categories on Deltarune Wiki are an easy way of grouping information and navigation. They sometimes behave like articles, as mentioned above.
All categories must be categorized in other categories, except Category:Deltarune Wiki, which is the root category of the wiki.
Maintenance categories must always be hidden.