The Dark Cloud Wiki's guideline is used to document good practice, as established through community consensus.
What is consensus?Edit
Consensus occurs when editors reach a general agreement through discussion upon which decisive action is taken. Consensus is not achieved via popular vote, but instead by the cogency of the presented arguments and its following actions taken through a process of concession and good faith.
After consensus is reached, it should then be documented, consulted, and enforced as necessary. Thorough but concise accounts of important decisions should be documented on this page or a relevant help page for accessibility purposes, though the conversation that led to the consensus should remain in tact if possible.
Checklist for inclusionEdit
As the Dark Cloud Wiki is, by nature of being a wiki, the subject of contribution by any given individual, the community uses a checklist of rules to determine what is kept or removed, or denied of being added to begin with.
- Articles — An article's subject has to be notable, unique or specific to the Dark Cloud universe, in order to ensure it is of practical and encyclopedic value to the reader.
- Information —
- All content must be cross-verifiable. Contentious claims should be supported by footnotes to reliable sources in order to insure the integrity and reliability of the website.
- Place footnotes within reasonable proximity of the relevant information, after all punctuation.
- Footnotes should reference game scripts, data pages, official websites, page numbers (for strategy guides or other books), or time markers for videos. Any references requiring greater generality are usually unnecessary.
- Categories, files, and templates — Put simply, these must have unique and practical value. Ensure they are not duplicates and will be used appropriately.
In order to establish cohesion across the project, the Dark Cloud Wiki uses the following style manual as a general guideline. However, for English practice, proper formatting, and editing style, see Wikipedia's Manual of Style. For help with introductory wiki formatting, see Help:Contributing.
- Capitalization — As in-game capitalization is often inconsistent and unjustified, use proper English capitalization instead: Only proper nouns are capitalized while common nouns are not.
- Puncutation — Logical punctuation is preferred over standard punctuation. See MOS:LQ for more details.
- Page names and section headers — Page names and section headers should use sentence case instead of title case.
- Naming convention —
- Articles should be named according to their in-game name; or a guide; or website's given name; or its concept art's title; or a name with one or more descriptors—in that order.
- For in-game names, articles should be named after their subject's most common name, with prefixes omitted, and surnames included.
- For characters with multiple names, their latest self-identity should be used.
- Main image — An article's main image should be of its subject's latest appearance, except when it is significantly more represented in previous events.
- Writing style — Concision determines how information is conveyed, encyclopedic value determines which information is conveyed. Aim to be as comprehensive as possible while using no more words than necessary.
- Scripts —
- Subtitle vocabulary, capitalization, punctuation, and emphasis should be replaced per actual diction and proper English rules. Replace all-caps emphasis with italic emphasis.
- In-game lines (e.g. communicator lines or tips from other characters) should have their own sections, suffixed with (in-game).
- Commentary regarding the actions of the cutscenes should be omitted, though contingent lines should be indicated with parenthetical text.
- Although ideal, it is not compulsory that all contingent lines be included for a "complete" script, as there are often many of them and their triggers are easily missed.
- Script page section headers should be named after either their cutscene names (found in scene players), or their respective mission names (found in mission lists, level select, or in-game prompts).
- However, for accessibility purposes and consistency's sake, every script page should have a "Prologue" and "Epilogue" section regardless of their scene name.
- Article structure — Use the most appropriate article structure as determined by general consensus. Use existing articles, especially popular ones, as examples. In general, an article should always contain a lead (also called an intro), and a body.
- The lead should be a concise but comprehensive overview of the subject, omitting no uniquely identifying factors but not going into too much detail. Note that some or all sections will be merged into the lead depending on the length of the article and the necessity of split sections, in which case it is longer known as the lead but part of the body.
To preserve a constructive, collaborative environment, all users are expected to adhere to a set of conduct guidelines:
- Especially in the midst of conflict, remain civil, avoid edit warring, and most importantly, assume good faith. Remember that editing articles is not about winning, and avoid taking things too seriously.
- The burden of proof is on the person wishing to add the material in question. This includes proving whether or not the content is notable, attributable to a reliable source, neutral in point of view, or adherent to other relevant guidelines.
- Reserve the use of article talk pages for discussing changes or questions to the article itself, not its subject. Use the forums for wiki-related discussion or questions. Use user talk pages, blog posts, or chat sessions for off topic, open ended comments or personal questions.
Policies involving administrative or otherwise technical operations of the site are documented in the "Help" namespace. The most important are listed below, but all can be found at Category:Help pages.
- Deletion rationales
- Image use and upload guideline
- Preservational reversion, protection, and blocking policies