Project:Style Guide

This is the for all pages on this wiki. Try your best to make all the pages on the wiki look like this, such that we may become as professional and standardized as possible. Happy editing!

Standard Layout
All pages should follow the below layout.

{{OPS {{Weapon }} Most pages should follow the following layout. Before you start writing with the other headings, provide a basic description of the item or topic here. If applicable, describe the way the item looks and give a summary of its basic function. Be sure to use the code {{PA}} for the first instance of the page's name. It will create the page name in bold. Shouldn’t take much more than three or five sentences.
 * title  = Standard Layout
 * content =
 * title      = Example
 * image      = Hammer 1
 * age        = 100
 * type       = Melee
 * slot       = Primary
 * gather     = 17
 * moveSpeed  = 80%
 * attackSpeed = 300
 * range      = 150
 * damage     = 40
 * struct     = 1
 * update     = 0.6.1

Technical

 * Use bullet points.
 * Give very specific data about the particular item. (i.e, Katana attack power is 40, Katana reduces move speed by 20%)

Using

 * Also uses bullet points.
 * Give your ideas on how to use the particular item. (e.g, Use the Great Hammer to pursue opponents, then switch to Katana and finish them off.)

Against

 * This section is only used if the subject has an effect. For example, the Dark Knight has an effect, so it has an Against section, but the Snowball has no effect, so its page will not use an Against section.
 * Again, uses bullet points.
 * Give your ideas on how to work against the particular item. (e.g, The Katana is effective against Daggers because...)

Gold Variant
Only used for weapons pages. Describe the Gold variant here, i.e., how its appearance changes, how much damage it does.

Diamond Variant
Same deal as the gold variant section but for the diamond variant, only use on weapons pages.

Ruby Variant
Again, same as with gold and diamond variants.

Real Life Equivalent

 * If applicable, describe briefly the real life version of the weapon or item.
 * Use bullet points.

Trivia (if applicable)

 * Use bullet points here too.
 * Give interesting, quirky and/or humorous facts about the item.

History
Give a summary of the history of the particular item, citing the changelog and providing images if applicable and necessary. Use the following format, with the latest updates first:


 * Update # - Change(s)
 * Update # - Change(s)

Footnotes (if applicable)

 * References to support data or notes/clarification.

Gallery
}}
 * A place to store 2+ photos about the page.

Standard Format
As everyone knows, lots of pages have duplicate. We would like to ask everyone to help resolve that issue, by removing, adding, and replacing categories, depending on the page and category. Creating new categories is discouraged; instead, use existing categories. New may be created if necessary, but in general, use existing templates. In addition, most pages should have an infobox detailing basic information about the page. Also, infoboxes should be placed above the first content but below any other notice templates. Perhaps the biggest problem the faces is point of view. Third person should be the universal standard to ensure that our pages are professional. It is advised to rework any instances of first or second person point of view into third person wherever possible. Link to page in its first instance on a page. For example, if Gold Weapons is mentioned three times on a page, it should only be linked to the first time. ' Note : This only applies to users who use Source Editor instead of or the visual section of. You can enable Source Editor in your. Not using Source Editor may result in bad formatting.'
 * -|Categories=
 * -|Templates=
 * -|Point of View=
 * -|Links=
 * -|Formatting=

Lists should have a space between their symbol ( for unordered lists and   for ordered lists) and the text.

Incorrect:
 * Item 1
 * Item 2

Correct:
 * Item 1
 * Item 2

Headings should have a space between either of the equal signs and the heading text.

Incorrect:

Heading
Correct:

Heading
Infobox parameters should all be aligned with each other.

Incorrect:

Correct:

Also, after an infobox or a notice template has been closed with, leave a line break.

Incorrect: Text.

Correct:

Text.

Accuracy, Objectivity, and Brevity
Accuracy is pretty simple — pages shouldn’t include random information that isn’t known to be true, as that’s not what wikis are for. A wiki is comprised of fact, not clickbait and overspeculation.
 * -|Accuracy=

Make sure information comes from reliable sources, and not one YouTuber’s thumbnail or the like. Articles should not contain misinformation — what good does that do? Is anything learned? Clearly, one must ensure that the content they add is helpful to users.

Objectivity means “not influenced by personal feelings, interpretations, or prejudice; based on facts; unbiased”. Now what this means is that you shouldn’t put opinions in articles. For example:
 * -|Objectivity=

Incorrect: “The Katana is a horrible horrible thing and the only weapon worse is the absolutely unusable Short Sword — it is obviously hard to control and you can’t get a good score with it.”

The issue with this is that no one can prove that the info is correct — it’s just what some random editor thinks. Even if there is more than one editor who thinks such, you must recall that wikis are collections of facts, not blogs. Thus, only objective statements that are actually true should be included in articles.

Brevity just means “briefness”. Now, at first glance, you might wonder why this is necessary. Shouldn’t paragraphs be embellished a little? The truth is, long-winded explanations are hard to read. A wiki is home to information, as previously mentioned — not walls of text that people cannot read. Always remember while editing that short and sweet is a treat.
 * -|Brevity=