Taming.io Wiki:Manual of Style

This page in a Nutshell

• Keep writing as objective as possible. Unless in guide pages, personal comments will not be tolerated.
• The title of pages that talk about multiple features must be plural, whereas others must be singular.
• Pages with very little content should be merged with more general pages.
• Add categories to pages where appropriate.

This guideline sets a standard on how one may edit a page in this wiki, which is to ensure a consistent page layout across this wiki. It also assumes you are using the source editor. First and foremost however, human judgement should be applied if there is a consensus that it should be some way. If you would like to propose changes to this guideline, you can do so here.

This page does not guide on how to do the actions mentioned here. To learn about that, refer to Community Central or ask our admins.

Merging

If a page does not have enough information to the point where it is inconvenient for the reader to go to it, merge it with another more general article. For example, if Stone Sword simply said "The Stone Sword is one of many swords in the game." then it would be appropriate to merge it with the swords page.

Naming

Namespaces

• Pages which talk about some in-game feature must be under the (Main) namespace.
• Pages which do not cover real in-game features must be under the Fanon namespace.
• Pages which include loads of features must be under the (Main) namespace, with a counterpart on the Category namespace.

Capitalization

• Files and categories must have the first word capitalized and every other word after it lowercased.
• All other pages must have the first word and every noun in it capitalized, and any other words must be lowercased.

File Naming

Files are best named if they are easy to find and if they follow a consistent syntax.

• If there are already files similar to the one you are uploading, use the same syntax as them.
• Files with ambiguous file names may be named how they are found in the game files, using the following syntax: <folder>-<filename>.extension.
  • You may do it vice-versa, too: <filename>-<folder>.extension, if that way sounds more natural.
• Files with ambiguous file names may be named with an adjective or a noun before the file name, using the following syntax: <adjective/noun>-<filename>.extension
  • You may do it vice-versa, too: <filename>-<adjective/noun>.extension, if that way sounds more natural.
  • You may use multiple adjectives/nouns if needed.
• Files with unambiguous file names (like sapphire axe) may be composed solemnly by the file name.
• You can also choose not to use the filename, but rather another name that still describes well the file.
• In case filenames have multiple words, separate them by underscores.

Plural

• Pages which talk about only one feature must be written in their singular form.
• Pages which talk about many features must be written in their plural form.
• Infoboxes must be written in their singular form.
• Navboxes must be written in their plural form.
• Other templates may be written the named it's most natural.

Content

• Comments that guide future editors should be added by virtue of HTML5 comments (<!-- comment -->), which may be added by the visual editor aswell. They should never be seen by the actual reader, in a footnote or otherwise. You may also consider adding it to a comment to the page or adding that to its talk page.

Writing

• Keep in mind the scope of the page. You may and should establish a relation with the subject of the article and another item (appletors and animals, for example), but to then elaborate that it can be obtained at age 5 is better left on the appletor page.
• Articles must be written using proper American English.
• Avoid abbreviations for the sake of clarity.
• Avoid repeating the same ideas already present in the page except if that information is in an infobox.
• Write everything in a concise, objective manner. Do not include personal opinions or ideas. For that reason, 1st and 2nd person pronouns must be avoided.
• Do not add history trivia to the page except in dedicated sections.

Suggestions & Bugs

Neither should be present in a wiki page. Suggestions must be sent in via Discord or Reddit, and bugs must also be reported via Discord or Reddit.

Formatting

• Bold text must be used in the first mention of the page's name and to highlight an important piece of information. It must not be used to put emphasis on an idea.
• Italic must be used in all instances of the name of the game (Taming.io - see also {{Game}}) -, in all instances of the game developer (LapaMauve), and when putting emphasis to an idea.
• Underlining, strikethrough, ALL CAPS, small caps or anything of the sort is best avoided altogether.
• Template parameters must be named with all words lowercased and separated by an underscore (a.k.a. snake case). When talking about a parameter, use the <code> tag to format it.

Links

• Entities and items that are named in-game must be treated as proper nouns (e.g. Stone Sword, Wolf, Dragon Egg), while groups of entities must not (e.g. swords, animals, bosses).
• The first mention of another page must be a link. Other mentions should not be links unless the last link is inconvenient to locate or if the formatting makes it more appropriate to do so (like in tables or infoboxes).

Categorization

• Category trees should go only in one way, and not fold in itself.

If: Category:Templates -> Category:Infobox templates -> Template:Animal Infobox
Don't: Category:Templates -> Template:Animal Infobox

• In the case of pages which have a category counterpart, they should be included in the category page. For example, Category:Items has a (Main) page counterpart, items, and therefore, items should have Category:Items in it.