StrategyWiki:Guide/Organizing the pages

After the initial planning stage, the next issue is how to organise the content. Unlike traditional walkthroughs, information in StrategyWiki guides should be separated into subpages when it reaches a certain length. While most games will require three or four pages at the very least, some games, like Sega Swirl, are simple enough that they can be covered on a single page.

Unlike Wikipedia, StrategyWiki uses subpages (e.g. Game Name/Walkthrough). All pages must be sub-pages of the main game page.

Capitalisation
As with headings, page names should be capitalised correctly, with the main page of a guide taking the game's name, and sub-pages taking sentence case, apart from Table of Contents and Getting Started, which are special. So, for example, a page on a fictional quest called "The gates of Valhalla" would be Game name/The gates of Valhalla. The only exception to this rule is if the quest name is referred to within the game with different capitalisation, the page titles here can be capitalised to match.

For information on the benefits of using sentence case in titles, see Wikipedia.

Types of subpages
There are many types of subpages that make up the guide as a whole. The most common types are explained below.

Table of Contents
While the walkthrough is the heart, the Table of Contents is the veins. Every guide has one (unless it is a single-page guide), and it should link to all pages used in the guide to enable quick access from anywhere to anywhere else.

First of all, the ToC should be generic, simple, and similar to other ToCs. The Table of Contents should have a variety of sections, such as Getting Started (covering controls, characters, and other basic information), Walkthrough (encompassing one or more pages covering the main levels or missions from beginning to end), and Appendices (for anything that does not fit into the other sections). Specific guides (such as Mega Man 7/Bosses) are usually listed under Appendices.

Because the Table of Contents is automatically included on all pages as part of Header Nav, if standard headings are used in it MediaWiki gets confused. Because of this, the /Table of Contents sub-page should use  for headings instead of   — i.e. use the h2 template. For a Table of Contents with many sections you can use col to divide the sections into columns (three is recommended for most purposes, although some guides will need more or fewer than this). A sample Table of Contents is shown below. You can see how it appears when saved, or click the edit link above to see how it is created. 🇨🇴

🇨🇴
 * Characters
 * Controls
 * Items

🇨🇴
 * 1) Level 1
 * 2) Level 2

🇨🇴 Note that this layout is purely visual; as a general rule, the actual page locations only need to be tiered once (e.g. Game/Level 1 instead of Game/Walkthrough/Level 1). This prevents pages from having complicated titles (e.g. Game/Walkthrough/Core Missions/Ric/Bombs Away, Baby) and also makes linking easier.
 * Cheats
 * Secrets
 * Patches

Sequential pages (e.g. the linear walkthrough) should be numbered (with #), while things that can be done in any order should be bulleted (with *).

Typically in larger tables of contents, the list of pages is split up into several columns, so that space is used more effectively. To do this, the col template needs to be used. Its usage is beyond the scope of this guide, but documentation is available on the template's page, and some example games (such as Diablo II) make good use of it. Similarly, games with expansion packs will integrate the expansion pack's table of contents into the main game guide's, using the subtoc and subtoc2 templates. Their use is also beyond the scope of this guide, but Diablo II is also a good example for their use.

To get you started, here are some generic ToC layouts for various genres:

🇨🇴 Adventure 🇨🇴 RPG/Action-adventure 🇨🇴 Racing 🇨🇴 Fighting 🇨🇴
 * Characters
 * Commands
 * Game Overview
 * FAQs
 * Walkthrough
 * Items
 * Secrets
 * Characters
 * FAQs
 * Walkthrough
 * Sidequests
 * Enemies
 * Items
 * Weapons
 * Armor
 * Spells
 * Controls
 * Cars
 * Tracks
 * Cups
 * Controls
 * Moves
 * Tactics
 * Tips and Tricks

Strategy
Mostly used for strategy/tactical/simulation/squad-based games, this page should provide general strategies. Mission-specific strategies should probably be covered on the page for that mission. It's also useful to spread a few handy reminders (e.g. "remember, Night Elves deal only half damage against Fell Orcs unlike the rest of their race") throughout the walkthrough.

Move lists
As a rule, only fighting games and beat 'em ups have these. Handle beat 'em up move lists much the same way as controls pages. Fighting games, however, are handled differently. Move lists are typically found in games that have a series, such as Street Fighter II. Move lists are put in two places: To prevent the need to copy the information in two places, and update a list twice, we put the list in one place and transclude the list. Each character in each game gets a single list (e.g. Street Fighter Alpha 2/Ryu), and it is transcluded in the two locations listed above by typing:. The colon in the beginning is an instruction to include the contents of that page on the current page that you are editing.
 * 1) The game for which the list applies (e.g. Street Fighter Alpha 2).  This page includes front page information about a game, including an info box, and table of contents, as well as the complete move lists for the game in question.
 * 2) The character page for the series (e.g. Street Fighter Alpha/Characters/Ryu).  This page includes biographical and possibly technical information about the character in question, as well as all of the move lists that apply to this character in the particular series.

Non-English guides
At present, StrategyWiki only hosts English-language guides. If enough interest is shown in other languages, support for them can be added much like at Wikipedia. Note that this doesn't mean you can't write a guide for a game which isn't in English (although that might be hard) — it just means that currently, all guides have to be written in English.