Okami Wiki

Okami Wiki:Manual of style

661pages on
this wiki
Add New Page

For nearly every Wiki, there is a Manual of Style of some form that the community uses document their expectations and standards for every article. These are usually subject to change, given how a community is also subject to the same, which is why these guidelines may change at any time. Checking back here often is typically a good idea. However, most major changes to article structure or grammatical changes will require the consensus of the community and land a spot on the Recent News bar on the Main Page namespace.

Regardless, readers should come away confident in their understanding of Ōkami Wiki’s current standards for article structure, grammar usage, and any extras that may exist, should they choose to read this entire guide. However, given the length of a guide of this nature, readers are not expected to read the entire thing, but rather reference it as needed during the completion of any projects they may have, whether self-assigned or handed down by the community.

Article structure

Nutshell section
This section in a nutshell:

The sections needed to complete most articles are a Table of contents, infobox, Quote, Section header, Lead section, See also, References, Navigation table, and Categories. Some pages will need Disambiguation, Article message boxes, and External links. However, not all pages will need these to survive.


As is the case with a game like ours, at times, there will be articles about characters and historical or mythological figures that share the same name. To help reduce confusion and allow readers to find the correct page, we need Disambiguation. In most cases, the character will receive the normal name, and the real world figure will have some sort of identification in the title. For example, Amaterasu is for the page about the beloved white wolf we've all come to know and love, whereas Amaterasu (Shinto deity) is about her real world counterpart. To add a disambiguation notice, throw the {{For}} template at the top of the page to maximize convenience.

Table of contents

The Table of contents is a feature of most articles with four or more headers. This is to allow readers to immediately find and view the information they've found the most relevant or important. However, not every article has a Table of contents. If this is the case, be sure to add __TOC__ after the Lead section, but before the first section header.

Article message boxes

Article message boxes, otherwise known as Notices, are notifications typically attached to the top of a page to inform readers of ongoing projects or changes that need immediate attention and should be added to pages needing such. Some of the more common templates that will be used are {{Stub}}. {{Incomplete}}, {{Bad cleanup}}, and {{Extra cleanup}}. Most of these have pages that can be viewed to learn more about parameter usage and how to add them to a page. For further information about Notice templates, see here.


Infoboxes are features that perhaps are the most familiar to people, whether they realize it or not. An infobox is a little box that typically hangs to the right, featuring all of the immediately useful information a reader might want to know. Adding one of these is essential to ensuring the success of an article in many cases. For a full list of available Infoboxes, see here.


Use of the {{Quote}} template allows for authors to share some of the lines a particular character has said or add further detail to a location, technique, or other feature through what another person from Nippon has said about it. Adding a quote box is easy too. The syntax goes as follows:

{{Quote|Text goes here|-Who said it?}}
Without any further information given, authors will generate a quote box like this:

Text goes here

—-Who said it?

However, given that infoboxes can have varying colors, the same can be said of quote boxes. A better explanation is found here, but the short version will be provided on this page.

Essentially, the general gist of things is that authors need to match the colors of the quotebox to those chosen for the infobox, since neither should have an empty color parameter. However, because quote boxes have more than one color parameter, authors should keep in mind that they need to provide ones with dark colored borders--typically making use of a "color dark" template like {[t2|Gold color dark}}--and regular or light color backgrounds--like {{Gold color}} and {{Gold color light}}. The alternation between dark and light backgrounds has to do with how it looks with the text but is largely left up to authors to decide.

Section headings

Section headings are little pieces of code that allow authors and readers alike to determine the difference between two groups of paragraphs, most useful in grouping information together for quick and easy reference. Speaking of easy, headers are ridiculously easy to add. Enclose the desired name of the section in dual equals marks like so: ==Title goes here== to create a title for a section.

