This Style Guide serves as an in-depth handbook on the standards of the Cookie Run: Kingdom Wiki's formatting and styling of content. These guidelines ensure a defined convention of content presentation for users' ease of understanding and reading flow.
General
Grammar
All pages must use correct English grammar and spelling to the best of the wiki editors' collective ability. This guide will not list all conceivable grammar rules—it will mainly cover those which may be unclear, obscure, or differing amongst dialects.
This wiki uses American English spellings and grammar rather than that of British/European English or any other English dialect. Examples of this include:
|
American English vocabulary should generally be used as well, though instances in which cultural differences exist should be clarified (example: "American football" rather than only "football").
Punctuation
Again, American English punctuation in general should be used rather than that of other English dialects. Examples of this include:
|
Lists of items using commas should use Oxford commas, meaning the second-last item in a list should be followed by a comma. Comma lists using "and" as a conjunction should use the full word of "and" rather than an ampersand (&).
|
Dashes used in sentences as an equivalent to a semicolon (;) should be em dashes (—) rather than en dashes (-). For ease of access, an em dash can be typed by holding the Alt key, typing "0151" on a keyboard's numpad, and releasing Alt.
|
Parentheses
Phrases surrounded by parentheses ((...)) which contain separate phrases also surrounded by parentheses should have the surrounding punctuation alternate between parentheses and brackets ([...]) (though extended uses of parenthetical phrases contained in parenthetical phrases should be avoided). For example:
|
A parenthetical phrase at the end of a sentence should have the sentence's end punctuation outside of the parentheses.
|
A parenthetical phrase that serves as its own full sentence separate from other sentences should have its punctuation inside of the parentheses, although this type of parenthetical phrases should be avoided.
|
Quotes
Quoted text preceded by original text should be introduced with a comma in most cases. For example:
|
Quoted text interrupted by original text should have its first segment end in a comma and the original text also ending in a comma.
|
"Incomplete" quoted text that is introduced by original text should not be followed by punctuation other than its wrapping quotation marks.
|
Quoted text followed by a syntactically-independent, full sentence of original text should be preceded by a colon (:).
|
Certain quoted text that is not dialogue, such as established titles of characters or media, should have end punctuation outside of the quoted text's quotation marks.
|
Similarly, quoted text which matches the syntax and intent of a sentence should not be followed by a comma.
|
Quoted text which contains another instance of quoted text should alternate the use of double quotation marks and single quotation marks. For example:
|
Formatting Titles of Works
The titles of works and media must be properly formatted depending on the type of work. Works should also be linked back to a source whenever possible (preferably the creator's own site or a Wikipedia article) and capitalized and punctuated exactly how they are at their sources. See below for a list of work types, how to format them, and accompanying examples.
|
Formatting Words from Other Languages
As Cookie Run is a Korean franchise with worldwide influence, the pages on this wiki will often contain transliterated words from other languages, especially Korean. These words should be italicized and have their Hangul or other original language's script un-italicized in parentheses next to the word. The parenthetical script should only be included in the first instance of the word in each section. Links should only cover the transliterated word in italics, not the original language script.
|
Transliterated words that are the names of people, companies, and other proper nouns should not be italicized. The original language script can be included in parentheses if it does not break the text's reading flow.
Wiki Articles
General In-Text Formatting
All quoted text, especially that seen in-game, should be written exactly as it is in the source material even if the original text has errors. Do not correct erroneous quoted text; if quoted text contains errors, {{Sic}} should be inserted directly after the error in the quote.
yields
|
Tone
The written tone of an article should remain academic and formal. Very rarely should exclamation points (!) be used in a wiki article, and slang words, connotative terms, and text abbreviations should be avoided. Personal opinions should not be expressed, as the wiki is meant to be objective.
To address the reader, "you" should not be used; instead, an editor should use "a/the player" or, rarely, "one".
|
In pages where it is the direct opinion or work of the wiki being expressed, an editor should use "the wiki" or "the wiki/administration/moderator team"—"we" should rarely be used if ever.
|
The only instances in which academic tone can be broken is in image captions, header quotes (on non-character pages), and so on—in other words, only in aspects of an article that are not the main text. In these instances, more lighthearted jokes, comments on the image/topic at hand, pop culture references, and so on may be inserted. Examples of this include the following:
|
While this caveat exists to allow some fun into articles, an editor must be very mindful of how they use this allowance; it should be used relatively sparingly and good judgement should be utilized in determining a quip to insert. Proper grammar and spelling must remain in these instances.
Links
Pages should not link to themselves nor should subpages link to their main pages unless the purpose of the link is for navigation. For example, an image in Espresso Cookie/Gallery should not link back to 
Espresso Cookie's main page, but the navigation tabs on the page may link back to the main page.
Links placed next to punctuation should not have said punctuation included in their link display text unless it is possessive punctuation (i.e. "'s"). (This does not apply to Template:CookieHead as it is coded in a way that does not allow "'s" to be included in the link.) For example:
|
In articles with paragraph text and sections, any links to pages on and off of the wiki should be actively linked only in their first instance of being mentioned in each given section—they may be linked again in their first instance in other sections. For example, an excerpt from Espresso Cookie's page for how and when it links to 
Madeleine Cookie's page:
Personality
Espresso Cookie is a serious, smug, and intellectual perfectionist, and does things with absolute precision. [...] His facial expression generally defaults to a composed and confident smile, but there are instances where he doesn’t bother hiding his displeasure or exhaustion (such as when faced with a preventable failure or [...] According to Trivia
Starting August 19th, 2021, in anticipation for the release of Kingdom's Japanese dub, hashflag images depicting emoji versions of Espresso Cookie along with [...] |
Icon Templates
Template:CookieHead
Links to playable Cookies' pages should use Template:CookieHead (or Template:Ch) when applicable. To use this template, fill the 1 parameter with a Cookie's name in all lowercase letters.
yields |
For instances where only the Cookie's head icon link is needed, use Template:CookieHead with the Cookie's name in the 1 parameter and with its icononly parameter (under the "add more information" option) being set to true.
yields |
In instances where a Cookie is not referred to specifically by name, the text which refers to them should be linked to the Cookie's main page and Template:CookieHead should be placed beforehand with its icononly parameter being set to true. For example, both strings of text below should link to Espresso Cookie:
yields |
yields |
Template:CookieHead also has a width parameter, but a Cookie head icon's default width normally should not be tampered with in standard article editing.
A space should not be placed after Template:CookieHead uses, as the template automatically inserts a space.
Template:CookieSkillicon
References to a Cookie's Skill should use Template:CookieSkillicon (or Template:Csi). For instances in which text refers to a Cookie's Magic Candy Skill, Template:CookieSkillicon should be used with its magiccandy function being set to true.
yields |
yields |
Although the function is very rarely needed, Template:CookieSkillicon can also be set to display only the Skill icon by filling the icononly parameter (under the "add more information" option) with true.
yields |
yields |
A space should not be placed after Template:CookieSkillicon uses, as the template automatically inserts a space.
Template:ClassIcon
References to a Cookie's type or default position should be linked using Template:ClassIcon. To use this template, fill the 1 parameter with a Cookie type or position (this must have its first letter capitalized).
yields |
yields |
Although the function is very rarely needed, Template:ClassIcon can also be set to display only the Skill icon by filling the icononly parameter (under the "add more information" option) with true.
yields |
yields |
Icon Templates in Image Captions
Unlike normal in-text links, icon templates should be used in every instance of a concept being mentioned in the caption in the section in which they are placed. They should not link back to the page on which they reside. In instances seen in character gallery pages, the subject of the gallery page should not be referred to at all. For this example, assume this gallery is in Espresso Cookie/Gallery:
References
References are an important method of sourcing off-site content. There are multiple methods of accessing the references tool and creating a new reference:
- Using the visual desktop editor, click the book icon between the indent button and the chain link button and click "Basic"
- Using the visual desktop editor, use the Ctrl+Shift+K key shortcut
Either option will open a window that prompts text. Here, one should write a title for their reference, highlight the text, and click the chain link icon to link the text to the source.
The source desktop editor can also be used to write new references. For this method, the syntax is as follows:
yields |
It's important to name references if one plans to reuse them; the default reference name is ":0".
In-text references should be placed immediately after their paired text, but after any end punctuation.
yields
|
Existing references on a given page can be reused by:
- Using the visual desktop editor, clicking the book icon between the indent button and the chain link button and clicking "Re-use"
This will open a window of a list of available references to reuse. Alternatively, any reference that has a name assigned to it can be copied and pasted in the visual editor to automatically reuse it.
The source desktop editor can also be used to reuse references and often is the only viable method in situations where references are in places that are difficult for the MediaWiki coding to recognize, such as infoboxes. This can be achieved by simply typing the code for the reference to be reused—including its name—and adding a / before the final > of the tag.
yields |
This appears in the references list on a page as x.x rather than simply x.
Image Links
While the function is not often needed to be plainly coded in the middle of an article, images can be coded to link to a page upon being clicked. This can only be achieved in source editing, where link=Page_Name should be added to an image's properties for an internal link and link=www.example.com should be added for an external link.
yields |
yields |