Help:Policies

From HACKED BY DEL.ICIO.US!
Jump to: navigation, search

This page is a guide to C:S Wiki's policies. If you don't find your answer here, try asking in our Discord server.

Guiding principles

These are the basic principles that inspire our work and policy.
Goals and non-goals
Nutshell: Our goal is to document publicly available Cities: Skylines content, varying from 'Let's play'-series to mods for the game.
See also: What to add
Consensus
Nutshell: Almost all decisions are made by achieving consensus rather than voting, so when discussing a change, state your arguments and build a consensus.
Plunge forward
Nutshell: Don't worry about making mistakes or making the perfect edit. If something needs to be done, then do it. Jump in and make useful edits to articles.
See also: Plunge forward

Content policies

Be clear
Nutshell: Avoid vague usage of language. Be plain, direct, unambiguous and specific. Avoid generalities.
Be concise
Nutshell: Omit needless words. Direct, concise writing may be more clear than rambling examples. Footnotes and links to other pages may be used for further clarification.
Spirit of the rule
Nutshell: Expect editors to use common sense. If the spirit of the rule is clear, say no more.
Maintain scope and avoid redundancy
Nutshell: Clearly identify the purpose and scope early in the page, as many readers will just look at the beginning. Content should be within the scope of its policy. When the scope of one advice page overlaps with the scope of another, minimize redundancy. When one policy refers to another policy, it should do so briefly, clearly and explicitly.
Avoid overlinking
Nutshell: Links to policies, guidelines, essays, and articles should be used only when clarification or context is needed. Links to other advice pages may inadvertently or intentionally defer authority to them. Make it clear when links defer, and when they do not.
Do not contradict
Nutshell: The community's view cannot simultaneously be "A" and "not A". When apparent differences arise between pages, editors at all the affected pages should discuss how they can most accurately represent the community's current position, and correct all of the pages to reflect the community's view. This discussion should be on one talk page, with invitations to that page at the talk pages of the various affected pages; otherwise the corrections may still contradict each other.

Community policies

Unwanted edits

Keep it fun
Nutshell: Writing about anything on this wiki should be fun. Behaviour that makes others enjoy editing less should be avoided. If your are subjected to such behaviour assume their good intentions, but discuss the issue, preferably with staff, if the problem persists.
Handle unwanted edits
Nutshell: Unwanted edits are contributions that are not in line with our policies and guidelines or Manual of Style. Any editor may revert such edits.
Edit wars
Nutshell: Do not wage an edit war. If you get involved in one, then step back and use the article's talk page to reach a consensus.

Links

External links and images
Nutshell: Keep external links to a minimum and if used, link to primary sources. There shouldn't be a dedicated section to external links.
Internal links
Nutshell: Make links to other pages on the wiki, but generally only link the first instance of an article name. These should be incorporated into the text of an article if practical, otherwise use a "See also" section at the end of the page.

Specific community policies

Deletion policy
Nutshell: Articles and images can be deleted if certain criteria are met. If you feel an article or image should be deleted, tag it for deletion using {{VfD}} and subsequently start a vote for deletion. Some items, such as spam, copyright violations or unintended mistakes created while moving pages or creating a redirect, can be 'speedy deleted' using {{Speedy}}.
Protected page policy
Nutshell: Administrators may protect a page when necessary, but it is preferable that abusive edits are effectively counteracted without protecting a page.
Image policy
Nutshell: Images must be compatible with our copyleft licence. The image page must contain a summary with the appropriate attribution information and licence information. Photos generally should not contain people unless it is a public space and the people are peripheral to the picture content.
Sock puppets
Nutshell: The creation of sockpuppets, i.e., multiple accounts per user, is discouraged, but they are usually just ignored.
No real world threats
Nutshell: Real world threats—essentially threats of physical or legal harm—are strictly prohibited on C:S Wiki. They are never necessary, and can have a chilling effect on public participation. If you do post a threat of a lawsuit or physical harm, even an ambiguous or vague one, you will likely be banned from further editing here with prejudice.
It's not carved in stone
Nutshell: Most of our detail policies and guidelines, and the manual of style can be changed if there is a need and the community can come to a consensus on the change. Any proposed change must be compatible with our guiding principles.
Jargon
Nutshell: Make your articles readable for everyone and anyone. Do not use professional language to make the article seem more legitimate.

Roles within the community

