Ōkami Wiki

Editing

Ōkami Wiki:Manual of Style

1
  • The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit. If you are undoing an edit that is …
Latest revision Your text
Line 8: Line 8:
 
==General style==
 
==General style==
 
* {{linkable|Plain English|text=[[wikipedia:Plain English|Plain English]] should be used when possible. Avoid unnecessarily complex or rhetorical wording, and write with concision and clarity.}}
 
* {{linkable|Plain English|text=[[wikipedia:Plain English|Plain English]] should be used when possible. Avoid unnecessarily complex or rhetorical wording, and write with concision and clarity.}}
* The specific dialect of English used should favor that of the game and its developer's locale.
+
* {{linkable|US English|text=As the {{wikiname|series-link}} and its developer, [[wikipedia:COMPANY|COMPANY]], are based in the United States, [[wikipedia:American English|American English]] spelling and conventions are preferred over other dialects.}}
 
** The only exception to this is the preference of [[wikipedia:MOS:LQ|logical quotation]] over American punctuation. This is to maintain an encyclopedic style and is not a preference based on regional style.
 
** The only exception to this is the preference of [[wikipedia:MOS:LQ|logical quotation]] over American punctuation. This is to maintain an encyclopedic style and is not a preference based on regional style.
 
* When titling articles, use proper English capitalization rules rather than going by in-game capitalization. [[wikipedia:Proper noun|Proper nouns]] should use [[wikipedia:Title case|title case]], while [[wikipedia:Common noun|common nouns]] should use [[wikipedia:Sentence case|sentence case]].
 
* When titling articles, use proper English capitalization rules rather than going by in-game capitalization. [[wikipedia:Proper noun|Proper nouns]] should use [[wikipedia:Title case|title case]], while [[wikipedia:Common noun|common nouns]] should use [[wikipedia:Sentence case|sentence case]].
Line 14: Line 14:
 
==Representation==
 
==Representation==
 
* Articles should be titled according to their topic's most representative name (i.e. the name most commonly used).
 