Within sections, authors can have endless subsections. However, the most useful and really the only one that should be used is the triple. This is because section headings have to do with headings in HTML. A level 2 header is the kind authors will be most familiar with in the long run, with level 3's coming in as close seconds. A level 1 header should NEVER be used, since it is the same size as the header at the top of the page and therefore confusing both to readers and the commands that automatically generate the Table of contents for a page.

Lead section

The lead section is the starting paragraph for any article and should be included regardless of type. Within this paragraph, authors are expected to introduce their topic to the audience, while bolding and mentioning the Title of the page, whatever it may be. After the title, authors are permitted to follow up with use of the {{Nihongo}} template to introduce and explain the Japanese as well, if it is known. If an author does not know the Japanese name for whatever their article will cover, feel free to hit up the Talk pages to find someone who does.

See also

The See also section is one currently found primarily on smaller articles without too much content. However, this is a section that should be added to every page. Use of this section allows authors to provide links to other pages, which in turn helps to generate more traffic to all parts of this Wiki, rather than a handful of main pages. When determining which articles to include, consider what would be beneficial or interesting to a reader. For example, if the page is about Waka, his See also section could include:

This list could easily continue to be extended, but then we'd be here all day. Regardless, this list should have a minimum of three other pages, whether internal or external links, and a maximum of seven. This is so that this section holds appeal, but not so much that it becomes supersaturated.


References is more or less a fancy name for an informal Bibliography. Drawing upon the necessary resources, authors can provide their sources for curious readers to learn more or confirm facts found within a particular article. While this is something that may seem unnecessary, it is an essential part of every article. Otherwise, we have users who do not believe the Moon Tribe cataclysm even happened or think that Sado is female. These are a handful of examples, but further highlight the need for proper citation. The following sections go over how to add them and what kinds are permitted for future author's convenience.

Adding citations

Wikia makes use of a little thing known as internal citations, inserted by using a <ref>. These are typically added right after a sentence that makes a claim that an author feels readers may not believe or after a claim that some may try to dispute. Essentially, insert ref tags wherever you feel controversy may arise. However, in cases such as Amaterasu's, where the two games oppose directly states information, please refer to the Talk page so that we can come together as a community on what to display. Be sure not to have edit wars with other users.

Now, with that out of the way, adding citations. When adding an internal citation, one encloses the text they want to display as evidence in a <ref> tag like so:

<ref>Textual evidence goes here</ref>
This will create a little number in brackets after the phrase this has been attached to like the one you see at the end of this sentence [1]. These will increase in number in order of appearance and display chronologically when a <references/> tag is inserted to the bottom of the page under a "References" header like so

  1. This making sense now?

Acceptable sources

Because of the amount if misinformation spread around the web, it's important for authors to only use credible sources.

Sources in English

baaaassiiccaalllyyyyyy make sure the information is accurate (so pretty much only stuff from the games, guidebooks, official artbook, or translated articles)

