OpenFront:Style
More actions
 | This page is a work in progress! Things may change and be added over time. Make sure to check back soon! |
This wiki vaguely follows Wikipedia's Style guide, thought to a much less strict standard, and along with some of its own standards. You can find the additional standards below.
The number 1 rule when deciding when to edit is to BE BOLD! If you think you can improve an article, go for it, and give it a try!
Article structure
An article should start with a 1-3 sentence introduction defining the subject and what it generally does, keep the details light. There should then be relevant "Heading" level chapters (no "Page Title") with optional sub-headings, and further.
Formatting
The article's subject should be bold, but only its first mention. A chapter's are sub-chapter's first mention of the chapter subject may also be bolded.
Math formulas from the game's code should generally be turned into standard(-ish) math formulation using math formatting. If a formula gets a little long, wrap it like so {{Scrollable Math|<math>x=0</math>}}, as this allows all screen sizes to view the formula properly. Try to break up large, complex formulas into smaller formulas each with only a few variables.
Linking
In each first instance of a concept with a page on the wiki, or whose further explanation is needed, add a link to that page (or wanted page). The link should be in sentence case, as long as it is derived from the subject's name, so for example "Cities" but "population building".
Links should generally only point to other articles and pages on this wiki, though exceptions can be made for Wikipedia (by adding a wikipedia prefix to the article name, for example: wikipedia:Game), and for the OpenFront's GitHub page, or other relevant sites.
Images
Adding images to articles is strongly encouraged, as they make them much nicer to read. Make sure images are relevant and mostly show only what you are trying to demonstrate. Where possible, use icons directly from the GitHub repository, or screenshots from the latest game update. Graphs may also be used to aid with understanding math formulas.
Tone
On article pages, try to keep the tone mostly neutral, informative, and use correct grammar. Avoid excessive punctuation, swearing, excessive jokes, etc. User pages, or other less public facing pages (such as the one you are reading) can be a lot more freeform.
Advice
You may add general pieces of relevant advice after explaining a mechanic on in an article's section. If there are many pieces of advice, or the advice is complicated and/or disputed, create a Strategy section instead. If there is even more strategy, a separate guide page may be more fitting, instead linking to that page by adding something like
under the Strategy heading. Factual, objective game mechanics should always go before subjective advice.