Pixel Gun Wiki:Manual of Style

The purpose of this manual is to create guidelines to help uniformize content across articles in the. Reading this is recommended to make the editing process more efficient, as it would save editors many corrections. The guidelines in this manual are enforced, and this manual should be referenced when solving editing disputes. If there are any questions, suggestions or issues arise please contact administration. Thank you.

Language

 * This wiki uses Standard American English (SAE).
 * "Epilogue", "Monologue", "Dialogue" etc. should be preferred over "Epilog", "Monolog", "Dialog."
 * "Color" etc. should be preferred over "Colour."
 * When making possessive forms of singular and proper nouns ending with s, add &#39;s at the end.
 * Present tense should be used whenever possible.
 * Locations and Characters with proper-noun names are not addressed using article determiners. Example: "Area 52 Labs" instead of "The Area 52 Labs".

Article Content

 *  content on this wiki should be factual and proven, instead of what is theorized, folk, or believed. Please avoid adding theories, "headcanons", conjecture, opinions, and other kinds of non-factual information.
 * Conjecture may exist in this wiki  only  if it's indisputable, officially proven, thoroughly supported, or required.
 * Most, if not all, content from this wiki should be verifiable. Readers should have the ability to prove it is true, accurate, or justified, should doubts arise. Content that is only verifiable under restricted circumstances, like being behind a paywall or accessible only to a few select people, should be approved by staff members first.
 * Articles must contain information closely related to the topic in question and not be unrelated.
 * Situations must be discussed in a disinterested tone. This is done by giving no bias or preference, unimportant issues unnecessary weight, and avoiding any loaded language. Avoid the use of imperative form and second person narrative (you) when writing articles.
 * Avoid the use of informal and casual language commonly present in everyday conversation (e.g. kids < children).
 * Language must be clear and understandable. Avoid being too talkative by using short and concise sentences to avoid overloading the reader. This wiki should use simple language and sentence structure for the benefit of all readers.

Images
Non-animated images should be in PNG format, preferably with lossless compression. Images in the GIF format should only be used for animated images.

Links
There are several rules to follow when adding links to articles.
 * 1) There shouldn't exist multiple links to the same page in a single article. Exceptions are:
 * 2) * when two or more links are linking to a different section of the same page.
 * 3) * when one of the links is in the infobox/navbox and the other in the actual content.
 * 4) Pages that can be linked internally must be linked as such. Further help on how to internally link pages check Help:Links and Help:Interwiki link.

Spacing
Spacing in an article's source is a minor thing, but is enforced on the wiki. {| class="wikitable" style="text-align: left" ! Bad ! Good
 * Bullet
 * Point
 * List
 * Point
 * List


 * 1) Numbered
 * 2) List

Header 4

 * Bolded
 * Indent


 * Bullet
 * Point
 * List
 * List


 * 1) Numbered
 * 2) List

Header 4

 * Bolded
 * Indent


 * }

Easy formatting
The wiki implemented several data attributes for easy formatting into the wiki's CSS. Those should always be preferred over the normal methods of formatting. Data attributes can be used by wrapping the text to be formatted in a  tag, and defining   in the opening tag. The following is a list of frequently used implemented data attributes and their possible values:


 * Text Color
 * or
 * A RGB value can be given as well:
 * Fonts
 * or
 * A RGB value can be given as well:
 * Fonts
 * or
 * A RGB value can be given as well:
 * Fonts
 * A RGB value can be given as well:
 * Fonts
 * A RGB value can be given as well:
 * Fonts
 * Fonts

Data attributes can be combined in one span tag. For example,  gives Hello

__