Policy on sources in other languages

  • need to be able to prove fluency in this language or provide a translated version to some extent
  • (Personally, I'll accept N3+ for Japanese and B2+ for any and all of the languages; basically just demonstrate that you’re proficient to me)

Policy on speculation, fanfiction, and theories

  • no Chuggaaconroy (or other YouTubers, really)
  • no theories
  • no unreasonable speculation (some is allowed when needed to explain things that would otherwise be confusing, like the difference in age between Mr. Bamboo and Isshaku)

External links

meant to be used mostly to show

Navigation Tables

Navigation tables are templates added to the bottom of pages to allow readers to access more articles within the same category of grouping. These are attached by enclosing the name of the template in double brackets at the very bottom of the page. This is to maintain uniformity and not detract too much from the main article. For a full list of navigation tables, see here.


To allow for easy and immediate indexing, this Wiki and many more make use of the Category feature. Admins on up can create categories for articles to go into, and no article should be without one. For a list of the Categories this Wiki has available, see Special:Categories:here.

As far as adding categories go, that's the easy part. Simply add the category you want an article to be indexed under to the bottom of the page like so: [[Category:category name goes here]] Now, an immediate example is a little tricky to provide, so feel free to explore the source code of other articles to get a better feel of how this feature both works and is added.

Extras to be added

Nutshell section
This section in a nutshell:

Some of the features that can be added to an article that improve the overall quality are:

  • Comments
  • Images and galleries
  • Tables
  • Links to other pages

In-line comments

<!--This is a comment!--> We use comments for a great deal of things on this Wiki. Most commonly, these are used to leave notes in the Source Editor to allow future authors a chance to learn more about the formatting of something or the way we do something else. In other computer languages, this same feature is used to explain pieces of code to new users or those who wouldn't understand why something is done one way when they would do it another.

<!--When using an infobox, don't forget to fill out the 'color' parameter.-->
Comments are also useful to block out code that isn't ready to be displayed or is acting differently than anticipated. You can often remove code or phrases entirely from the page without deleting them, to allow the page to exist without them while someone is working on fixing them in the background.
<!--{{{{Tt||why isn't this||working?}}}} This glitch needs further investigation-->
While comments aren't required, they are advised for users who will be doing a lot of heavy-duty coding that may require explanation for those less experienced or confused.


Images help to make an article visually interesting and less boring overall. Primarily, these are used to inform readers or break up massive walls of text. Attaching an image is easy. Simply upload the image here and then attach it to a page where it would fit best like so: [[Image:Picture_name.file type]]This line of code will place the following picture wherever it was inserted in relation to the rest of the article's existing images or text. Beyond this, there is a great deal of secondary formatting that can be included. For example, one can change the size of an image by telling the page how large the pixels are needed. To get 250 pixels, which is our standard here for most images, write [[Image:Picture_name.file type|250px]]. We're not done yet though! Now we have the option to align the image to the left, right, or center. And adding that to this little picture is as easy as last time. Simply tag tag "left", "right", or "center" right after the pixel size to force an image to go wherever one wants it to end up: [[Image:Picture_name.file type|250px|center, right, or left?]]. The last thing that can be added is a caption. Captions give a voice to images and allow authors to explain what's going on in a picture, and can be added like so: [[Image:Picture_name.file type|250px|center, right, or left?|Caption goes here!]]

  • provide information on how to take screenshots on PS2, Wii, PS3, and DS or merely provide links to guides


When an article has many images, or can be improved by having more, and having inline images may detract from the readability of an articles, the use of a <gallery> tag is encouraged. After inserting this tag, it is essential that more than three images are included, whether they are approved fanart, scanned images from the artbook, or screenshots of recorded gameplay.


Tables should use a "class" design when possible, and should include as little 'fancy' formatting as possible. Tables can also be made sortable by adding a "sortable" class.

For long tables, it is recommended to create an "alt" class to alternate row colours to enhance readability. The below examples use "toccolours" as a class, but this is only for the purposes of demonstration, and isn't generally recommended.

With row headings, table caption, sortable

I am a caption
Heading one Heading two Heading three
Row heading 1 Row data 2b Row data 3c
Row heading 2 Row data 2b Row data 3a
Row heading 3 Row data 2c Row data 3b

{| class="toccolours sortable"
|+ I am a caption
! Heading one || Heading two || Heading three
| class="title" | Row heading
| Row data 2
| Row data 3
| class="title" | Row heading
| Row data 2
| Row data 3
| class="title" | Row heading
| Row data 2
| Row data 3

Without row headings, with alt rows

Heading one Heading two Heading three
Row data 1 Row data 2 Row data 3
Row data 1 Row data 2 Row data 3
Row data 1 Row data 2 Row data 3
Row data 1 Row data 2 Row data 3

{| class="toccolours"
! Heading one || Heading two || Heading three
| Row data 1
| Row data 2
| Row data 3
| Row data 1
| Row data 2
| Row data 3
|- class="alt"
| Row data 1
| Row data 2
| Row data 3
| Row data 1
| Row data 2
| Row data 3
|- class="alt"
| Row data 1
| Row data 2
| Row data 3

Creating links to other content

One of the great features of any Wiki is the ability to link to existing pages anywhere around the web. Adding links is easy too, but there are different kinds, so it's easy to get confused.

Within this Wiki, adding a link as easy. Simply enclose the title of the page you want to connect to your article within double brackets. For example, if a user wanted to provide a link to this page, they would write [[Okami Wiki:Manual of style]]. This looks weird if an author wanted to say something else though. For example, say an author wanted to say:

If you need guidelines for writing articles, see here!
Okami Wiki:Manual of style
Adding that link by itself would look really odd. Luckily for us, we have the ability to rename links too! Changing a few things inside the brackets to look like this: [[Okami Wiki:Manual of style|here!]] renames the link so that it fits the author's needs and still directs users to the correct page. When finished, it will look something like this:
If you need guidelines for writing articles, see here!
But, you might say, not everything we use here is internal. Sometimes there's a need for external links as well. Lucky for us, this is easy to. Instead of double brackets, external links use single brackets. For example, if an author wanted to provide a link to Community, simply add the following: []. Renaming these kinds of links is slightly different than before, but nothing too terrible. Rather than use this: |, authors will instead create a space after the link and put the word or phrase they want to display on the page instead like so: [ Community]. This is because of the difference in the way Wiki itself handles both internal and external links. Regardless, adding a link is typically very easy, and should an author forget, this guide is always here, or they can rely on features within either Editor.

Now that everyone knows how to add and name templates, that brings us to one of our final points about adding links: naming. As authors may or may not know, we have a rather strict naming policy for images, and the same applies to links. We will not tolerate ridiculous names for links. Rather, appropriate use to redirect readers to other content is the primary goal. If the link needs to be renamed to fit within a particular phrase, do it. Otherwise, do not rename links unnecessarily.

About red links

Red links are created when a user tries to refer to a page that does not exist. Essentially, these are little red warnings for any user to correct the information on a page. Nearly every time, authors can avoid adding a red link by ensuring their spelling is correct and checking their work via the preview window. If you see any red, you know the link's dead!

Normally, this isn't too big a problem for other Wikis. However, we have had issues with rampant red-linking in the past at the hands of a former administrator, prompting the creation of Project Red link deletion. Having dealt with this level of severity, we do take this seriously and have some rather rigid guidelines for those who cannot be bothered to check their work for dead links.

Pages that do not exist

If a there is a link on any page to another article that does not exist, there is a strong chance that this will be removed and the user will receive a warning. However, if this link refers to an article that will go live on this site within the next few hours, feel free to do so, since the link will not be dead forever. However, if this is not rectified after a few days, the link will be assumed dead, removed or corrected, and the user responsible warned.

Pages that cease to exist

For pages that cease to exist, no blame is to be spread about, especially if a user did not know about a different page's demise. If contributors happen to come across a red link that refers to a page they know has been deleted, simply correct the link to refer to the proper page or remove the link altogether and leave the intended text behind.

About Templates

Templates are links to full list of templates in use

Using Templates

To add a template to this Wiki, simply find the one you want to use and then fill out the correct parameters. For example, adding {{Project improve ad}} will add the Project improve banner wherever it is placed on the page. Some of our more commonly used templates are:

Some of the more immediate useful ones, however, are the templates users can attach to the top of a page to inform other contributors about incomplete articles or articles that need immediate attention, such as correction of deletion. The templates used to accomplish this are:

All of these have a blue, clickable link in the middle of them that potential authors can view to gain more insight about the use of a template. If usage guidelines do not exist for a particular template, feel free to start a discussion on the Talk page of that template. A more experienced user will get back to you as soon as they possibly can.

Creating Templates

Explaining all of the ins and outs of a template here would take its own article, and luckily for us, you can find a fantastic guide right here! This will walk you through the how, so that we can go over the when and why here.

Templates need to be created in cases where something will be in high use, such as the {{Fang}} template or any number of the infoboxes. Usually, someone higher up in the bureaucracy will create a template that the community needs. However, this doesn't mean users cannot make templates for personal use. In fact, doing so, especially in a personal Sandbox, is highly encouraged.

Because of the looser guidelines surrounding the creation of templates, it's a good idea to find and ask a Staff member, Community Central or Vanguard.

Color guidelines

To learn more about color usage on this wiki, please see here for a more detailed guide.



Nutshell section
This section in a nutshell:

Authors are expected to use standardized American English when writing articles. However, this does not mean articles must be dry and bland. Rather, it is the opposite. The goal is to provide entertaining information with as much accuracy and color as possible.

Grammar is like a writer's toolbox, and the following sections will explain how to make good use of these tools, the first of which is grammar.

In order to allow readers to feel like they are experiencing the game again for the first time, it is essential that authors use a combination of third-person pronouns and an active voice. An example of this would be something like:

Struggling to overcome a need to be the hero, Oki let Kutone fall to the ground before running over to save a wounded Shiranui from the falling tree.
The following passage also goes on to explain another important point. Authors should try to combine creative writing elements, such as descriptive and visual language, with skills developed during training on the writing of informative essays. However, given the nature of a game like this, authors can rely more on their creative writing skills more than anything else, unless the situation specifies otherwise.

The final point of interest for any reader is a broad and varied vocabulary. Read the following passages and decide which is more interesting to read.

  • She used the sword to fight the demons. The sword was red, green, and grey and had a little purple gem in the middle.
  • She equipped a new Glaive before facing the legion of demons before her. The blade was a piercing silver, a striking collection of ruby and emerald ribbons of leather were loosely tied together around the handle, and a small, deep purple jewel lay embedded between the blade and the guard.

Authors should be inclined to choose the more appealing second passage versus the first, which makes use of the same word multiple times. Authors are welcome to and even encouraged to make use resources like dictionaries and thesauruses to broaden their word use when necessary. This is to ensure each and every article is as well-written as it is interesting. If an author ever uses an uncommon word or phrase and can find a good explanation, feel free to leave a link to the external page to allow confused readers a chance to learn a new definition. Often times, Wikitionary is a fantastic resource for this purpose.


Unlike many other Wikis, the title of any page should only contain one capital letter unless the games have set a different standard. For example, to write "Amaterasu and Issun" would be correct, but "Amaterasu's Adventure" would not, unless it was otherwise written like that somewhere in the game. This is why we have articles like the Ark of Yamato genocide and Moon Tribe cataclysm that appear to have odd capitalization. This is merely the way we do things as of right now.


Punctuation allows for readers of any skill level to make sense of whatever it is an author has written. Because of its power, this Wiki has some specific guidelines for regarding the usage of such.

As far as commas go, we make use of the Oxford comma. Essentially, what this means is that lists look like this: "cats, dogs, and birds"; and that two clauses are separated like this: "Knowing that he would not reach her before tomorrow, he put the phone down and went to sleep.".

Apostrophes are fairly easy to figure out. They are used in common contractions, such as "don't" or "can't", in addition to being useful for possessives, like "the dog's bone". However, in the case of a word ending in an "s", like "Celestials", authors are expected to follow the "s" with a single apostrophe and nothing more, so that it would read like so: "Celestials' demise".

Periods are yet another easy one. These are primarily used to finish off sentences, and nothing more. In fact, as far as sentence enders go, periods are the only ones that should be used in an article. A question mark (?) or an exclamation point (!) should never be used within an article, but rather, should be implemented at a user's discretion on other pages, unrelated to articles.

The last little tidbit of punctuation education is the use of parentheses. Unlike the majority of Wikis and widespread usage on the Internet, we do not tolerate the use of parentheses in place of commas or hyphens. The following, for example, would be wrong and considered in need of correction.

  • She knew he wouldn't be coming home (which is why she was crying)
  • He wanted to see what the community (or rather what was left of it) wanted to do to help rebuild the firehouse.

Both of these can be easily corrected to demonstrate proper use of English like so:

  • She knew he wouldn't be coming home, which is why she was crying
  • He wanted to see what the community--or rather what was left of it--wanted to do to rebuild the firehouse.

Failure to make use of these guidelines can result in a warning or a ban for repeat offenders.


As mentioned before, this is primarily an English Wikia, for the time being. Specifically, we use American English, which at times affects vocabulary and spelling, with more emphasis on the latter. Some odd features for those unfamiliar with the American dialect include "color" versus the British "colour" and "fiber" versus the British "fibre". Generally speaking, these are pretty easy to catch and correct, and should an author fail to do so, it isn't the end of the world. Often times, another contributor will come along and correct it for them. However, they should not rely solely on the work of others to correct their mistakes. Should rampant misspellings become an issue, members can be issued a warning or a ban, if the circumstances warrant it. Should an author be truly concerned about this matter, they can often add or change their browser language to something like English (American) to allow the browser to correct or highlight spellings that don't fit within the guidelines of American English.

When writing full articles, regardless of your native tongue, be sure to use "you" instead of "u" and "to" instead of "2". Articles should look like well-written essays and not text messages. We do understand that people edit via mobile phones, but this kind of language will not be tolerated from users, regardless of the platform they access this site on. If needed, take more time to write out full words and sentences or switch to a personal computer to maximize control and ease of use.

Title of works

Following the usual standard for American English, authors are expected to use proper formatting when inserting the titles of existing or soon to exist works. Primarily, this will apply to the writing of Ōkami and Ōkamiden. These, among others, should be properly spelled and italicized, which includes the use of 'Ō' in the names of both games. To access a shortcut to avoid having to repeatedly copy-paste this character and other macron characters, look for the "More +" button in the Edit window, click on it, and look for the macron character needed.

Hepburn rōmaji

Because of this Wiki's usage of the {{Nihongo}} template--one created to allow the appearance of Japanese text, readings, and translation--there is a need to have a standardized set of rules regarding the implementation of rōmaji in an article. For this Wiki, we make use of Hepburn rōmaji for both Japanese and Itak, language of the Ainu people upon which the Oina are based. The general rules for this variation of romanization are as follows:

  • し, ち, and つ are romanized as "shi", "chi", and "tsu"
    • じ, ぢ, and づ are in turn romanized as "ji", "dzi", and "dzu". The latter two should be acknowledged as being different than じ and ず even in rōmaji, simply because it is proper spelling
  • Long vowels--such as ああ, いい, うう, ええ, and おお--are romanized as ā, ī, ū, ē, and ō.
    • Others like えい and おう are written as "ei" and "ō", respectively.
  • Double consonants like だった are written like "datta", with two consonants to represent the chīsanatsu
  • Titles are to be separated from the name: カグヤ姫→Kaguya-hime
  • Particles do not need to be capitalized: アマ公の秘密→Ama-kō no himitsu
  • These same rules apply for Itak as well

If authors are ever unsure about these rules, be sure to ask an experienced Japanese language user such as Chaujiu, Weirando or Tormented Sufferer.

Guidelines for outlying category article creation

Character article guidelines
Species article guidelines
Location article guidelines
Location types
Technique article guidelines
Weapon article guidelines
Demon article guidelines
Demon class article guidelines
Boss article guidelines


With everything all said and done, authors should now be ready to take this Wiki by storm! However, since there is a chance some things may have been missed or not explained fully, please be sure to make good use of this guide's Talk page to gain further insight and clarification.

We hope you enjoy your time here~!

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.