* Articles should be titled according to their topic's most representative name (i.e. the name most commonly used).
* For characters, their full names should be used. Omit prefixes, titles, and honorifics (see [[#Redirects|§ Redirects]] below).
+
* For characters, their full names should be used. Omit prefixes, titles, and honorifics (such as "EXAMPLE" [[EXAMPLE]], "EXAMPLE" [[EXAMPLE]], or "EXAMPLE" [[EXAMPLE]]).—see [[#Redirects|§ Redirects]] below).
 
* The [[Project:File use#Main image|main image]] of an article should be of the subject's most recent canonical appearance.
 
* The [[Project:File use#Main image|main image]] of an article should be of the subject's most recent canonical appearance.
   
Line 20: Line 20:
 
Redirects help guide readers to the correctly titled page when there is a discrepancy about how the article might be named. However, they should only be created and used sparingly, for maintenance, usability, and [[wikipedia:Search engine optimization|SEO]] reasons.
 
Redirects help guide readers to the correctly titled page when there is a discrepancy about how the article might be named. However, they should only be created and used sparingly, for maintenance, usability, and [[wikipedia:Search engine optimization|SEO]] reasons.
   
* Redirects should be created for topics with multiple, [[Project:Notability#Relevancy|frequently used]], [[Project:Verifiability|sourced]] names. This may include the prefixes, titles, or honorifics applied to character names. Spelling variations may also warrant redirects if both spellings are used consistently across a single source.
+
* Redirects should be created for topics with multiple, [[Project:Notability#Relevancy|frequently used]], [[Project:Verifiability|sourced]] names. This may include the prefixes, titles, or honorifics applied to character names, such as [[EXAMPLE]] & [[EXAMPLE]]. Spelling variations, such as [[EXAMPLE]] & [[EXAMPLE]], may also warrant redirects if both spellings are used consistently across a single source.
   
 
* Redirects should always be created for when two articles are merged, or when a single article covers multiple topics, such as with achievement names.
 
* Redirects should always be created for when two articles are merged, or when a single article covers multiple topics, such as with achievement names.
Line 27: Line 27:
   
 
* Links to redirects in articles should be avoided. While they may be functional, they cause route fragmentation, are less optimal for SEO, and are not future-proof. Furthermore, it is more [[wikipedia:Semantic HTML|syntactically semantic]] to link the proper article title, while modifying the output text if needed.
 
* Links to redirects in articles should be avoided. While they may be functional, they cause route fragmentation, are less optimal for SEO, and are not future-proof. Furthermore, it is more [[wikipedia:Semantic HTML|syntactically semantic]] to link the proper article title, while modifying the output text if needed.
  +
   
 
==Article layout==
 
==Article layout==
Line 37: Line 38:
   
 
* The '''lede''' is a condensed version of the ''body''. It serves as an introduction to the article, although generally it should not contain any unique information (and therefore rarely needs to use [[Project:Verifiability|citations]]).
 
* The '''lede''' is a condensed version of the ''body''. It serves as an introduction to the article, although generally it should not contain any unique information (and therefore rarely needs to use [[Project:Verifiability|citations]]).
** The lede is the first part of the article, and should be placed before any level 2 section headers (or smaller), but after any introductory templates (infoboxes, message boxes, or the {{tl|appearances}} template).
+
** The lede is the first part of the article, and should be placed before any level 2 section headers (or smaller), but after any introductory templates (infoboxes, message boxes, or the {{tl|games}} template).
** The first sentence of a lede should include the article's name and any alternative names in bold, the type or category the topic belongs to (e.g. "character", "faction", "location"), and the games in which it appeared.{{note|If it appeared in around three or more games, "{{wikiname|series}}" may be used instead, leaving {{tl|appearances}} and the "History" section to be more specific.}} The first sentence should be as brief and definitional as possible.
+
** The first sentence of a lede should include the article's name and any alternative names in bold, the type or category the topic belongs to (e.g. "character", "faction", "location"), and the games in which it appeared.{{note|If it appeared in around three or more games, "{{wikiname|series}}" may be used instead, leaving {{tl|games}} and the "History" section to be more specific.}} The first sentence should be as brief and definitional as possible.
   
 
* The '''body''' contains the article's comprehensive, detailed, and organized information. Its primary focus is on canonical and gameplay information.
 
* The '''body''' contains the article's comprehensive, detailed, and organized information. Its primary focus is on canonical and gameplay information.
 
** This generally includes, in the following order: historical information (lore, relevant missions and cutscenes), characteristics information (appearance, behavior, etc.), and gameplay information (combat, performance, strategies, etc.)
 
** This generally includes, in the following order: historical information (lore, relevant missions and cutscenes), characteristics information (appearance, behavior, etc.), and gameplay information (combat, performance, strategies, etc.)
 
** The creation of subsections should be proportionate to the length of the parent section, similar to the [[Project:Notability|notability]] standards applied for the splitting or merging of articles.
 
** The creation of subsections should be proportionate to the length of the parent section, similar to the [[Project:Notability|notability]] standards applied for the splitting or merging of articles.
** Historical information should be written from an in-universe point of view, meaning for example the use of the protagonist's name rather than "the player", the writing should always be in past tense, and history-related sections should not mention out-of-universe facts.
+
** Historical information should be written from an in-universe point of view, meaning the use of "Jak" rather than "the player", the writing should always be in past tense, and history-related sections should not mention out-of-universe facts.
** The opposite is true of gameplay and characteristics sections, which describe facts from an out-of-universe perspective and should thus be written in the present tense, and may use the term "the player" rather than the protagonist's name if appropriate.
+
** The opposite is true of gameplay and characteristics sections, which describe facts from an out-of-universe perspective and should thus be written in the present tense, and may use the term "the player" rather than "Jak" if appropriate.
   
 
* The '''appendix''' contains any supplementary information, namely: behind the scenes sections, galleries, see also sections, notes (annotations and citations), references, navbox templates, and category links. The tense within these sections should use whatever is most appropriate; if the events described in "Behind the scenes" sections, for example, are from the past, use the past tense.
 
* The '''appendix''' contains any supplementary information, namely: behind the scenes sections, galleries, see also sections, notes (annotations and citations), references, navbox templates, and category links. The tense within these sections should use whatever is most appropriate; if the events described in "Behind the scenes" sections, for example, are from the past, use the past tense.
  Loading editor