RuneScape:Style guide/Layout

This style guide on page layout is a style guide used to determine the overall layout and ordering of pages.

Use common sense when needed, but the following section outline describes how an article should be structured. This does not include everything, but it is an indicator of how item an article could look like. This default was made to create more consistency between articles. Although it is meant to provide a general structure, it may be deviated from if necessary.

Header

• {{External}}
• Hatnote type templates (e.g. {{Otheruses}})
• Messagebox type templates (e.g. {{HasStrategy}}/{{Cleanup}})

Body

Entity	Examples	Notes
Main infobox	e.g. {{Infobox Location}}	See Category:Infobox templates for an exhaustive list of infoboxes.
Main image	[[File:Blade of saeldor detail.png]] [[File:Wyrm icon.png]] [[File:Duradel chathead.png]]	If the subject has both DII (Detailed Item Image) and chathead available, include the chathead after the DII. For NPCs, prefer a chathead image, otherwise an icon image if it has one.
Article introduction	The dragon scimitar is the strongest scimitar ...	The subject should be emboldened and include the most relevant information about the item in the first sentence.
Article-specific sections	==Treasure Trails== ==Transcript==	For articles about an equipped item, place the {{Infobox Bonuses}} template before the article-specific sections. Example articles: Dragon scimitar, Kandarin headgear 1, Wise Old Man

Section order

Sections should be level 2 headings and adhere to the order outlined below. Some sections may not be relevant to the article and thus should not be included.

Section name	Must include	Notes
[Skill name] info	A list of templates appropiate for this section can be found at Category:Skill info templates
Combat styles	{{CombatStyles}}
Creation	{{Recipe}}
Products	{{Uses material list}}
Item sources	{{Drop sources}}
	{{Store locations list}}	Should be under a level 3 "Store locations" header
	{{Item spawns}}	Should be under a level 3 "Item spawns" header
History
Treasure Trails	{{Anagram}}, {{Cipher}}, {{CrypticNPC}}, {{FaloItem}}, {{CharlieItem}}, or {{SherlockChallenge}}
Family	{{Family tree}}	The template must be correctly formatted into another template related to the article similar to {{Family tree Ardignas}}.
Music unlocked or Music	Music name(s) as wiki links formatted into a table
Transcript or Dialogue (for NPC pages)	{{Hastranscript}}
Combat Achievements		Combat Achievements tasks should be linked to and formatted into a table.
Changes	{{Subject changes header}}, {{Subject changes}}, and {{Subject changes footer}}	{{Subject changes header}} should be used on top of the changes list with the entries placed into {{Subject changes}} and {{Subject changes footer}} as the list's footer. See the documentation for more information on formatting.
Gallery	<gallery></gallery>	"(historical)" should be appended to the header whenever the gallery is about the subject's graphical update.
Trivia	Bulleted list
See also	Bulleted list
Notes	{{Notelist}}
References	{{Reflist}}
External links	Bulleted list	External links to the official website or a database related to the article that either do not go into the infobox or the article's body.

Items

The item infobox should also be added and filled with the appropriate values, after which a short paragraph introduces the item. This does not have to be very long. Only the item infobox and the introduction are required on an item article. Inclusion of images and/or what sections are used (see below for a full list of possible sections) depends on the kind of item and is thus optional.

Images

Images should complement the article and occasionally should supplement the article (in the case of maps, etc). Images should be right-aligned. However, centre-alignment can be used for some images in the articles, such as maps or left-aligned when the right side is cluttered or when it is more fitting. The detailed image of the item at the starting section should also be left-aligned. Images should be of the item or where it is obtained.

Quests

The lead section should be summarising the plot of the quest and, if possible, it is recommended to follow the following section structuring:

1. Details (with the inclusion of {{Quest details}}; {{Quest details page}} for quick guides)
2. Walkthrough (with appropriately-named level 3 headers for each section of the quest)
3. Rewards (with the inclusion of {{Quest rewards}}; {{Quest rewards page}} for quick guides)
4. Required for completing (detailing the quest/diary requirements in a bulleted list)
5. Transcript
6. Music unlocked
7. Historical/Pre-release info
8. Developers (in a bulleted list)
9. Changes
10. Trivia

Drop tables

It is recommended to follow the precedence for drop tables as shown, if applicable. Some exceptions apply, such as loot chests and implings.

For the following, a "sufficient amount" is defined as more than three items.

1. 100%
2. Uniques/Pre-roll
3. Weapons and armour (If a sufficient amount of either exist, it may be split with "Weapons" being first)
4. Runes and ammunition (If a sufficient amount of either exist, it may be split with "Runes" being first. If a sufficient amount of rune drops exist, it should be split into "Elemental runes" and "Catalytic runes")
5. Herbs (Using {{HerbDropTable}})
6. Seeds (Using the appropriate seed tables)
7. Coins (If multiple quantities are possible)
8. Either "Resources", "Potions", "Consumables", "Other", etc. If there is an insufficient amount for one section, it may be merged into a larger "Other" section.
9. Gem/Rare drop table. (Using {{GemDropTable}} or {{RareDropTable}})
10. Tertiary (For items that are dropped independently of the main drop table, such as clues)
11. Other tertiary tables, such as "Catacombs tertiary", "Wilderness Slayer tertiary", and "Wilderness Slayer Cave tertiary".

Footer

• {{Succession}}
• Navboxes (See Category:Navigational templates for an exhaustive list of navboxes.)
• {{Restricted title}} or {{Parentitle override}}
• {{DEFAULTSORT}} or {{DISPLAYTITLE}} magic word
• Categories
• {{Stub}}