Baystation 12:Manual of Style

From Baystation 12
Jump to: navigation, search

The Manual of Style (or MOS) is a set of guidelines that are to be followed when editing pages.

Page Creation

Article Titles

  1. Article titles follow Title Capitalization.
  2. If the article title is within the lead section, it must be bolded.
  3. If the article is on an object that appears in game, it must be exactly as it appears in-game, with exception to capitalization
  4. Article titles should not contain a suffix, except where absolutely unavoidable. (Such as when referring to a species)

Notability

Articles must be one of the following :

  1. Contain enough information to warrant a new page
  2. Be part of the game. eg, an object.

Articles must not be one of the following :

  1. Unreleased or removed content
  2. Joke or hoax articles
  3. Created for the purpose of advertising specific servers or other products are not allowed.

Editing

Style of pages

When creating a page, use the same style as other pages of the same category. This helps both readers and editors, as it lets readers get accustomed to the site and how to find information.

The following must be made of similar style, based on the relevant project page:

  • Header names and order
  • Referencing style
  • Navigation boxes
  • Categories

Writing

  • To emphasize points and other (see below), articles must not use bold, ALL CAPS, underlining and similar methods.
  • It is not appropriate to use these methods when identifying a subject. This is what headers are for.
  • If there is an important notice, you can use these methods to emphasize this. However, it may be more preferable to use warning templates.
  • Boldface in particular is reserved for headers and wiki maintenance.
  • You should not use it to expand and emphasize acronyms (United Nations)
  • If a page is not an article, such as a wiki guide (not to be confused with gameplay guide) or maintenance page, they can ignore this rule (such as this page).
  • Articles must always begin with a summary paragraph, followed by a level 2 header.
  • Acronyms are always all caps.
  • Headers should always have a summary of the content if it is a single topic. If it is a collection of topics, then the summary can be absent.

Articles should "flow." This means that they are not "chopped up" into smaller sections by icons, pictures or templates.

Italics

The use of italics should follow good English print style.

It can be used for:

  • Mathematics/Variables (E = mc2 , ISBN)
  • Cross-referencing (The humans also interacted with Skrell (see Skrell).)
  • Introducing new words (Flimflam.)

It should not be used for:

  • Title emphasis (The Dragons species)

There may be special use cases. If you are not sure, ask an experienced editor.

Jokes

Jokes are only allowed when used sparingly and do not affect the flow of an article.

Linking

  1. Linking must not be more than 10% of the article.
  2. Links must only be linked once at the first instance of the appearance of the link, with exception to templates and tables.
  3. Unless it affects the wording of an article, two links should never be beside each other.
  4. Article links should not be capitalized, create a redirect or use the alt title feature.

Linking a redirect is preferred over a piped link.

Redirects

Redirects are acceptable under any of the following conditions:

  1. Alternative spelling of the title, such as "Armour" for "Armor"
  2. Alternative or shortened name, such as "Torch Bridge" for "SEV Torch Deck B Bridge"
  3. Previous article name, such as a recently merged article.
  4. Alternative capitalization or form, including changing the title to a plural case.

Templates

Articles, regardless of content, should always strive to have an infobox and navbox. These allow users to more easily identify quick information and find other links.

Headings

  1. Headings always use level 2+ headers.
  2. Headings follow sentence case.

Content

  1. Articles must not contain notices of bugs, glitches or problems in the game. This is to both reduce workload when the bug is inevitably fixed, and prevent misinformation or breaking of the flow of an article.
  2. Articles must not contain HTML if markup is available, this is targeted at HTML codes such as bolding, tables, etc. This does not apply to backend pages (IE. templates)

Minor vs. major edit

  • A minor edit is an edit that nobody can dispute - for example, a grammar fix or fixing a missing link.
  • A major edit is anything that involves changing or adding to the content - for example, adding links, rewording sentences and moving content.

Quality standards

Baystation 12 has a set of quality standards so that articles are written in a concise and consistent manner.

  • Prefer vocabulary common to all varieties of English. Insisting on a single term or a single usage as the only correct option does not serve the purposes of an international wiki.

Consistency

While Baystation 12 does not prefer any national variety of English, within a given article the conventions of one particular variety should be followed consistently. The exceptions are:

  • proper names: Use the subject's own spelling e.g., joint project of the United States Department of Defense and the Australian Defence Force;
  • passages explicitly discussing varieties of English;
  • URLs: Changing the spelling of part of an external link's URL will almost always break the link.

