Help:Style

From Starsider Wiki

Jump to: navigation, search

In order to achieve some amount of uniformity in style between articles despite variance in contributors, all users are encouraged to take the following guidelines on Style into account.

Contents

Article names/titles

  • All article names should be in singular form, not plural (ie. "Stormtrooper" rather than "Stormtroopers").
  • Only the first word of an article name should be capitalised, unless a proper noun.
  • Articles about Characters should be the name by which the character is most commonly known, with full names preferred to partial names or nicknames. Titles, such as military ranks or titles of nobility should be used only in the article itself, or in the template sidebar if essential, particularly as an identifier, but never in the page's title. It's highly recommended that authors detail the significance of any rank and/or give details of why a player character would be referred to as such, to inform readers for roleplaying purposes (eg. "Captain Smith was still known as such despite retiring soon after the last years of the Clone Wars. Since he'd been referred to as such throughout the conflict, and it stuck once he'd left the battlefields that had earned him the title").

Image:Titleexample.jpg

  • If possible, make the article's topic the subject of the first sentence of the article (as opposed to putting it in the predicate or in a subsequent sentence). For example, write "This Manual of Style is a style guide" instead of "This style guide is known as....".
  • If the article title is an important term, use it as early as possible in the article.

Article perspective

All information in any article can be divided into two types, to which different writing styles may apply. Any given main section within an article should clearly be either In-Character or Out-of-Character, never a mix of the two:

In-character

"IC" information is written from the perspective of a neutral observer in the RP universe, about actual RP events. It does not mean this information may actually be used ICly during roleplaying. Rather, the information should be written as if from a historical perspective. In other words, if you are adding IC information to an article, imagine that you are a historian in the Star Wars universe writing at a hypothetical point some years (even centuries) after the events you are describing.

Thus your aim, as a good historian, should be to chronicle these people, places, and events with as little bias and as much factual accuracy as possible - although a degree of historical interpretation is also permissable. Authors are encouraged to be mindful of the overarching narrative that has been taking place within Star Wars Galaxies so that they might contribute to the larger story taking place, and tell an audience about their specific parts of the larger whole.

Character biographies, descriptions of the outcome of events, backgrounds of ships, and histories of factions are examples of information that would be considered In-Character.

Out-of-character

"OOC" information is written from the player's perspective, and covers "behind the scenes" topics which deal with the background to, or process of, roleplaying. For instance, all articles in the Concepts category are written from a purely OOC perspective. However, other articles may contain OOC sections in addition to IC information - examples include the RP rules of guilds or cities, meta-data about characters that other players should know if they RP with them, and any other out-of-game notes/guidelines that may need to be made in an article. OOC information can thus be written in the past, present, or even future tense.

As with In-Character information, however, anything from an OOC perspective should be written in a neutral tone, as if you were the author of a RPG sourcebook or a game manual. If possible, it's also recommended that "behind the scenes" details be appended to the end of an article to preserve an initial "narrative" flavour.

Sections

Headings

Use the == (heading) markup for headings, not the ''' (bold) markup. Example:

===This is a heading===

which produces:

This is a heading

If you mark headings this way, a table of contents is automatically generated from the headings in an article. Sections can be automatically numbered for users with that preference set and words within properly marked headings are given greater weight in searches. Headings also help readers by breaking up the text and outlining the article.

  • Capitalize the first letter only of the first word and of any proper nouns in a heading, and leave all of the other letters in lower case.
  • Avoid links within headings.
  • Avoid overuse of sub-headings.
  • Keep the heading short: headings more than ten words long may defeat their purpose.
  • Avoid redundancy and unnecessary words in headings, such as articles (a, an, and the), pronouns, and repetition of the article title.
  • Do not give identical titles to different sections. Doing so tends to confuse the reader, and makes it more difficult for any writer to create a section link to any such section except the first.

Structuring

  • For an article of any length (ie. more than a couple of paragraphs), using headings to divide the text into Sections is crucial.
  • Sub-headings help readers get an overview of the article and find subtopics of interest. Create sub-headings if a section becomes too long, and choose appropriate sub-headings to aid in your exposition.
  • Ensure that each section, or sub-section, of the article has a noticeably different theme and point in the information which it contains. For instance, the "Biography" section of a Character article should contain information only about their lives, and it is recommended to be broken down into further sub-sections each covering different main periods in the character's life (ie. "Birth and Childhood", "Adolescence", "Adulthood", etc.).

Miscellany

Canon/Fanon

If a section or sub-section is focused upon providing standardised Universe information about a particular topic (ie. the history of the YT-1300 production model), it is useful to note whether the information you are providing is Canon or Fanon. Place the appropriate template tags at the beginning and end of the section - {{Canon}} and {{Endcanon}}, or {{Fanon}} and {{Endfanon}}

Quotes

Quotations should follow this general format:

  • If the quote is less than a paragraph long, simply including it in the article's body with "quotation marks" will suffice.
  • If the quote is at least a paragraph in length, or a piece of dialogue, insert as a block quote using the quote template.
  • Quotes that serve as introductions to article subsections should not contain internal links because they appear unprofessional and are generally distracting.
  • Redundant internal links should not be added to quotes because they serve little purpose beyond making the quotes appear cluttered and messy. Links should only be added to quotes if they contain a specific article's ONLY mention of a particular concept, but even then, it is better to integrate the internal link into the body of the article's text.

Units of measurement

For consistency, all articles should use metric units of weight, mass, length, and other measurements. This follows the practice in most sources of official Star Wars canon.

Ship names and classes

Names of specific spaceships should be:

  • Capitalized
  • Italicized
  • Used with the definite article
e.g.
"The Thunderflare operated in the Core region."
NOT "Thunderflare operated in the Core region."
  • Referred to by neutral pronouns (it, its)
e.g.
"Chimaera was a fine ship. Its commanding officer was Captain Pellaeon."

Class names are italicized only when a spaceship in the class bears the same name. The definite article may be used, but it is not required.

  • When a ship’s class is a modifier, use a hyphen:
"Quasar Fire-class Bulk Cruiser"
  • When it is a noun, do not use a hyphen:
"Ships of the Victory class were often overlooked"
e.g.
An Executor-class Star dreadnaught

Images

  • All images in the main body of an article's text should be placed within a frame.
  • Images should be scaled, if necessary, to be no greater than 350 pixels in width.
  • A short caption should be included to explain the nature of the image, and any relevance to the corresponding article text.
  • It's recommended that, wherever possible, images be sourced from Star Wars Galaxies itself, preferrably cropped from personal screenshots.

Stories

Articles are meant to be encyclopedic in nature and style, not a place to copy fiction/stories to, no matter how relevant. If you wish to include text from a story in an article, please do so as a Quote, no more than two paragraphs in length, or provide a link to it elsewhere. We encourage any stories to be posted in the Stories category in the StarsiderGalaxy.com forum.

Sources and Inspiration

  • While the Star Wars universe has generated volumes of material for authors to derive material and research, it is highly recommended that material added to the Starsider wiki be their own work. Material that from similar resources such as Wookieepedia will need to be rewritten as a new article. Anything work copied directly from these sources contravenes the principles of the Starsider wiki and disrespects the time, skill and labour of the original author. Material copied will be subject to extensive editing and possible deletion. Authors are recommended to take the time to write the material in their own words.
  • Sources can be referenced at the end of an article though, if posible, links are recommended in order to preserve a flow to the historical perspective.
Personal tools