Inkipedia:Policy/Manual of Style

This is Inkipedia's official Manual of Style, which guides you through how articles on this wiki should be written and formatted. Please do not judge this Manual too seriously&mdash;be reminded that not all of us have viewed this Manual at all.

Grammar and spelling
For our readers to be able to understand and enjoy the material within our articles, this text must be well-written. Please try to adhere to the rules of grammar and spelling as much as possible. Although not everyone on this wiki is a professional proofreader, you are encouraged to do the best you can in ensuring that your technical details are grammatically correct. If someone corrects your spelling or grammar, do not take it personally. They are simply helping readers.

Pronouns
Please use singular they when referring to a person of unknown gender. For example, someone referring to a player should use they, as the person is of an unknown gender (he/she/other).

If this bothers you, reconstruct the sentence to use a plural subject and use they.


 * Unacceptable
 * After checking his inventory, the player gets the Basic Tee.


 * Acceptable
 * After checking their inventory, the player gets the Basic Tee.


 * Alternative
 * Players should check their inventories to receive the Basic Tee.

Quotes
Please copy text that you are quoting exactly as it is written. This includes any spelling errors and other obscurities. To indicate that you have copied an error (and it is not an error of your own), please use the [sic] tag.

Contractions
At best, make an attempt to avoid contractions such as "don't" and "can't." These sound very informal and, in general, decrease the formality and professionalism of the article.

Capitalization
In article titles and the article body, only the first word and proper names are given a capital letter. Wikipedia's Manual of Style can be used for guidance. The following things should always be capitalized, due to being proper names, or due to being consistently capitalized by Nintendo:
 * Names of weapons. Does not include common names such as "main weapon" or "roller".
 * Names of gear items. Does not include common names such as "headgear" or "shoes".
 * Names of abilities. Includes gear abilities and the Super Jump action, but not common actions such as swimming or regular jumping.
 * Names of unique locations like shops and stages.
 * Names of modes.
 * Any mechanics that are consistently capitalized in-game. For example, Inkrail and Gusher are always capitalized, but sponge and ride rail are not.
 * Inkling, Octarian, types of Octarians, names of characters. Does not include common names such as "squid" or "octopus".
 * Some currencies: Golden Eggs, Power Eggs. Does not include common names like "cash", or "egg" when it is alone.

Italicization of titles
Major works of art, including video games, should have their titles italicized. With this in mind, please italicize every mention of a game in the Splatoon series.

Point of view
A common mistake while editing is to use phrases like the below:


 * I think the Basic Tee is at the start of the game.

Although this is completely valid due to the grammar rules above, notice that it is expressing the idea in first person. This can confuse the reader a good deal. Who is the "I" speaking?

Second-person statements are also typically not acceptable. Take, for instance, the below phrase:


 * If you speak to the girl amiibo, she will ask you to complete Octo Valley with a charger.

These are slightly trickier to spot. Notice how the author is explaining the situation using the reader as the example, as if the reader is the subject of the situation.

In general, attempt to stick as close to third-person as possible. Try this phrase:


 * Speaking to the girl amiibo in Inkopolis Plaza challenges the player to complete Octo Valley with a charger.

Or simply
 * Octo Valley can be completed with a charger by speaking to the girl amiibo in Inkopolis Plaza.

The only exception is in sections such as Walkthroughs, Tips, userpages, and blogs. In such cases, use second-person instructional text if possible, except for your userpages and blogs, where you can use first person.

Linking
Links are the thread that sews the wiki together. Although their importance cannot be stressed enough, it is also important that you know how to use them properly.

Do not be obtrusive
Although links are important, do not let them get in the way of the reader. The following sentence is unacceptable:
 * Black Trainers are trainers with a white heel (see Cyan Trainers, Purple Sea Slugs, and Pink Trainers.)

Notice how the text seems to acknowledge the existence of the links and seems to "point" at them with the "see" phrase.

This is better:
 * Black Trainers along with Cyan Trainers, Purple Sea Slugs, and Pink Trainers, are shoes with a white heel.

Although link text stands out from the rest of the text, do not let links halt the flow of the writing.

