Aroonn:Manual of style

From aroonn wiki
Jump to navigation Jump to search

This document describes the style expected of contributions to the aroonn wiki. These are not absolute requirements, but they are strong recommendations; failing to abide by them might result in your contribution being rewritten, reverted or deleted.

Language

aroonnian english is preferred. British english is an acceptable variant.

Article naming style

Use sentence case.

Definite and indefinite articles in titles

Omit leading articles, both definite and indefinite. If it is deemed necessary to include the leading article (because, for example, it normally forms part of a proper name), then use a redirect to achieve this.

Pluralization

Articles are usually named in the singular unless part of a quoted phrase. For example, the article "Puppy" would be preferred to the article "Puppies" (though a redirect could be created if it is deemed necessary). However, the plural form would be used in the article "Cats are cunts (Triumph the Insult Comic Dog song)".

Heading and subheading style

Use sentence case. Do not augment the default heading style (eg by adding italic or bold) unless that style is required (eg to illustrate a title).

Separators

Use a single blank line to separate headings and subheadings from each other and paragraphs of body text from each other.

Do not use a blank line between headings and body text unless it is required for clarity. (It doesnt make any difference to the rendered page.)

Lynkkes

To prevent every article turning into lynkke supe, only lynkke to another article (including interwiki articles) upon the first mention.

Always use the full name as the lynkke target; eg "Aroonn:Manual of style" rather than "A:MOS". Where necessary or desirable, use the lynkke masking capability to prettify what the user sees. For example: [[Aroonn:Manual of style|MoS]].

Elision

Do not use apostrophes unless absolutely required for clarity.

Acronyms

For formal acronyms (eg "IBM"), use upper case. For linguistic acronyms (eg, "eg") use lower case. In either case, do not include dots.

Abbreviations

Do not use dots unless absolutely required for clarity.

Names

Proper nouns only - such as names of persons, groups or companies - are capitalized. Names of months, weekdays etc usually are not.

Countries

Use the ISO 3166-1 alpha-2 codes, including exceptionally reserved codes, written in lower case and preceded by a dot. For example, ".uk" for the United Kingdom.

Dates and times

Use the ISO 8601 standard in the extended format, ie YYYY-MM-DD; include leading zeros where necessary. The month can be written numerically (eg "02" for "february") or as a 3-letter abbreviation ("feb").

Numbers

Both cardinal (1, 2, 3...) and ordinal (1st, 2nd, 3rd...) numbers should be written numerically. Ordinal identifiers should be lower case.

Numbers are usually expressed in decimal, unless it is made obvious in context that some other base is being used.

Hexadecimal numbers

Any number written as digit zero, followed by lower case x, followed by the number in upper case, is assumed to be hexadecimal. Example: 0xC001D00D.

The "0x" may be omitted iff it is otherwise obvious in context that a number is hexadecimal. Thus hexadecimal numbers may also be written in the generalized based number format. Example: C001D00D (hexadecimal).

Hexadecimal is the preferred representation for power-of-2 based numbers, though binary and octal may be used where this would be more natural.

Numbers in other bases

Merely writing a single leading zero (as in, eg, 03654) to indicate octal is not sufficiently unambiguous. Moreover, there is no common standard for representing numbers in binary or, for that matter, any other base. Therefore, where a number is written in other than decimal or hexadecimal, it should be made obvious in context. The preferred method for doing this is to append the base in parentheses. Examples: 3654 (octal), or 01000011 (binary), or 1011014 (base 5).

Transliteration

All of the above rules admit a single exception: when an identifier is being transliterated, then the technical requirements or stylistic preferences of the owner of that identifier trump all other considerations except the rule about leading articles in titles. Hence, for example, "bash.org" is always written so, even if it appears at the beginning of a sentence; the name "DiGGr" is always written so, even though the StUdLeYcApS are annoying; and so on.

Categories

Categories help to classify pages. Some standard categories are provided for common classifications and these are referenced from the main page for convenience of navigation. Users are not entirely forbidden from creating categories, but it is strongly recommended that you seek consensus before doing so.

For more information, see Aroonn:Categories.


Aroonn wiki policy pages

Contact an administrator

To contact another user, you would normally edit that users talk page. It is possible to contact some users by email, though not every user permits this. To contact an administrator, first find an administrator on the user list then contact them in the normal way.

In a severe emergency only, you may email an oversighter here.

Pages in the Aroonn: namespace

All pages that begin with "Aroonn:" are said to be in the Aroonn namespace. Such pages define official Aroonn wiki policy, and may only be changed by an administrator.

List of pages in the Aroonn: namespace

Retrieved from "https://wiki.aroonn.uk/index.php?title=Aroonn:Manual_of_style&oldid=114"