Caller's Bane Wiki:Naming conventions

Bellow are community guidelines for naming pages of. They are meant to clearly outline how titles should be chosen. Please follow them in order to maintain consistency throughout the site and make searches easier.

Language
Wiki rules still apply to page names:
 * Use North American English rather than Queen's English.
 * Refrain from using profanity.
 * Use an "encyclopedia" style.

Format

 * Use "sentence case", not "title case".
 * The initial letter of a title is capitalized.
 * Subsequent words in a title are not capitalized, unless they are part of a proper name, and so would be capitalized in running text. When this is done, the title is simple to link to in other articles.
 * Example: "Version history", not "Version History".
 * Use the singular form.
 * Example: "Scroll", not "Scrolls" (speaking about the game element). Note that Scrolls is a valid title as the name of the article about the game itself.
 * Exceptions include nouns that are always in a plural form in English.
 * Use nouns or noun phrases.
 * Example: "Sacrifice", not "Sacrificing", nor "How to sacrifice".
 * Sometimes the noun corresponding to a verb is the gerund (-ing form).
 * Avoid definite and indefinite articles.
 * Do not place definite or indefinite articles ("the", "a" and "an") at the beginning of titles unless by convention it is an inseparable part of a name (e.g. if a card name starts with an article).
 * Example: "Battlefield", not "The Battlefield".
 * Avoid abbreviations.
 * Avoid ending with a punctuation mark.

Special characters
Technically all other Unicode characters can be used in page titles; but some characters should still be avoided, or require special treatment:
 * There are technical restrictions on the use of certain characters in page titles. The following characters cannot be used at all: # < > [ ] | { } _
 * There are restrictions on titles containing colons, periods, and some other characters.
 * Characters not on a standard keyboard: use redirects.
 * Sometimes the most appropriate title contains diacritics (accent marks), dashes, or other letters and characters not found on most English-language keyboards. This can make it difficult to navigate to the article directly. In such cases, provide redirects from versions of the title that use only standard keyboard characters.
 * Example: "Jakob Porser" redirects to "Jakob Porsér".
 * Characters resembling quotes or accent marks: avoid them.
 * The characters ʻ ʾ ʿ ᾿ ῾ ‘ ’ “ ” c, and also combining diacritical marks with a "space" character, should generally not be used in page titles.
 * A common exception is the apostrophe ', which should, however, be used sparingly.
 * Symbols and characters not supported on all browsers: avoid them.
 * If there is a reasonable alternative, avoid characters that are so rare that many browsers cannot render them.

Article names
A good article title has the following characteristics:
 * Recognizability
 * Titles are names or descriptions of the topic that are recognizable to someone familiar with Scrolls.


 * Naturalness
 * Titles are those that readers are likely to look for or search with as well as those that editors naturally use to link from other articles.


 * Precision
 * Titles usually use names and terms that are precise enough to unambiguously identify the topical scope of the article, but not overly precise.


 * Conciseness
 * Titles are concise, and not overly long.


 * Consistency
 * Titles follow the same pattern as those of similar articles. See explicit conventions.

These should be seen as goals, not as rules. For most topics, there is a simple and obvious title that meets these goals satisfactorily. If so, use it as a straightforward choice. However, in some cases the choice is not so obvious. It may be necessary to favor one or more of these goals over the others. This is done by consensus.

Redirects should be created to articles that may reasonably be searched for or linked to under two or more names (such as different spellings or alternative names). Conversely, a name that could refer to several different articles may require disambiguation.

Category names

 * Standard article naming conventions apply; in particular, do not capitalize regular nouns except when they come at the beginning of the title.
 * Example: "Spell scrolls", not "Spell Scrolls".
 * Names of topic categories should be singular.
 * Example: "Scrolls game" category contains pages related to the game.
 * Names of set categories should be plural.
 * Example: "Spell scrolls", not "Spell scroll".
 * Don't write the category structure in names.
 * Example: "Scroll images", not "Images - Scroll images", nor "Images - Scrolls".
 * Choose category names that are able to stand alone, independent of the way a category is connected to other categories.
 * Example: "Scroll images", not "Scrolls" (a subcategory of "Images").

File names

 * File names should be clear and descriptive, without being excessively long.
 * While the image name doesn't matter much to the reader (they can reach the description page by simply clicking on the image), it matters for editors. It is helpful to other contributors and for maintenance of the wiki if images have descriptive or at least readable file names.
 * Example: "Ancestral Totem.jpg" is more helpful than "20121003133742.jpg".
 * Generic file names should not be used.
 * To avoid accidental overwriting of images or other media, very generic filenames should not be used when uploading.
 * For example, an image of a scroll should not be given the name "Scroll.jpg", as sooner or later someone else will try to do the same thing and overwrite the old image. The new image will then appear wherever the old one was used – in this case, an scroll article would then show the wrong scroll image.
 * End file names with the (lower case) extension corresponding to the file format, just as you would do for a file on a storage device.
 * Examples: End JPEG image names with ".jpg", end PNG image names with ".png", end SVG image names with ".svg".
 * Regarding images, if possible, prefer vector graphics (such as SVG) over raster graphics (such as PNG, JPEG, and GIF).
 * Like other wiki page names, file names are case sensitive except for the first character, which will always be normalized to uppercase.

Template names

 * Template names should be clear and descriptive, without being excessively long.
 * The name should give an idea of what is the purpose of the template to users who don't know it.
 * An exception is templates whose purpose is to provide a shorthand for other templates or wiki formatting, in which case not giving a short name could defeat their purpose.
 * Example: Tl which stands for "template link".
 * Abbreviations can be used sparingly if full words would make the template name too long.
 * Use spaces to delimit words in the template name.
 * Avoid underscores.
 * Avoid sticking words together, even if the first letter of each word is capitalized.
 * Above are naming conventions of programming languages whose identifiers cannot contain space characters. Template names can, so make use of it.
 * Example: "Documentation subpage", not "Documentation_subpage", nor "DocumentationSubpage" nor "Docsubpage".
 * Create a template subpage for templates that are intended to be only used within that template.
 * Template subpage names (i.e. after the slash character) should not be capitalized.
 * Example: "Infobox/row" (which is a template only to be used in a parameter of the "Infobox" template), not "Infobox row", nor "Infobox/Row".
 * Example: Template documentation subpages ("/doc") are to be transcluded only in the template they document.

Explicit conventions
Further guidelines may be given in category pages when specific conventions apply to the pages they contain or the type of pages they represent.

This includes:
 * To be determined...