Manual of Style
The Manual of Style is the style manual for all Evade Wiki articles. This article is to be used when in doubt or disagreement over how an article should be structured and written.
The manual of style were last revised by FutureLitBLX on 5:57, January 1 2025 (Refresh)
General
Evade Wiki style aims to resolve editorial conflicts based on grammar, vocabulary and spelling. Editors should keep in mind that you should use American English language, make sure sentences are written smoothly and are able to be read. All articles should use language that is simple and unambiguous.
Formatting
- All article titles should be correctly written as it is directly displayed in the game without stylistic corrections (e.g., GrappleShot, not Grapple Shot).
- Because Evade Wiki is an online encyclopedia, a formal writing style is used. For this reason, casual undertones and slangs should be avoided. For example, do not use "ofc" in place of "of course", "abt" in place of "about", etc.
- The usage of contractions, such as "they're", "didn't", and "could've" are generally avoided. Use full forms like "they are", "did not", and "could have" instead.
- DON'T use AI for formatting articles.
Templates
Templates are pages designed to be included on other pages. They are found in the Template namespace and usually display material that needs to be shown on multiple pages at the same time. Once you've figured out what templates you have to work with, you can begin thinking about how to use them in their most basic form.
Article Structure
This section describes how articles should be structured and section titles formatted. This is highly specific depending on the page. If a header is not listed under general headers, it should be removed. It is recommended to use source editor whenever editing a page.
Infobox
The type of infobox depends on the page you are editing. All values should correspond to a value in the infobox. Additionally, an infobox can use <tabber> or <gallery> if there are multiple images that can be applied for an infobox. For example:
{{Template |image1=<tabber> |-|Icon = [[File:Filename.png|300px]] |-|View = [[File:Filename.png|300px]] </tabber> }}
The title in the infobox must be generally the same as the title of the page, except pages with brackets. Always provide a "View" section into the infobox. This means provide a ingame screenshot for the specific usable, utilities, nextbots or lights.
Honourable Mention Examples
Bad Example:
{{NoticeTemplate}} ==Heading== {{Template|parameter=value|parameter= string <br/> string2}} ===Sub-heading=== *Bullet **Sub-bullet |
Good Example:
{{NoticeTemplate}} {{Template |parameter = value |parameter2 = string<br>string2 }} ==Heading== ===Sub-heading=== *Bullet **Sub-bullet |
Description/Overview
The Description is important for making an article. It describes small information for the page and it does not need to be excessively long. Almost all articles need to have a sufficient description.
Appearance
This only applies to Nextbots, Maps, Usables, Lights and Utilities pages. This is where the description of the aesthetic appearance of the object is described.
Cosmetics
If the item has a cosmetic, please provide them using a table complete with high quality image, price and rarity.
Trivia
Trivia is an optional structure. If the content has trivial facts please include them, if not don't include it.
Update History
Update History is are the records of changes on the content. Please include them.
The relevant navbox should be placed at the bottom of the page. There must be three spaces between the main content of the article and the navbox.
Notice/Reminder Boxes
These should be used when something important in the article that is misunderstood, but is not fitting to put in Trivia. For example, if the Silenced SMG is an exclusive item, don't put in the Trivia section, add a notice instead.
Disambig
The box can be used when 2 or more articles have similar names, or the article has changed names in game, or has been removed.
Uploading Files
- When uploading images of icons, it is recommended to have the image size at 1200x1200 pixels. This does not apply to other images if it degrades the image quality in some way.
- Image, video, and audio files should be high quality. Images must be in PNG format, and the background should be transparent as well to allow for other usage such as using them in templates.
- Note if the nextbots have JPG images, use JPG format instead.
- When uploading new versions of files, replace the existing file instead of uploading a totally new one.
- This can be done by going to the file's page and clicking on "Upload a new version of this file".
- An exception would be when the subject has a new appearance (for example, a certain usable or utility has had its appearance changed), then the new appearance should be uploaded as a new file.
- Please use the content's name for the file name. If the content is outdated create a new file instead. For example:
File:Old_CONTENTNAME - Outdated Content File:Ver1_CONTENTNAME File:Ver2_CONTENTNAME File:Ver3_CONTENTNAME
Links
- There should NOT be multiple links to a single page or source. There are two exceptions to this rule
- There must not be links in a section heading.
Magic Words
Magic words are phrases used by Fandom which triggers the software to do something. When using magic words, they should be used in source editing instead of visual editing. See Community Central Article Here.
List of Common Magic Words
Here are some commonly used magic words:
__NOTOC__
hides the table of contents on a page.__TOC__
places the table of contents exactly where this is entered. It overrides the NOTOC switch.__NEWSECTIONLINK__
replaces the "Edit" button with "Add topic", for adding new sections on a non-talk page.__NONEWSECTIONLINK__
replaces the "Add topic" button with "Edit", on talk namespaces.__NOWYSIWYG__
disables the classic editor on a page.__HIDDENCAT__
makes a category hidden.{{CURRENTDAYNAME}}
outputs the current day of the week.{{NUMBEROFARTICLES}}
outputs the number of articles on your community.{{SITENAME}}
outputs the name of the community.{{PAGENAME}}
outputs the name of the page the word is placed on.{{FULLPAGENAME}}
outputs the full name of the page, i.e. with the namespace prefix, of the page it is placed on.