This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dom6:wiki-styleguide [2026/05/29 08:33] wigglefig |
dom6:wiki-styleguide [2026/05/30 00:06] (current) wigglefig |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| This style guide provides guidance on how to make quality contributions to illwiki. If these guidelines seem too difficult to follow (non-native speakers, etc.), don't let them stop you from contributing! It is more important that the wikis have contributions than having everything "done right", | This style guide provides guidance on how to make quality contributions to illwiki. If these guidelines seem too difficult to follow (non-native speakers, etc.), don't let them stop you from contributing! It is more important that the wikis have contributions than having everything "done right", | ||
| + | |||
| + | Much of this style guide has been copied or adapted from the [[https:// | ||
| =====Dominions-specific language===== | =====Dominions-specific language===== | ||
| Line 10: | Line 12: | ||
| * In their [[http:// | * In their [[http:// | ||
| - // | - // | ||
| + | - //' | ||
| + | * No armor protection at all: naked | ||
| + | * <11 total prot: light | ||
| + | * 11-15 prot: medium | ||
| + | * 16-19 prot: heavy | ||
| + | * >20 prot: very heavy, super-heavy, | ||
| + | - //Unit stats:// Attack and defence skill can be lumped together as 'melee skills' | ||
| + | * <9: poor | ||
| + | * 9-11: average/ | ||
| + | * 12-13: good | ||
| + | * >14: great | ||
| =====Article organisation===== | =====Article organisation===== | ||
| Line 22: | Line 35: | ||
| =====Writing style===== | =====Writing style===== | ||
| + | - For most wiki articles, write in third person, avoid using first/ | ||
| + | * //Correct: Jotunheim has the option of focusing on either scales or a bless.// | ||
| + | * Incorrect: You should take a heavy bless and mass-produce Thrymshirdings for an early power spike. | ||
| + | - Use a semi-formal register. | ||
| + | * //Correct: Many players use MA Ulm's early strength to rush a neighbour, allowing them to gain an advantage in gold and gems over the rest of the lobby.// | ||
| + | * Incorrect: Ulm should obviously attack a neighbour early. How else would you play a nation of burly men in massive armour? | ||
| + | - Write in general, abstract terms. | ||
| + | * //Correct: Knights of Avalon are excellent against most types of independent province defense and perform well against other nations.// | ||
| + | * Incorrect: With a traditional Enchanted Blood/ | ||
| + | - Capitalisation should only be used for the first letter in a sentence, and proper nouns. The name of game mechanics do not count as proper nouns. | ||
| + | - The wiki views both US and UK English as acceptable languages and there is no need to correct between the two; however, consistency through a page is appreciated. | ||
| + | |||
| + | =====Wiki formatting===== | ||
| + | - The first thing on a page should be its actual title, made into a heading via this formatting code: %%======Title======%%. This should be followed by a general description of the page's topic. More in-depth discussion should be separated by lower level headings like %%=====this=====%%. | ||
| + | - Wikis work due to the use of internal links to other pages, the first instance of any other page should be linked with square brackets %%[[like this]]%%. | ||
| + | - Do not emphasize text with __underline__ or CAPITALS, use italics instead, in addition avoid excessive use of **bold**. | ||
| + | - Write so that everyone can participate: | ||
| + | |||
| + | =====Duplication of information===== | ||
| + | Duplication of information on the wiki is frowned upon and should be avoided where possible as it leads to increased maintenance overhead and display of outdated information even though it has been updated on other locations. | ||
| + | |||
| + | If a piece of info seems relevant to another article, consider simply linking to the article with that information. Create a sub-header with a link to the relevant page immediately underneath it. Follow with a concise summary of the target link's relevant information. | ||