Universally used terms are often preferable to less widely distributed terms, especially in article titles. For example, glasses is preferred to the national varieties spectacles (British English) and eyeglasses (American English); ten million is preferable to one crore (Indian English).

  • If one variant spelling appears in an article title, make a redirect page to accommodate the other variants, as with artefact and artifact, so that all variants can be used in searches and in linking.
  • Terms that differ between varieties of English, or that have divergent meanings, may be glossed to prevent confusion, for example, the trunk (American English) or boot (British English) of a car ....
  • Use a commonly understood word or phrase in preference to one that has a different meaning because of national differences (rather than alternate, use alternative or alternating depending on which sense is intended).

Grammar

We follow Wikipedia's grammar standards.

Similar pages

In general, if another page is similar in topic (E.g a colony page), articles should try to follow the style and layout that previous articles have already setup. Efforts should be made to make these pages consistent with one another.

Uploading

Icons / Sprites

  1. Icons / Sprites must be at their original size (most common sprite is 32x32) or upscaled to double the size.
  2. .PNG format
  3. Transparency must be kept.
  4. Icons are only acceptable when they are a direct rip from the source - with exception to icons that would be aesthetically unpleasing in their default state.
  5. Up-scaled icons must be done by nearest neighbor.

Screenshots

Screenshots of the world can be done in the editor, however, it is preferred that the screenshots be taken in game.

  1. .PNG format
  2. Screenshots must be kept borderless (no window visible.)
  3. Screenshots must not contain multiple windows, as to preserve readability.
  4. Screenshots of locations must not have the standard HUD visible.
  5. Screenshots must be up to date, and must not contain any visible bugs or glitches, as to maintain sanity.

Other images

  • Images taken from other websites must comply to copyright.
Any images that do not comply with copyright will be deleted.
  • Images must be of high quality and should relate to the article.
  • "Real" images should be used sparingly.

Templates

Most articles have set templates avaliable. You can view them here.

Layout

Each article requires to follow a specific layout to maintain consistency. This is primarily for templates and notes.

Sub-pages

Sub-pages are acceptable under any of the following conditions:

  • They are a proposed rewrite of a page.
  • They are of a player guide.

Documents

Using the Document: namespace is acceptable under following conditions:

  • There is the preceding template {{template:document}} by default, or a custom document template (based on template:document) for multiple documents.
  • References and notes are kept at the end of the template through {{close}}.
  • Other details about the document can be placed after the document.
  • Only one document per-page is accepted. You can use sub-pages for multiple pages.

Documents must be kept in the "Document" namespace. Documents can both be linked or referenced by an article. References are preferred.

Infoboxes, sidebars and navboxes

  • There can only be two sidebar or infobox elements at any given time.
  • If there is more than one navbox, they must be in a collapsed state.

Lore

Lore has different rules from the rest of the wiki. View them here.

Vandalism

Vandalism is reverted immediately. Vandalism is defined as a edit with malicious intent - such as spamming, advertising another site, blanking pages, etc. Exact definition is admin discretion (within reason.)

Copyrighted content

Copyrighted content is any content that belongs to somebody else. This is a global wiki rule and works outside the manual of style.

Images and literature

Before uploading or submitting content ascertain the image or written content is:

  • Own work: You own all rights to the image or content, usually meaning that you created it entirely yourself. In case of a photograph or screenshot, you must also own the copyright for all copyright-protected items (e.g. statue or app) that appear in it.
  • Freely licensed: You can prove that the copyright holder has released the image or work under an acceptable free license. Note that images that are licensed for use only on Wikipedia, or only for non-commercial or educational use, or under a license that doesn't allow for the creation of modified/derived works, are unsuitable. When in doubt, do not upload copyrighted images.
  • Public domain: You can prove that the image or work is in the public domain, i.e. free of all copyrights.
  • Fair use: You believe that the image or content meets the special conditions for non-free content, which exceptionally allow the use of unlicensed material, and you can provide an explicit non-free use rationale explaining why and how you intend to use it.

Plagiarism

