Manual of Style

From Containment 13 Wiki
Jump to navigation Jump to search

This page serves as the Containment 13 Wiki's Manual of Style, which sets the guidelines about how pages should be edited, formatted, named and maintained.

Manual of Style, or MoS, as it's commonly referred to, is a ground basis for all articles and pages within the wiki. This should assist some editors within this wiki to orientate their edits and what should be kept in mind when doing them in order to lose confusion in both MediaWiki's editor and our choice of page style. Note that the MoS should also be treated with common sense, meaning that not all details will be included, only the ones that people might not figure out by themselves. Another note, even though this should be clear, is that all pages are meant to be following the wiki guidelines.

Language

  • We prefer the use of British (UK) English, Canadian (CAN) English or Australian (AU) English across all pages, templates and files to be uploaded or are uploaded, although we do not enforce what language you have to use, you are required to use American English (US) with WikiText which is the Wiki's markdown language, this means you need to use "center" instead of centre, and color instead of colour when using WikiText in such code like <span style="color:#FFF">Placeholder</span> and [[File:Placeholder.png|center|thumb]]
  • All articles should be written in the third-person view, using terms such as "Player" or "User".
  • When writing content for templates and pages, we understand that not everyone has a perfect understanding of proper English grammar, but a decent level of grammar is preferred when writing and editing pages on this wiki.

Page & Template Formatting

  • Whenever mentioning the pages name within the body text it should be bolded.
  • You should never use a template such as {{PAGENAME}} to show the page's title.
  • Whenever linking to a category you must use [[:Category:CategoryName|CategoryName]].

Page Creation

If you're creating a page based on a topic, but with no text (which is common, if people haven't created it as a placeholder/unfinished page for others to complete), this is what you should refer to. This is done by either clicking on a non-existent hyperlink page or typing out your desired title in the search bar, performing the former.

Page Titles

Page titles are already created once you start editing in either visual or source editor, which can't be removed or changed, unless you wish to create another page with a different title. Titles are also what your page will be on about, meaning you won't necessarily have the option to rip off the page's topic over to another (example being a page about a character being about an SCP).

Page Sections & Headings

Each section should be dedicated to a specific detail of the topic you're editing/creating (may it be weapons, items or alike), keeping other sections separated from each other. Example being the characteristics of a Group of Interest's appearance, separated from their loadout and statistics. Sub-headings are also somewhat applied to this.

Types of Text & Their Purpose

As you may be aware, there are headings and different kinds of sub-headings, along with preformatted and block quote texts. Headings and sub-headings shouldn't be majorly overused, only used for separating different details (more in Page Sections & Headings). However, for preformatted and block quotes, they are rarely used.

Bold

When using bold styling in a page, it is customary to bold the title of the page at the very start. To insert it in the source mode, put three apostrophes before and after the text. Example: '''Bolded'''

Italics

When using italics styling in a page, use it when mentioning a piece of media, including but not limited to: TV shows, franchises and comic books. To insert it in the source mode, put two apostrophes before and after the text. Example: ''Italics''

Capitalisation

General

Upper and lower case letters must always be placed correctly:

  • Uppercase letters should be placed only as the initial letter of a paragraph, an article title, a map, a person, etc.
  • Lowercase letters need to be put in the rest of the paragraphs, except for article names.

Example:

Bad
== HEADING ==
=== sub-heading ===
introductory text.
Good
== Heading ==
=== Sub-Heading ===
Introductory text.

Proper Spacing and Content Separation

Bad:
{{Stub}}{{Infobox|title=value|image= file_name.png|caption=string <br />string2}}introductory text...

==Heading==
===sub-heading===

*Bullet
**Sub-bullet
Good:
{{Stub}}
{{Infobox
|title = value
|image = File name.png
|caption = string<br>string2
}}
Introductory text...

== Heading ==
=== Sub-Heading ===

* Bullet
** Sub-bullet

Gallery

  • Whenever adding a Gallery to a page you do not need to add the File: prefix or the double brackets in front of the filename and at the end of the filename extension e.g. .png]] and make sure to remove all underscores from the filename as they are not necessary for the image to display correctly.

Regular Gallery

When you are going to create a new gallery, it is recommended that you do this using Source Mode and do it like the example below:

<gallery widths="165" hideaddbutton="true">
Example 1.png|Example One
</gallery>

Slideshow

When you are going to create a new slideshow, it is recommended that you do this using Source Mode and do it like the example below:

<gallery type="slideshow" hideaddbutton="true" navigation="true">
Example4.png|Clicking photo takes you to [[Help:Contents]].|link=Help:Contents|linktext=Help:Contents
</gallery>

Infoboxes

Every page on this Wiki should have a corresponding infobox if one exists for the page's content. This infobox should contain key information about the subject the page is about. If there's multiple images for the subject then you should use a gallery, so the different variations are on separate tabs. Infobox galleries do not require any additional code such as widths="150", as you are only adding tabs to switch between the different images.

Whenever creating Infoboxes, avoid using slashes and backslashes in the names for the data tags, always separate combination tags. You should never have one parameter do the job that two individual parameters can do. Example:

Bad
{{Infobox
|title=Example
|image=Example
|type/purpose=Example
}}
Good
{{Infobox
|title=Example
|image=Example
|type=Example
|purpose=Example
}}