This page contains the Starfield Wiki's article guidelines. It describes criteria and general rules for all the content on the wiki.
- Any registered editor is free to edit this page to improve its readability as long as the essence of the article remains unchanged.
- If you would like to suggest content changes or propose a new policy or guideline, please leave your suggestion on the talkpage.
Editing
You are free to edit pages on the wiki but understand that others can also edit your work. Please do not abuse this right by starting an 'edit war', simply discuss any problems on the discussion page or report abuse to an admin.
Content criteria
- All content should relate to Starfield series of games, its setting or game mechanics.
- All content needs to be accurate. Starfield Wiki aims to provide reliable information. In particular, adding speculation and own inventions (fan fiction, fan art etc.) to articles should be avoided. However, feel free to write to include this content in your user pages or blogs
- All content needs to be verifiable. Other editors need to be able to check and verify it.
- All content needs to be informative. Information which is only of interest to the writer or to other editors (as opposed to readers) should not be included in articles.
- All content needs to be objective. Opinions, game-play strategy, and "my favorite"-style passages should not be added to articles. Accordingly, guides may only be posted as sub-pages of one's user page or as a blog.
- All content needs to relate to the games as delivered by the developers; user modifications are not covered by this wiki.
- Mentions of modifications which may fix game bugs are the exception and links to these can be provided.
- All content needs to abide by copyright regulations. Generally, content from other sites should not be copied unless permission has been granted. For example, do not upload magazine scans or add illegally obtained information, so as to avoid potential legal problems.
Video
Wikis are predominantly text-based with supplemental images. Video may be added to articles, however it must meeting the following criteria:
- Cover a subject that is difficult to demonstrate in text
- Take a direct route
- Only show content relevant to the subject
- Only includes sound and content from Starfield and other official sources
Spoiler policy
In general, the whole wiki is considered a spoiler and specific spoilers should not be marked as such in articles. The only exception to this rule is information relating to upcoming games or add-ons, i.e. games or add-ons which have not been released yet but are to be released in the future.
Gender and Sexuality
Starfield contains themes around gender and sexuality, which must be handled respectfully. When discussing characters within the media and individuals associated with the media the following must be applied to content:
- Sexuality should not be assumed: unless someone has stated their sexuality this should not be recorded within the article content. where it has been stated, it must be referenced in the content.
- Gender should not be assumed: unless someone has stated their gender, it should not be stated.
- Where the gender is known, gender should be referenced. Visual evidence does not meet the burden of proof for gender, neither do pronouns.
- Statements such as "that man" or "I am a woman" are acceptable, unless this is evidence the statement is misgendering.
- Where the gender is known, gender should be referenced. Visual evidence does not meet the burden of proof for gender, neither do pronouns.
- They/them pronouns should be used in content by default unless alternative pronouns have been provided and can verifiably referenced.
- Pronouns used by an character to refer to another character can be used for affirmation of an individual pronouns, unless it conflicts with the character's preference. The use of pronouns in reference to another character is treated as developer intention to let us know the character's pronouns.
- When discussing real life individuals, only the pronouns the individual has stated be used should be used; usage by other's should not be used.
- When discussing an individual's relationship to others, gender neutral relationship terms (e.g. child, sibling, partner) should be used where gender has not been determined.
- Pronouns used by an character to refer to another character can be used for affirmation of an individual pronouns, unless it conflicts with the character's preference. The use of pronouns in reference to another character is treated as developer intention to let us know the character's pronouns.
- In cases where an individual may have transitioned, unless there is direct confirmation of a transition (e.g. I/they were, I/they became) a declaration of transition should not be made.
- Anecodotal/visual evidence falls below the threshold of proof required to state an individual has transitioned.
Note: Due to the sensitivity of these subjects, an exception to our Blocking Policy will be made for these guidelines . Where good faith can be seen in the contribution (i.e. an attempt has been made to follow policy) or a first time break of these guidelines is made, guidance will be given and the contribution corrected. Bad faith contributions or repeated attempts to break policy will result in an immediate indefinite block.
Trivia and Behind the Scenes
As with any form of media, there are many seemingly obvious cultural references or facts about a subject. Common comparisons such as planets sharing names with Greek gods will be removed as filler content that in some cases could have multiple origins. Anything that has been outright stated by an individual involved with the Starfield series of games may be added as long as it can be publicly referenced and does not require more than a web browser for online content or a copy of the book/journal for physical media to access. Any such commentary should be added as a reference in the background etc where possible. If this is not possible a Developer Commentary section can be added to the page.
Plagiarism policy
A wiki doesn't just live and die on the information it contains; it also survives on the reputation it builds as an information source.
Plagiarism hurts the wiki's reputation and reduces our ability to be seen as an authoritative information source - it also could be a breach of copyright.
It could also put the wiki at risk - unauthorized copyrighted content could see parts of, or even the whole wiki made unavailable.
What is, and what is not, plagiarism?
"The practice of taking someone else’s work or ideas and passing them off as one’s own" ― http://www.oxforddictionaries.com/definition/english/plagiarism
As a trusted source of information, we want as much of our pages as possible to be made up of original content that cannot be found anywhere else. To this end, we would prefer editors, whenever possible, to create original works that do not directly copy anyone else's work.
This is not to say content cannot be inspired by it - maybe you saw something somewhere else that you thought might improve a page. By all means, feel free to bring that to the wiki - but make sure its your own work and written in your own words - and if you can improve and develop the idea further.
Sometimes you may have to use other peoples words and work, here are some situations where this is acceptable (this isn't inclusive):
- Licensed Content. If you have prior permission from the content owner, you can reuse their content - We've asked permission to present to you many of our sound files for example. You should still cite who the owner of the work is though.
- Copyleft/Creative Commons/Public Domain - this is a specific form of licensed content, the owner of the work has made it available for anyone to use without prior permission, but in the case of the first two this is subject to some rules. You should ensure that you follow any requirements set by the content owner (such as following the license conditions, or attributing in the way that they request); if no attribution standard is given by the owner, then you should ensure that they are identified and if at all possible the original linked in the references (for non-displayed content, the comments may also be acceptable).
- Quotes - Its perfectly permissible to quote a person, or even a copyrighted work. Your quote should be limited to the amount you need to make your point - for example, you can't quote an entire magazine article, but a paragraph or two may be acceptable. You should use the Quote template, and link to the source of the quote wherever possible, giving credit to the author/speaker/publication.
- Fair Use - There are also times where it is possible to reuse content within the US's "Fair Use" exemption. Much of the source files and screenshots fall into this category, as does images used in news reporting. The origin should be credited and linked wherever possible.
General Grammar Rules
Article Titles and Subtitles
When creating articles, they should be in upper case with the exception of conjunctions (e.g. of, the, in). In most cases a lower case redirect should also be made for use in articles to simplify editing.
Article Content
Although item names are always capitalized in-game, the wiki follows general writing rules. In article content, carrot should only be Carrot if it's a trademark, proper noun, or the start of a sentence. Taxnomical (or scientific) nomenclature always capitalizes only the first name, and is always written in italics.
Guidelines:
type | rule | examples |
---|---|---|
location name | capitalize (proper noun) | |
quest name | capitalize (title) | |
item name (unique) | capitalize (proper noun) | |
item name (generic) | lowercase (except trademarks within the name) |
coke Coca Cola |
taxonomical naming | capitalize the first name, lowercase for the rest. Always in italics. |
Salmonidae salinis Beta lupus familiari |
nautical vehicles | Name should be capitalized in all cases Always in italics in line with nautical industry standards. |
Mary Celeste |
vehicles, excluding nautical craft | Name should be capitalized in all cases Never italicised as there is no official standards. |
|
media (real and fictional) | Media titles should be italicized and use proper noun capitalisation. Use of "and" and ampersand ("&") can be used interchangeably, but should be consistent on the article; article title should use the game's preference. | Pride and Prejudice Pride & Prejudice Attack on Titan |
Written Numbers
Written numbers should be used in writing where the number is between zero and one hundred. Numbers exceeding one hundred should be in numeric form.[1] The only exceptions to this are financial values, which should always be in numeric form.
References
Not all information is "obvious" as to where the wiki has obtained it, maybe it was in an obscure piece of dialogue that could be acquired under specific circumstances or in an overlooked, highly protected terminal. Content such as this should be referenced on the article. For the purpose of this policy, reference components in italics are only required, where relevant.
References should come after the punctuation, to avoid the punctuation markings themselves becoming detached sentence (or fragment). If source material is on the wiki (e.g. terminal entries), it should be linked in the reference.
Dialogue references
All dialogue references should be in the following format:
Character, topic, event, location.
- Examples
Terminals, books and datapads (written sources)
Written sources should referenced in the following format:
Source name, subsection, (sub)location (location).
- Examples
External sources
External sources can be both digital or physical and when used the source, article/chapter/etc. title and date accessed should be given. Where there is an author and/or date on the source itself this should also be used:
Author, Source name, date, article/chapter title (link if online), date accessed (if online).
Where the media is digital, the Source name should be linked to the original source.
Game data
Font styles
- Only the first mention of the articles subject should be in bold, all further instances would be plain text.
- Quotes should be in italics
- Any other use of font styling should be minimal.
Organisation
Anyone can add a page or image, which can ultimately lead to confusion if no order is followed. Please name things to a standard.
Files
Filenames should be descriptive to the content:
- Starfield cover art.jpg
- Raiders faction logo.jpg
Titles such as 123.jpg are unhelpful in content searches as Special:Search does not show the image itself.
Be mindful to keep filenames as short as possible. "Ellie doing a dance around a fire on the bodies of her captives wielding a shotgun and a six pack of beer.jpg" is descriptive, but unwieldy; reducing it to "Ellie campfire dance.jpg" would be a more suitable title.
Titles
Overall, article titles should be in the singular, rather than the plural. The only exception to this is overview articles, which cover multiple subjects in a topic (e.g. Weapons).
Article titles should also follow Capitalization policy.
Redirects
Redirects should only be created in the following situations:
- Where a user is likely to search with words included or omitted .
- Where a subject is bundled into another article only, for example Botantical lab key may be bundled into an article for Keys.
- Common misspellings - these would be done by the administrators based on the wiki search data or commonly recreated misspelled articles.
- Ease of maintenance - where the text to a page link often will not match the article title (e.g using first name only, pluralism which differs from the singular) a redirect may be beneficial to editors and readers.
- Plurals that do not change the spelling of the singular (e.g. carrots) should not be created.
- The inverse (plural to singular) can be created, however they should only be created only if the singular is frequently used in articles.
Categorization
All images and all pages must be added to a Category by adding this code to the bottom of the page or in the image summary:
- [[Category:Name of category here]]
In general, where there is a relevant, more specific category, this should be used in place of the general category. A companion would have the Companions category and forgo the Characters category. Weapons would be categorized by their sub-type (e.g. Handguns) as opposed to the general Weapons category.
In the case of a topic fitting into more than one category, multiple categories can be used, listed in alphabetical order.
Category creation
Creating new categories should only be done in the following conditions:
- Where there is no category that the article would suitably fit into.
- Where multiple articles could be better linked together.
- They should not be of 'special interest', unless justified through community consensus.
New categories should be descriptive and useful to readers. Weapons with Glowly blue bits Is descriptive, but not very useful; readers looking for this information are likely to be in the minority, padding articles needlessly and making it a special interest category.
'Special interest' categories
Special interest categories can be considered, but only with a majority consensus from the community. They are often too niche, or too broad to be of benefit from a maintenance or search perspective. Categorization by gender for example is very broad, although some may be interested in the character ratios, or want to play through by only interacting with one gender, this removes the overview of characters, or in the case of being categorized by employer, may make some sub categories exceptionally small. Some special interest categories may be of use based on game design; however, there are better ways to extrapolate this such as through DPL.
Article Format
The layout of articles is agreed by the community and articles must follow the general agreed format. Although this format is largely fixed and any significant changes should be made with community consensus, there are instances where being bold and making ad-hoc inclusions is encouraged as long as the agreed format is retained.
The below sections show the order, requirements in a section, if that section is required and any additional information. Any sections that are not required should be included when there is information that can be added, but if there is no information should be omitted.
Planets and Moons
Required | Order | Section/Template | Additional information |
---|---|---|---|
Yes | 1 | {{Infobox Celestial Body}} | |
Yes | 1a | Lede | A short summary of the article subject, typically starting with the article subject in bold what it is and any flavour text |
Yes | 2 | Overview | A written summarisation of the infobox details and any lore about the planet. Any information related to the planet that does not fall within another section can be placed here. |
Yes | 3 | Resources | A short list of the available resources on a planet. This should begin with the minable resources as on sentence then a follow up sentence of resources that can be obtained from flora and fauna. |
No | 4 | Fauna | A written summary of the fauna available. |
No | 4a | {{Fauna Table}} | Summary breakdown of the fauna on the planet. |
No | 5 | Flora | A written summary of the flora available. |
No | 5a | {{Flora Table}} | Summary breakdown of the flora on the planet. |
No | 6 | Developer Commentary | Any developer confirmed behind the scenes commentary. This must be referenced. |
No | 7 | Gallery | An image gallery |
No | 8 | References | Section containing the <references /> tag. Only required if there are references on the article. |