Avoid "click here" syndrome
Many web designers know that link text that says "click here" is not descriptive and requires the reader to click on the link to discover what article is the destination. This rule of thumb also applies to wikis as well, especially within the article namespace. In particular, "click here" syndrome is to be avoided within standard articles, although its use is also discouraged within the Category, Template, Inkipedia, and Help namespaces.

Short article, one link
When adding links within a short article, it is unnecessary to link the same word multiple times. In longer articles, however, the better choice is to "renew" the link for every section.

Treat readers like idiots
A rule of thumb for music notation is "treat the musician like an idiot." Although this seems odd at first, it makes sense that the composer ensures that the musician does not assume certain dynamics, articulations, etc. without the composer's consent. Composers should also assume that the musician does not fully understand the feel and attempted emotion of the music, and that all needed articulations should be added whether the musician expects them or not.

The same also applies to encyclopedias. Suppose a reader who is inexperienced in Splatoon reads the following sentence:


 * Capturing a Splat Zone is important to winning in Splat Zones.

Wait, what is a Splat Zone? What makes it "important?" These questions pop out of the reader's mind when he/she reads the sentence.

Be very specific, regardless of the complexity of the topic. Be formal, and define new Splatoon terms as they appear.

...But do not overdo it
Do not be too specific because of the Treat Readers Like Idiots guideline. If how you are describing the feature does not have a linking article, then consider you are going into too much depth. The following article beginning is not acceptable:


 * Black Trainers are trainers in Splatoon.

Um...what? We already know trainers are trainers. We also don't have an article devoted to trainers.

Do not delve too deeply into how an article is classified. If it is clothing, say that it is shoes, and not that it is a "type of trainers".

Chronological order
Please keep each game in the Splatoon series in chronological order. Articles should show the history of a topic starting with the first game and ending with the latest game. For example, an article about a weapon present in the first two games in the Splatoon series should have general information first, then Splatoon information, then Splatoon 2 information.

Line breaks
Please use the    tag to add a line break, as recommended by Wikimedia's Lead Platform Architect. Other variants of the line break tag will produce the same result but are longer to type.

Multiple line breaks
Multiple line breaks (   ...) look messy. If they are in place to align a picture or template, it may be better to use a clr template instead.

Coloring
Unless there is an extreme case with a very good purpose, do not use coloring in articles. There are two major types of coloring:


 * 1) The whole page is a single color or format. While the universal color scheme may seem much more interesting and "cooler" than the plain, black-on-white text, the inconsistency can be both distracting and irritating. If you have a general color that you want to apply to all pages, talk to the administrators about the wiki's skin or insert some CSS into your personal settings.
 * 2) A single portion of the text is colored. If you use the colors to apply emphasis, use bold or italic fonts.

Localization
Many of Inkipedia's articles are in the American English language. The gear articles' names are from the American version, and other names of the same gear should redirect to that article.

Where possible, please switch an American word, or where spelling is questioned, to a neutral word. For example, the American spelling "traveled" and English "travelled" should just become "went" as necessary.

Where there must be a decision, American will be used; however English will also be made available where possible. In an example template, Template:Color, a redirect from Template:Colour can be used and either template used to the author's discretion. However the word "color", where no ideal synonyms exist, should be kept.

Article titles should follow the American version if it differs (such as E-liter 3K as opposed to E-Litre 3K).

Where there is a collision of interest, the American version should still be used but a clear distinction made at the top of the article must be given (as in the case of Jungle Hat).

Editing of userspaces

 * Generally, users should only edit their own userspace, unless permission is given by the page's author (e.g. a guest list), or you are genuinely helping the user (e.g. replacing an old picture or fixing poor code).
 * All userpages must adhere to the Polices laid out across the Wiki.
 * If you wish to remove one of your own pages, please use the Delete template with a summary such as "Author request" and an administrator will do it for you.
 * Note: please note that this is an encyclopedia and not a place to just edit your userpage with cool codes. You are free to edit your userpage as much as you want but please help contribute to improve this wiki.

Thank you for reading!