Halopedia:Manual of Style

For more general information, see the Wikipedia Manual of Style.

This Manual of Style for Halopedia is a guide for editors on how to properly format Halopedia articles.

General

 * 1) Please categorize articles and insert navigational templates appropriately to ensure that Halopedia is a more orderly compendium of Halo knowledge.
 * 2) Please do not insert a heading, such as == Summary ==, if there is only a single heading within the article. Just don't put a heading until you feel the need to insert two, and then you may create two.
 * 3) Whenever inserting pictures in "thumb" format, such as [[Image:Random.jpg|thumb|left]], be sure to add a caption like [[Image:Random.jpg|thumb|left|Caption goes here.]].
 * 4) Refer to the Halo universe from a third-person perspective.
 * 5) List all references at the end articles. It should not be:  Instead, use the reference tag if necessary, or else, write:
 * 6) Refrain from using slashes whenever possible. Instead, work the word "or" into the sentence, or figure out some other way of stating it.

Use the Minor Edit button
As a corollary to the above, if you're making a minor edit (e.g. fixing a spelling error or tweaking formatting), check the "This is a minor edit" button below the Summary box before saving the page. Again, this will make things easier for the rest of us.

Use the Preview Button
The preview button is right next to the save edit button, and is there for a reason. It's your own personal spell checker, link checker, whatever-else checker. Use it. Users that purposefully do not preview edits as to inflate their edit count are not well regarded amongst Halopedians, and you may find yourself in trouble with an administrator.

Don't link to the current page
In other words, a page should not link to itself. If it is attempted, the link will simply turn into bold text.

Link once
A given page should only contain one link to any other page. If a page links to Captain Jacob Keyes in one place, then that should be the only link to Captain Jacob Keyes on that page. Typically this link should be the first instance of the term in the article.

Don't use conversational style
This is an information site. It should read like Wikipedia, not like your diary.


 * Check your spelling and grammar. Don't use internet slang (ex. "How r u?" or "c u 2nite"). If you're not 100% sure about the way a word is spelled, type it into Google or Dictionary.com. If you know that you're not the strongest speller, compose your edits in a word processor like Microsoft Word or use Mozilla Firefox or Google Chrome which has spell-checking built in.
 * Don't use "smileys" or "emoticons".
 * Don't "reply" to content others have posted. If you think a particular point warrants discussion, post on the article's Discussion page. If you're 100% sure that something should be changed and don't think a discussion is necessary, just change it. Dialogue goes only on articles' Discussion pages or the forum.
 * Never abbreviate the names of characters, places, or anything. Wherever possible, use the full name of a character the first time they are mentioned. After the first mention, you may refer to "Master Chief" as "the Chief" or "Captain Jacob Keyes" as "Keyes" and so forth.

Stubs
If you don't know enough information on a topic, or you know there's more, add a stub to it. To do so, try this:

And people will know that it's a stub by looking at the stub category. Generally the template is put at the bottom of the page.

Don't sign your edits
All contributions are appreciated, but if every user left their mark on every contribution they made, the Wiki would be nothing but signatures. If you've made an edit that you're particularly proud of (such as a transcript or screenshot), the correct place to take credit is on your own user page. If you do not have a user account, we respect your anonymity, but your edits will remain anonymous, too.

Do sign your Talk posts
If you make a post on a discussion page, please sign it. If you have a user account, this is as easy as typing ~ at the end of your post. If you don't have a user account, just sign it with your name or nickname so everybody can tell who's who when reading long conversations. Even better, create an account anyway and use the signature method described. There really is no reason not to if you're going to stick around.

Headers/Headings as Links
Never make a header title as links. Instead, use the Main Redirect Template and add it under the header. Additionally, avoid adding the the Ref Tag to the header.

Article Standards
The purpose of standardizing all articles to an official format is to improve the quality and readability of all articles in Halopedia. That said, all users must follow the official format.

Summary/Brief Introduction
A brief introduction of the level with a plot summary. Shouldn't be detailed.

Description
A section for more detailed information on the level, including an in-depth plot summary and achievement information.

Transcripts
Transcripts should be added with a YouTube Link embedded in such format {Cutscene}

Behind the Scenes
Includes characters involvement, production notes, etc. Shouldn't include weapons, vehicles or glitches.


 * This section should also include link to walkthrough.

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Gallery
All images should be included in the gallery section. Images should not be added in the above sections as it is messy.

Layout
Includes a detailed description about the level's layout.

Strategies
Strategies should focus to those which is quick, simple and effective. Forge tips should be avoided.

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Gallery
All images should be included in the gallery section. Images should not be added in the above sections as it is messy.

Character

 * 1) Please name all character articles by their full known name, not their title/rank as well. For example, Sergeant Major Johnson's article is titled Avery Junior Johnson, not Sergeant Major Avery Junior Johnson.

Summary/Brief Introduction
A brief introduction about the character and his/her background. Shouldn't be detailed.

Biography
In chronological order. List out the character's history (involvement in the Human-Covenant War, early life, etc).