Hierarchy
Nutshell: C:S Wiki has a hierarchy of people involved in the community, with varying levels of responsibility in the project. People burdened with more responsibility are expected to serve those above them, and make life easier for them.
Administrators / Sys-ops
Nutshell: Administrators are registered users who have shown a good appreciation of the policies and guidelines and made significant contributions, have been nominated by the community and have been granted some additional functions. They are the plumbers and janitors of the wiki and perform mostly mundane tasks, but also those few tasks which could do permanent damage if done wrongly.
Autoconfirmed users
Nutshell: Users who have been registered for longer than 4 days are autoconfirmed. In addition to this allowing them to mark anonymous users' edits as reviewed, it also means that their own edits are marked as reviewed automatically.

Infrastructure and software

Avoid HTML
Nutshell: HTML should be avoided in marking up articles. Use Wikimarkup for formatting when possible. If Wikimarkup is not possible, and the formatting will be generally useful, consider a MediaWiki template.
Wiki markup
Nutshell: MediaWiki software uses a special code called Wiki markup for formatting the text and images in an article. The Wiki markup used while editing a page will determine how the text looks and what links and images are in the page.

Recognising contributors and articles

Be apreciative
Nutshell: Feel free to thank users for their edits using their user talk page.
Featured articles
Nutshell: Feel free to nominate an article to be featured at our main page using our Discord server.

Organisation of the wiki

Creating articles

What is an article?
Nutshell: An article or entry is a page on this site that has encyclopedic information on it.
See also: What is an article?
Disambiguation pages
Nutshell: A disambiguation page lists the full titles of several different articles with similar names, and allows the reader to choose between them.
Naming conventions
Nutshell: Articles should follow the most-used and most representative name.

Content policies

Avoid negativity
Nutshell: Encyclopedia's are there to document something and not to give a stance on something. Leave out your opinions, regardless if they're positive or negative thoughts.

Manual of Style

Manual of Style
Nutshell: Our Manual of style is a collection of rules of thumb and guidelines for giving C:S Wiki articles a consistent look and feel. Most of these rules have exceptions, but to put together a good reference work collaboratively, it's best to follow the rules unless they're quite inappropriate for a particular situation.

Structure

Article templates
Nutshell: Articles are generally structured using standardized section headings and order, and we have handy substitution templates to help with this.
Avoid long lists
Nutshell: Long lists and large groups of items can be difficult to grasp. If there are more than 9 items to group, consider subdividing into groups of 7±2 items.
Infoboxes
Nutshell: An information box tells the reader something interesting about the destination or an attraction that is not included in the listing. They are good for providing supplemental information but should not be overused in an article.
Maps
Nutshell: A picture may be worth a thousand words. A clear and simple (interactive) map can often be more useful than a written description.
Section headings
Nutshell: Wherever possible, section headers should be identical to the ones in the article templates. The more consistent the sections of articles in C:S Wiki are, the easier it is for readers to find what they're looking for.

Writing style

Abbreviations
Nutshell: Using abbreviations for commonly known terms is encouraged. The abbreviations used should be uniform.
Creating emphasis (Italics, Bold, Underlining)
Nutshell: Use boldface to call important topics and use italics for emphasis, but don't overdo it.
No Captain Obvious
Nutshell: If something is very obvious or true for nearly all articles, it does not need to be written down.

Language

Foreign words
Nutshell: It's often useful to point out the local-language name for a place or thing in an article. List the foreign-language word in parentheses after the English name.
Romanization
Nutshell: Non-Latin alphabet names should be written in the latin alphabet for English to assist readers in pronounciation.
Spelling
Nutshell: Destination guides should be written in the local variant of English.

Numbers and dates

Currency
Nutshell: The cost of an item should be listed in the local currency unless the local convention is to list the price in a foreign currency. Prices should be listed with the currency symbol or abbreviation that readers will encounter: € and EUR, $ and USD.
Measurements
Nutshell: Metric or imperial units of measurement should be displayed depending on the predominant local usage. It is good practice to provide both metric and imperial conversions (local units first with conversion in parentheses).
Time and date formats
Nutshell: Times should be displayed in the local timezone using the 12 or 24 hour format, whichever is the predominant local usage. Days of the week should be abbreviated to the minimum number of letters. Dates should use the format dd mmm yyyy.

Legal information

Disclaimer
Nutshell: You're responsible for yourself, we are not.
Owning edits
Nutshell: The contributions that any user makes on this wiki is automatically published into the public under CC BY-SA 3.0. No individual user 'owns' an article, even if they may claim so.
Terms of use
Nutshell: The whole content of C:S Wiki is available for everybody, provided that our Copyleft license is followed.