Pikipedia:General content guidelines

This page details Pikipedia's guidelines towards article content in general. More specific guidelines can be found here. For policies, see Pikipedia:General content policy.

Article format

General

• Articles must have a "See also" section. In extreme cases where no related pages exist, link to the category the page is in.
• In the opening paragraph, the name of the article's subject should be in bold.
• Articles should ideally have at least one image and the {{game icons}} template at the top. Although not encouraged, an article may go without images if its subject cannot easily be shown. The game icons may be missing from a page if it does not directly relate to any Pikmin game (e.g. a Super Smash Bros. game article).
• Use formal US English. That said, just because the wording should be formal doesn't mean it has to use advanced words.
• When referring to the player, use the pronoun "they" (e.g. "the player can check their options").
• Dates should be written with the {{date}} template.
• Instead of the <references/> tag, use the {{refs}} template.
• Reference tags (<ref>) shouldn't have spaces before them. For transcripts, use {{transcript}}, and make the second parameter follow a format similar to the following: "Olimar's notes on the Red Bulborb"; note the links and lack of period.
• To add equations, use {{equation}} and whatever recommended instructions it contains.

Italicizing

Shortcut: P:ITALIC

All titled media should be italicized in articles. At Pikipedia, this is mainly video games, but also covers series, music, books, and films, for example. Pikmin Adventure is also included, because for the sake of being a collection of Pikmin information, Pikipedia treats Pikmin Adventure as a game (instead of a mini-game).

"Pikmin 1"

Shortcut: P:P1

The first Pikmin game, Pikmin, should only be referred to as "Pikmin 1" where ambiguous. In article text, game names are italicized, so this is not a problem, but in categories, for example, it could easily refer to the species or series, without the "1".

Capitalization

Shortcut: P:CAPITAL

Some subjects in the Pikmin series have ambiguous official capitalization, commonly because subjects whose names aren't in title case are forced to be as such because of the way they're presented (Piklopedia file, lock-on screen, etc.). This, combined with different games being inconsistent about the capitalization of some names has lead to the following community-created guidelines:

Proper nouns

Title case. Proper nouns are to always be written in title case. It should be clear what things are given proper names, like areas, caves, characters, and important objects (ship parts, treasures, fruits).

Species

Title case. This applies to Pikmin type names, enemy species names and plant names (e.g. "Yellow Pikmin", "Beady Long Legs", "Pellet Posy"). These names are of the most obvious examples of inconsistency in the series. Although in the real world, species names are commonly written in lowercase, fans of the series are used to seeing them written in title case; specially considering it's common in video games for enemy type names to be in title case.

Families

Lowercase. The names of families should be written in lowercase, as is the case in the real world. This capitalization is normally seen in the games as well.

Common objects

Lowercase. For objects that are common throughout a game and do not have a major impact on gameplay, their names should be in lowercase. This mirrors the way it is in the real world – humans don't capitalize the word "egg" or gate" for no reason. This includes, but is not limited to: hazards, obstacles, sprays, nectar eggs, nectar, rubble, bomb rocks, pellets, and geysers.

Simple words

Lowercase. For words that do not deserve or need any specific capitalization, they should be written in lowercase like any normal text, even if they're important mechanics. This means that words like leader (and captain), day, area, cave, sublevel, etc.

Special cases

• "Onion", as well as the Onion's type, must always be written in title case. (e.g. "Red Onion", not "red onion".)
• The President's "name" should be written as "the President", for consistency's sake.
• Scientific names use a capital first letter for the genus, and a lowercase for the rest. Example: "Oculus kageyamii russus".

For the purpose of being clear, "title case" refers to names in which the first letter of each "non-minor" word is capitalized (e.g. "This Text is Written in Title Case Style"), and "lowercase" means that the words all start with a lowercase letter. Naturally, the names of subjects at the start of sentences, headers, etc. always start with an uppercase letter, with very few exceptions.

Frames and galleries

Shortcut: P:FRAME

Example of a picture with a frame and caption.

Always add a caption to images, and finish it with a period. Organize galleries so that the most in-game-related content comes first.

All images with frames (see example on the right) and images on galleries should have a caption on it, even if it's just something like "Follow-up to the previous image.". Captions should be treated like an article's body, with links and italicizations, ending in periods, etc.

When creating a gallery for an article, organize the images so that the most in-game related content is placed first. For example, suppose you have a gameplay screenshot, a texture ripped from the game, a concept art picture, a strategy guide picture, and a photo of a relevant real-world item. You should list them in that order. If the subject appears in multiple games, there should be a subsection for each game. All Super Smash Bros. series images should be under a subsection with the same name, regardless which Super Smash Bros. game it is. If there are any images that don't fit in a specific game, there should be an "other" subsection.

Region

Shortcut: P:REGION

When the information on a subject changes according to the game's region, the US version's info should come first on the page, then the European version, and finally the Japanese version.

When naming a region, avoid using the term "NTSC" or "PAL", as explained here. Instead, use "US", "Europe(an)" or "Japan(ese)".

Prerelease

Shortcut: P:BETA

When referring to a prototypical version of something, avoid using the terms "alpha" and "beta". Those terms can mean different points in development for different developers, so unless the developers specifically brand a point in time or version as being "alpha", "beta", or "release candidate", do not use those terms. Instead, use "prototype", "prerelease", or "early".

Order for common sections

Shortcut: P:OCS P:SO

Some sections are common to many pages; where present, these should be ordered as follows:

• Glitches
• In other games
• Technical information
• Naming (+Names in other languages)
• Gallery
• Trivia
• Names in other languages (if the Naming section is missing)
• See also
• External links
• References
• Navigation templates (this section has no heading)

Order for games

When there are sections of an article for different games, games should be listed in release date order, with main-series games before spin-off games and miscellaneous games. If it's necessary for a re-release to have a separate section, it should go after the original version of that game. This results in the following game order:

• Pikmin
• New Play Control! Pikmin
• Pikmin 1 (Nintendo Switch)
• Pikmin 2
• New Play Control! Pikmin 2
• Pikmin 2 (Nintendo Switch)
• Pikmin 3
• Pikmin 3 Deluxe
• Pikmin 4
• Hey! Pikmin
• Pikmin Bloom
• Pikmin Adventure
• Super Smash Bros. series

Naming section

Shortcut: P:NAMING

Most articles should have a section where they explain the subject's names. If applicable, the article should mention the origins, explanations, or inspirations of the names, as well as their meanings and translations.

For this, use {{naming}}. If the article's subject has names that derive from another, or uses names that are common in a family, then the respective list item should contain something like "See <link> for details on <word>", with a link to the article+section that details that information. This avoids having to explain what the same words mean over several different articles.

If the "Naming" section is created, the "Names in other languages" section should be a subsection of this one, and should make use of {{foreignname}}.