Personality and Traits
Information regarding the character's personality and traits should be detailed here. "Extra" information about the character's combat style and attitude towards enemies/allies can be added if applicable.

Identity/Appearance/Age
If it applies to the character, this section should be included. If "Identity" is needed, list out Bungie's production notes on the character's identity. If "Appearance" is needed, list out his/her appearances in either games, novels, or other media.

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Gallery
All images should be included in the gallery section. Images should not be added in the above sections as it is messy.

Summary/Brief Introduction
A brief introduction about the weapon's origin. Shouldn't be detailed.

Design details
Includes the description and operation of the weapon.

Ammunitions
Describes the type of ammunition used by the weapon. Applicable only to rifles, pistols, etc.

Accuracy
Only applicable if the accuracy differs significantly throughout the series. Outlines the accuracy issues by the weapon.

Advantages
As per title, advantages only. Strategy should be removed.

Disadvantages
As per title, disadvantages only. Strategy and tips should be removed.

Influence
If applicable only if it has relations to the real world or to the species' culture.

Tactics
Brief description of tactics for the weapon.

Campaign
Campaign tactics listed here. Should be brief and straight-forward.

Multiplayer
Multiplayer (Online and Offline) tactics listed here. Should be brief and straight-forward.

Advanced Tactics
Covers the miscellaneous/extra information. Should be brief and straight-forward.

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Gallery
All images should be included in the gallery section. Images should not be added in the above sections as it is messy.

Background
What type of unit this is, the actions they have taken, and a brief summary of their exploits.

History
The entire history of the unit, from conception to disbandment (if applicable).

Subordinate Units
All subordinate units under the command of the topic unit.

Personnel
All personnel assigned to the topic unit.

Equipment
All equipment used by the topic unit.

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Music/Song
There is no official format for Music/Song articles except a brief overview/description of how the music/song is produced (Hoodwind, piano, Gregorian Chant, etc). Additionally, scenes where the music/song is played should be included.

Also, a YouTube video should be added to the article if available and a Music Template should be included at the end of the article. If a YouTube video is added, it should be in such code: 200px|right.

Note: a Song is defined as metrical composition intended or adapted for singing, especially one in rhymed stanzas; a lyric; a ballad where as a Music is defined as pitch (which governs melody and harmony), rhythm (and its associated concepts tempo, meter, and articulation), dynamics, and the sonic qualities of timbre and texture. That said, a Song is when a lyric is present (Example: Breaking Benjamin's Blow Me Away used in Halo 2) whereas a Music is when only the melody is heard (Example: Chopin's "Preludes #15, Raindrop" used in Believe campaign).

Starship
undefined

Background
A brief summary of what the ship's mission is and the history.

Operational History
An extensive history of the history of that particular ship.

Armaments
An extensive summary of the weaponry aboard the ship, including small arms lockers for Marines.

Aircraft
An extensive summary of the aircraft aboard the ship.

Marines
An extensive summary of that particular Marine contingent aboard the ship.

Command Crew
A list of all members serving with the Command Crew.

Officers
All officers serving aboard the ship.

Crewman
All crewman (enlisted) serving aboard the ship.

Marines
All Marines stationed aboard the ship.

Pilots
All Pilots stationed aboard the ship.

Ships of the Line (Only for ship class)
An extensive list of all ships in a particular class. i.e. the UNSC Pillar of Autumn was a Halcyon-class Cruiser.

The format for listing ships should be as followed: * (Hull Classification Symbol - Hull Number)

Trivia
Redundant trivia should be avoided. Glitches, Misc Information, and References should be added here.

Gallery
All images should be included in the gallery section. Images should not be added in the above sections as it is messy.

Action Figures Series
Action Figures should be grouped according to its series/wave. A perfect example would be McFarlane Halo 3 Series 1 where all of the figurines are grouped together. As such, all action figure articles should follow this format. There should be no individual articles.

Description/Overview/Summary

 * NOTE: Only two (2) images should be added to an action figure section at a fixed size of . Refer to McFarlane Halo 3 Series 1.
 * NOTE: If the action figure has other colour variants, utilise the . Refer to McFarlane Halo 3 Series 1.

Includes what colour variations, armour permutations/variants, weapons, etc. Information such as prices are considered unreliable as the value of these action figures changes.

At the end of the section, add a.

Walkthrough Standards
This is to improve the quality and readability of all walkthroughs available in Halopedia.

English Use
Every walkthrough should be spell-checked, grammar-revised, and reviewed by a veteran user to ensure that the walkthrough is within our MOS. That said, internet memes and slangs should be avoided.

Sections
Every walkthrough should be divided into their own respective sections. For instance, if the level has 4 cutscenes, then the walkthrough should also be divided into those 4 sections. This is to avoid confusion for visitors and new users. Additionally, walkthroughs must be written using the Legendary Difficulty as it will provide players the best advices and strategies in lower difficulties (In layman's terms, if you can do Legendary, you can do Easy, Normal and Heroic).

Templates
Only the Succession template should be added at the end of a walkthrough. The Level template is only reserved for the main articles.