Dovedale Wiki:Style Guide

Discord Forms Guidelines Rules Staff FAQ Policies & Terms

Introduction

This style guide aims to ensure a professional environment on the wiki, and to ensure pages are uniform and easy to read. The style guide provides an extensive guide to issues such as capitalisation, orthography, abbreviation, punctuation, spelling, numerals and many other questions of language usage.

This style guide also assumes you are using the Source Editor.

Style

Orthography

Here at the Dovedale Railway Wiki, please write in British English. This applies to the spelling (centre not center) and grammar (burned not burnt) of words and sentences. Differences in vocabulary are excusable (such as autumn and fall).

There are some exceptions to this rule:

If the game quote is in any other English dialect, you are not to amend the quote.
Double constants are preferred when used in British, Canadian or Australian English (for example, labelled not labeled).
If the names of objects or standards are formally recognised, such as in the case of units or chemistry, you are to use those instead.
- metre not meter (Le Système international d'unités).
- aluminium not aluminum (International Union of Pure and Applied Chemistry).

Wikitext

Please use wikitext text formatting over HTML text formatting, unless neccesary. ( ' ' 'bold' ' ' over <b> bold </b> )

When formatting templates, you are to only have one line per input, unless there is only one parameter.

Correct:

{{Robux|1}}

Correct:

{{Passing_Loop
|image=
Day view=A view of benyhone loop and signalbox from the direction of FM.png;Overpass=Benyhone overpass.png
|tracks=2
|location=Between [[Fanory Mill]] and [[Llanfairpwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch|Llanfairpwll]], next to [[Benyhone Loop Signal Box]]
|signal_box=[[Benyhone Loop Signal Box]]
|catch_points=At both ends
|status=in_operation
|status_description=Since [[Update Logs#Version_1.1.0|Version 1.1]]
}}

Punctuation

Avoid comma splices. That is, independent clauses should be separated by a semicolon, a terminal ending or a colon, but not by a comma:
- Correct: Her romances are entertaining; they are full of exciting adventures.
- Incorrect: Her romances are entertaining, they are full of exciting adventures.
The Oxford Comma should only be used when its absence could create ambiguity or change the meaning of the subject.
- Correct: I need to buy apples, bananas and oranges.
- Incorrect: I need to buy apples, bananas, and oranges.
- Correct: My favorite foods are pizza, macaroni and cheese, and crackers.
- Incorrect: My favorite foods are pizza, macaroni and cheese and crackers.
Do not use ampersands (&) in replacement of ‘and’.
You are encouraged to write in full instead of abbreviations.
- The only exception of these are in infoboxes, where space is limited.
Apostrophes should be used correctly. In addition, you should only use straight apostrophes (') not curled ones (’).
- Correct: The cat licked its paw
- Incorrect: The cat licked it's paw
- Correct: It's raining outside
- Incorrect: Its raining outside
Always have a space succeeding a comma, like so.
When using brackets or parenthesis, you need to add the correct terminal endings if they are at the end of a sentence.
- Correct: You can spawn a train at Fanory Mill (Class 377).
- Incorrect: You can spawn a train at Fanory Mill (Class 377)
- Correct: (You cannot spawn a train at Satus Services.)
- Incorrect: (You cannot spawn a train at Satus Services).
Avoid using ellipses(...) , unless copying a game quote.
Avoid ending a sentence with exclamation marks (!) or question marks (?), unless copying a game quote.
Whenever a name with a terminal ending ends a sentence, do not repeat that terminal ending.
- Correct: John Doe, Ph.D.
- Incorrect: John Doe, Ph.D..
A space must follow every comma and period.
- Correct: Masonfield, Marigot, Pallion and Gleethrop.
- Incorrect: Masonfield,Marigot,Pallion and Gleethrop.
Quotes should be written using a quotation mark ("), not an apostrophe (').
All quotes should be a direct, word-for-word transcription of the original text. No text should be altered, even though there may be errors or conflicts with this style guide. In this case of an error, you may use [sic] to denote this.

Numbers, Dates and Currencies

All numbers up to ten should be spelt out in text format (one, two three). Numbers after ten may be written in numerals (21, 22, 23).
- This does not apply to tables, update logs, quotes or infoboxes.
- You should not start a sentence with a numeral. Spell it out or add a word in front so you can use a numeral.
  - Incorrect: 58 people attended the shift yesterday morning.
  - Correct: Fifty-eight people attended the shift yesterday morning.
  - Correct: A total of 58 people attended the shift yesterday morning.
The word percent is preferred over the symbol (%), with the exception of tables, update logs, quotes or infoboxes.
Notation of currencies should come before the number, if you are not already using a template (example 1000XP over XP1000).
- Do not shorten Robux as R$, but use the {{Robux}} template. For example, 150.
All dates should be written in longhand form, and should follow the order of DAY/MONTH/YEAR. Do not shorten the month, year, or anything else.
- Do not append ordinal indicators (-st, -nd, -rd) for dates.
When writing numbers with ordinal indicators (-st, -nd, -rd), use the superscript wikitext formatting option by typing <sup> text </sup> .
Numbers should be formatted with a comma as the thousands separator, for digit grouping, and a period (or full stop) as the decimal separator. Numbers above 1,000 should all have a thousands separator.
- Correct: 12,000
- Incorrect: 12.000
For time, a 24-hour format is preferred over the 12-hour format.
- Avoid redundant words, e.g. Do not say 16:00 in the afternoon.
All times should be in the Coordinated Universal Time (UTC) timezone. Do not add a time, following another separate timezone.
For units, use the following:
- Length - Studs
- Speed - Miles Per Hour (may be abbreviated as mph) or studs per second (may be shortened to sps, to be used only for legacy calculations)
- Time - Hours, Minutes and Seconds

Writing and Formatting

No profanity is allowed in articles, with the exception of appropriate offsite links, and quotes.
- You may be punished under the rules for adding profanity.
- This includes light profanity such as 'shit', 'damn', etc.
Avoid contractions (cannot over can't).
Roblox is preferred over ROBLOX.
When mentioning any notable user, like a developer, check that that is their most updated name. Searching their previous name on the Roblox website can yield their current name in the search results.
- Correct: cl0vermead0w
- Incorrect: l1z4rdju1ce
- Incorrect: happyshalala
When mentioning other games or brand names, use italics, and the full brand name. For example: Stepford County Railway, British Rail and Arena: Tower Defense!
- In addition, you should avoid shortening names of brands or games. For example, Great Western Railway is to be used over GWR.
If the articles name is repeated further in the main text page, it should be bolded.
All quotes in quotation marks should be written in italics. You should try to use the {{Quote}} template when writing quotes.
If a hyperlink to a page on this wiki, or another website is appropriate and available, it generally can be repeated for every instance.
If you are linking to a certain section, you should always use the Anchor Tag to allow readers to jump to the section.
- Example:
```
 [[Satus Services#Gallery|Photos of Satus Services]]
```
Bullet point indentation should be used if there is a further point that can be stated about a previous bullet point.
- This should not be excessively used to the point where the text is far from the left side of the page.
Bullet points should not be used in replacement of using conjunction words, unless the list is long.
The term "removed" should only be reserved to features, items or enemies that no longer appear in the game for the majority of people.
- It should not be removed from the term "unobtainable", such as badges that still exist, but cannot be obtained.
- Items that are obtainable by a small amount of players such as the Class 411 are considered "admin-only" content, not removed.
- Items that have been previously obtainable for all players but are not exclusive are to also be labelled appropriately.

Editorial Style

Neutral Point of View

All content on the wiki must be written from a neutral point of view (NPOV) - that is writing in a way that is representing the subject fairly, proportionately and as far as possible, without editorial bias.

Avoid stating your own opinions and facts - this is not your own blog, but a game encyclopedia.
Don't add seriously contested assertions as facts.
Avoid stating facts as opinions.
Use nonjudgmental language - you should neither sympathise or disparage your subject, although this sometimes can be balanced with clarity.
Always identify and indicate the relative prominence of opposing views.

A very guide on this topic is available on this wikipedia content policy page.

Write for your audience, not your peers

Use simple and easy to understand terms. Remember, people are coming to the wiki to learn things and allow people understand, and they may not. Most are not familiar with the topic, that is why they are on that page, to read. Use simple easy to understand terms over fancy jargon.

Your goal is not to impress your peers, but to allow the audience to easily read learn and understand the subject.

Files

Name files descriptively and appropriately. Avoid random strings of texts, or joke names, unless you are using it for personal pages or user blogs.
No players or surface user interfaces should be visible on infobox photos.
Train photos should be taken at an angle where at least the first carriage can front can be seen. There should be no obstructions like signals or players.
Freecam should be used to take photos.
If you are replacing a file, please check it is not being used for archival purposes.
File replacements should not be done for a new version of something. For example, if Satus Signal Box got an overhaul, instead of replacing the image with its old appearance, upload a new image.
Ensure you clear all sensitive EXIF data before uploading a file. Not all data is scrubbed when uploaded to MediaWiki. See this page for more.

Grammar

Proper Nouns should always be capitalised.
- Correct: The level crossing is located along Satus View Drive.
- Correct: There was a fire at the Training Centre.
- Do NOT capitalise designations, such as teacher, lawyer, manager.
It is generally fine to shorten et cetera to etc., and id est to i.e. For lists, etc. counts as its own item, so must be preceded with a comma.
- Correct: Singapore, Thailand, Malaysia, etc.
- Incorrect: Singapore, Thailand, Malaysia etc.
- Incorrect: Singapore, Thailand, Malaysia and etc.
Trains should be always referred to by their classes, unless there is no applicable name, or you are specifying a specific train.
- Correct: Class 43
- Incorrect: HST
Articles should be written in the present tense, except those with pages that refer to removed or discontinued things.

Article Style

Titles

Titles and infobox titles are normally written in title case (Satus Signal Box versus Satus signal box). Only the first letter of a major word should be capitalised, unless specifically spelt otherwise. Conjunction words should not be capitalised.

Tabbers

Tabbers allow you to place multiple similar pieces of information on a page while saving space. Tabber titles should be succint, due to limited screen real estate. If you are conducting a large amount of formatting inside a tabber, it is acceptable to nest a template inside the content section, so as to avoid style conflicts.

Infoboxes

The type of infobox depends on the page you are editing. All values should correspond to a value in the infobox. It is preferred to leave parameter values empty, if it does not apply or does not exist. Additionally, an infobox can use a tabber for items like images if there are multiple images that are suitable to apply for an infobox. You should only add these images if they are important. Other images can go into galleries. You are to follow the following tabber guidelines for tabbers in infoboxes:

Station - Exterior View, Other notable entrances/exits/shops/counters, Platform View (optional)
Company - Company Logo only
Train - Exterior View (showing clearly, at an angle, the entire train), Interior View (optional)
Landmark - Exterior View, Interior View (optional)
Crossing - Exterior View only
Signal Box - Interior View(s), and Exterior View, Charts (no in-game screenshots) only
Siding - Exterior View only

Quotes

Quotes must succeed the infobox to avoid styling issues. They should be placed in the {{Quote}} template. A grammatical error within a quote should be denoted with "[sic]".

Facilities

This only applies to stations. Things like toilets, shops and waiting rooms may be identified in this section.

Gallery

This is where any images or videos relevant article should go. Before uploading any photos, ensure they are in good quality (unless it is for a removed item, and you have made a reasonable effort to retrieve a better image), and are relevant to the page.

Trivia

This is where any information not relevant to the other pages should go. Any information here must be noteworthy. This includes any superlatives and should not include mundane comparisons or information. Do not insert real world information unless it is directly related to the game.

Navboxes

Relevant navboxes should be placed at the bottom of the page for pages in categories like stations, landmarks and trains.

Edit Summary

You are encouraged to add, and write a descriptive edit summary that can help people in the future decipher what you edited, without going to the edit page.

Article Creation

Before starting a new article, it is best practice to ask a staff member if you should create a page, unless it is a new station, landmark or train being added in an update.
Unreleased (such as sneak peeks), cut or exclusive content should generally not be added unless permission has been given from wiki staff.
Admin/Developer inserts should not be added. Only trains that are able to spawn via buttons or the :spawntrain command are to be added. (i.e, it is in the game files, and is not inserted using the :insert command)
- An exception is for all company trains, which are only limited to the company page and its subpages.
Consider the following before making your article:
- Look at similar articles - is there something already covered?
- Notability – should this topic have an article?
- Search for an existing article - does it already exist? Possibly under a section?