Plagiarism is NOT copyright infringement. However, all content from open-sourced wiki's must be attributed to their original creators. Most other Space station 13 wiki's do not have a copyright and are considered open-source - this does not mean that you are free to copy and replicate the content on this wiki. We do not allow plagiarism. All works that are taken from, or derivative from - including sources that are derivative from our original works - must be properly attributed in at LEAST the talk page or sourced at the bottom of a page. An exception would be if the content is a derivative work from Baystation 12 directly, and is nearly identical to it's source material. (E.g, a table.)

Lore is included in this, plagiarized lore will not be tolerated without proper attribution. If the content is directly ripped from a literary source, it will not be acceptable.

Server content

All copyright issues with images or works that are from the server code itself must be dealt with by developers. Contact them if you see a copyright issue within the game sprites / code. If any sprites or content is removed from the code, it must be removed from the wiki as well.

Page length

We try to stay around a readable prose size of 50,000 bytes for long pages. Anything longer and the page may become difficult to read. Pages under 2000 bytes should be considered stubs. See Special:LongPages - if a page becomes too long, instead of deleting content, split it into other articles.

Enforcement

Enforce it whenever necessary! However, keep in mind:

  • Enforcing the MOS may anger some people; not everybody will agree with your interpretation. Be prepared to defend your edit, just citing the MOS may not be enough.
  • Do not force it where it turns into an edit war - if it comes down to it, the style is up to the admin in charge.
  • It's important to remember that the MOS is a set of guidelines, it's what we go to when we want to make a good page. Just because it says it here may not mean it is necessarily correct. Ultimately, it is up to the wiki administrator.
  • Although we try to use similar enforcement as some sites such as Wikipedia, it is important to note that we are not Wikipedia - enforcing their high standards is too much for many casual editors.
  • As stated earlier, follow the spirit of the guidelines. Sometimes the MOS may not apply to what people are doing. Don't try to enforce it where you think it may not be necessary.

Failure to abide

It's important to note that ignorance of the MOS can or may excuse the mistakes of a newcomer. Although we try to get as many people to read it before editing, sometimes it can slip their mind or they think they already know what they are doing. In fact, you can violate the MOS by attacking a newcomer for not following it. Instead, use tags, discussion and inform them of the issue as gently as possible.

Try to:

  1. Always choose a compassionate and gentle persuasive approach.
  2. Approach challenging behaviors as a self-protective and responsive behavior occurring as a result of triggered/unmet needs.
  3. Moderate your approach and wording.
  4. Take responsibility for resolving conflicts.
  5. Always explain reverts in the edit summary, and use plain English rather than cryptic abbreviations.
  6. Listen actively.

Try not to:

  1. Infantize a newcomer, impulsive labeling as a vandal, outpacing the newcomer with policies instead of educating with core ones, ignoring and reverting newcomer concerns and contributions in their active presence of editing.
  2. Use acute and repetitive paraphrase of intimidation language, confrontations and quizzing with respect and confidence.
  3. Use sarcasm.
  4. Use excessive jargon.
  5. Use intensifiers in commentary (e.g., exclamation points and words like terrible, dumb, stupid, bad, etc.).

I got enforced by the MOS

Have you felt the fury of the MOS? Follow these steps.

  1. Know that the editor isn't after you personally. The editor is simply doing their duty, they are not personally after you - if you think they are, you should contact an administrator first.
  2. Choose to learn from the incident. Why is the guideline in place, why does it apply to what you are doing? Even if a guideline may seem silly to you at first, it may be there simply to prevent bad habits.
  3. Find something of value from the experience. Extract the wisdom that may have been unintentionally veiled.
  4. Be reasonable about the edit. Don't get upset over a minor inconvenience.
  5. Move on from it!

If you seriously believe that you did correctly follow it, discuss with the editor on the articles talk page. If they do not reply, leave them a message on their userpage. Remember, even if you disagree with the MOS, it's often easier to stand on the shoulders of giants then reinvent the wheel.

Punishment

Only in extremely rare cases do we ever punish somebody for not following the MOS. This would only occur if somebody is intentionally ignoring it for the sake of making a statement. Similarly, following it too closely and instead of following the spirit of the guidelines for the sake of making a statement. Generally, do not seek to punishment for a user - often the situation is because of a misunderstanding.

Conclusion

Follow the spirit of the guidelines, but do not become too caught up in enforcing policy that you forego style and readability. Be nice to new editors and most importantly: keep pages consistent!

See also