From StrategyWiki, the video game walkthrough and strategy guide wiki
Jump to navigation Jump to search
(another link fix)
(comprehensive guide to creating a main game page. added info from other pages, moved info to other pages)
Line 1: Line 1:
{{subpage|Needs to be split between all the walkthrough pages}}
{{Header Nav|game=StrategyWiki:Guide}}
{{Header Nav|game=StrategyWiki:Guide}}
Starting a guide can be a tedious process at first, but by the time you've finished reading this guide, you'll be well on your way to starting and contributing to guides.
The first step to working on any guide is finding the guide on the wiki. After [[StrategyWiki:Guide/Searching|searching]] for the guide you want to work on, you may find that it doesn't yet exist. If that's the case, you should start out by creating the main page. See the [[SW:SCOPE|scope policy]] first to make sure the game qualifies for inclusion on the wiki.


==Getting Started==
==Naming==
===Differences from plain text guide writing===
{{sidebar|width=200px|title=Note|contents=Due to server configuration, the percent symbol (%) does not work correctly in page titles.}}
There are some important and fundamental differences between wiki content and traditional guide writing.
Each game gets its own page. When naming a guide, attempt to use the official name given by the game developer or publisher. In most cases, it's not a good idea to go by how the title is presented on the cover art, which uses artistic typesets and splits titles across multiple lines. If no official name is available, all words except for [[WP:Title case#Headings and publication titles|internal closed-class words should be capitalized]].
{{-}}
===Disambiguation===
If there are multiple games with the same name that require different guides, the first release that was given the name should get the title.  To help users find guides for other games with the same or similar names, disambiguation links should be added to the front page, with one blank line separating them from the end of the infobox.  These links should either point to a series category which contains all the relevant guides using the {{t|series disambig}} template, or directly to each game using the {{t|game disambig}} template). For example, the [[Super Punch-Out!!]] page has a link at the top to the SNES version, and the [[Batman]] page has a link to the Batman category.


* ''Nobody "owns" the guides.'' All content is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike License].
For games with the same title that are ''not'' the original, titles are disambiguated by following them with the game's system, year or other identifying characteristic in parentheses. In the case of simultaneous releases of different games with the same title, the first guide to be written gets the main title and any guides that follow will be disambiguated. Another occurrence may be a game that is released under two different names in different regions or for different consoles. In this case, the main title also goes to whichever guide is started first. The alternate name would then be redirected to the main game so that anyone searching for it would end up in the right place.
* ''There are no closing comments sections.'' Each guide is considered to be written by the community. Writings speaking for the community, or any other for that matter, are not welcome.
* ''There is no copyright section.'' The disclaimers link at the end of the page outlines the terms of the license.
* ''No contacting section.'' That means no e-mail addresses or chat handles. Use talk pages, instead.
* ''No credits section.'' A list of contributors is recorded automatically by MediaWiki (click on the history tab to see).
* ''No attribution.'' All edits are automatically attributed (click on the history tab to see).
* ''You can use rich text formatting and some HTML.'' ('''bold''', ''italic'', <u>underline</u>, [[Main Page|hyperlinks]], etc.) using MediaWiki markup, or HTML if no MediaWiki equivalent exists.
* ''Tables are allowed,'' as long as you use wiki markup for them.
* ''Images that enhance the quality of a guide are allowed, and encouraged.'' We provide a place to upload images onto our servers.


===Starting a guide===
Exceptions to the above rule exist for games that became popular under a certain name or were originally released with a non-English title. If the game was released under multiple names, it is common practice to use the name most known globally. If there is a tie, it is up to the discretion of the guide's original writer. As an English wiki, English titles take precedence over foreign ones. Common examples are games released first in Japan, which get the English title for their guides here.
The first thing is to choose a game to write for. It's best to choose a game you like and have played through completely to be fully able to write about it.  Think about how you will go about collecting information and how to organize information prior to creating pages for it.  Here's a few tips for starting off:
* ''You will need some amount of motivation or ambition to work on your chosen game.'' If you meet another fan also interested in working on that game, that's great; this will distribute the workload.
* ''You don't have to immediately jump into writing the [[StrategyWiki:Guide/Organizing the pages#Walkthrough|walkthrough]]'' (which is oftentimes the hardest part). If you want to concentrate on an item list or boss strategies to get used to wiki guide writing, that's fine.
* ''Changes go live the moment you hit save.'' You can write as much or as little at a time as you like.


Remember, if you're ever uncertain of how to lay out your page, you can use the [[StrategyWiki:Sandbox|Sandbox]] to test it. Bear in mind that it's a free-for-all workspace; if you come back later and your work is gone, check the history for the last edit beside your username. By editing this old revision you can get back what you were working on (however, any additional changes to the page will need to be merged in with your new content – you may want to just copy the necessary text and then load the current version of the page before editing).
Article disambiguation can be complicated, so when in doubt, bring candidates for disambiguation to the attention of other editors and admin by posting in the [[StrategyWiki:Staff lounge|staff lounge]].
* ''If necessary, confirm that the game in question is [[StrategyWiki:Guide/Scope|notable]]''.  While it is ideal to cover every game, a guide is only useful if there is or was a significant player base. Otherwise, you may expend too much effort into writing a guide that may never be seen.


Once you've decided on a game, you'll need to start it up and fill out an infobox. But first it needs a name.
===Versions===
If a particular version of the game has changes (such as more/fewer characters or remixed levels) this should be explained on the appropriate pages. However, if a game is substantially different from other versions, it may warrant having its own guide, in which case it would use the standard disambiguation in its title. In general, combining guides should be tried first to avoid duplication of effort.


===Naming===
It is also possible to share the guide up to a certain point, then put any ''extra'' information on the guide to which it applies. See the [[../Table of contents/]] page for how to use the {{t|subtoc}} to accomplish this.
{{sidebar|width=200px|title=Note|contents=While you should use the correct name of the game wherever possible, please do not use % (percent) in the page name. Due to server configuration this symbol does not work correctly. Any other characters should be fine, and there is no problem using the percent sign within page text.}}
Each game gets its own page, preferably the official name of the game. If there are multiple games with the same name that require different guides, the first release that was given the name should have its guide with that location. To help users find guides for other games with the same or similar names, disambiguation links should be added to the front page, with one blank line separating them from the end of the infobox.  These links should either point to a series category which contains all the relevant guides using the {{t|series disambig}} template, or directly to each game using the {{t|game disambig}} template).


When naming a guide, attempt to use the official name given by the game developer or publisher. If no official name is available, all words except for [[WP:Title case#Headings and publication titles|internal closed-class words should be capitalized]]. For sub-pages within a guide, all pages should follow the in-game naming and capitalization. For sections not mentioned directly in the game, sentence case should be used.
==Page creation==
[[Image:StrategyWiki Template Page Buttons.jpg|thumb|right|Use the "Main game page" button to start a new main page.]]
There are many ways to get to the page creation screen:
# ''Search box'': Put the name of the game in the search box and press "Go" or "Search". If the game doesn't exist, you'll see a red link to it at the top of the results page where it says "You searched for ''Your Game''". If you pressed "Go", there will also be a link under the "No page title matches" section, and the link will say "create this page".
# ''Address bar'': You can type the URL of the page you want to create directly into your browser's address bar by putting in <tt><nowiki>http://strategywiki.org/wiki/</nowiki>'''Your Game'''</tt>. This takes you to a splash screen letting you know the page doesn't exist. Click the link that says "edit this page" to create it.
# ''Red link'': Any time you see a red link on the wiki, it means the page being linked to doesn't exist. If you find a link to the main page you want to create, it will take you directly to the editing screen where you can begin to create the page.
 
Setting up the main page for a new guide has been simplified with the use of the preload buttons above the edit box. Simply click on the "Main game page" button to be given a basic layout, then just fill in the blanks.
{{-}}
{{-}}
===Article disambiguation===
==Content==
If two games with the same title differ dramatically from one another, a disambiguation system will be used whereby the system of release and/or year of release are included in the title (abbreviated if appropriate). For example, the [[Super Punch-Out!!]] page has a link at the top to the SNES version, and the [[Batman]] page has a link to the Batman category. If the games have the same name and system but different publishers/developers, put that in parentheses.
The main page of a guide should be set up as contained in the main page pre-load template, with the following in this order:
 
#Any tags, such as {{t|future}}, {{t|stub}}, etc.
If releases are the same game on all but one system, the most common game should occupy the main name with disambiguation only for the special title. For example:
#The {{t|Header Nav}}.
* Spiderman The Movie II — Spiderman on all consoles.
#An {{t|infobox}}.
* Spiderman The Movie II (NDS) — Spiderman on the Nintendo DS
#Any disambiguation templates, such as {{t|game disambig}} or {{t|series disambig}}.
When in doubt, bring candidates for disambiguation to the attention of other editors by posting in the [[StrategyWiki:Staff lounge|staff lounge]].
#The {{t|marquee}} template for [[arcade]] games with a marquee image.
 
#Introduction section ''without'' a heading. It should be a paragraph or so in length and provide a general introduction to the game and its development. The first occurrence of the game name should be emboldened using <nowiki>'''</nowiki>, and the {{t|nihongo}} template should be used to add Japanese text where applicable. The first occurrences of items such as dates, systems, companies or other games should be linked.
If the same game was released under multiple names, it is common practice to use the name most known globally. If there is a tie, it is up to the discretion of the guide's original writer to name the game guide (just make sure properly categorised redirects are present for the other names). See [[#Alternate titles|alternate titles]] for more information.
#{{t|Continue Nav}}
 
#A short story or gameplay section, also without a heading. This section is not meant to be comprehensive, but should give a broad overview of the story or gameplay, or contain the relevant backstory for the game.
===Creating the main page===
#An optional <nowiki><gallery></nowiki> of alternate box art, game flyers, etc.  
[[Image:StrategyWiki Template Page Buttons.jpg|thumb|right|The new page template buttons for ease of use.]]
#{{t|ToC}}.
Once you've decided on a page name, the easiest way to get started is to type the full name of the game you want to work on into the [[Special:Search|search]] box (at the top right of every page) and press "Go". If nobody has started a guide for your game, the resulting page will tell you so. Then, just click on the "create this page" link to begin editing your guide's first page.
#An optional external links (<nowiki>==External links==</nowiki>) section. See the [[StrategyWiki:Guide/External links|external links policy]] for information on appropriate content for this section.
#The series navigation template, if one exists. These are in the form of '''<nowiki>{{</nowiki>''Series Name''}}'''.
#<nowiki>{{DEFAULTSORT:}}</nowiki> where applicable.
#Categories located at the bottom. See [[StrategyWiki:Guide/Categorization|Categorization]] for more information.


Before any work is done on the guide, there must first be a main page. Setting up the main page for a new guide has been simplified with the use of the template buttons above the edit box. Simply click on the "Main game page" button to be given a basic layout, then just fill in the blanks. If you can, write a summary or introduction to the game (see other guides for examples of such). This should include a few lines about the history of the game and some spoiler-free teasers about the beginning of the plot. At all costs, avoid any spoilers on the main page.  Note that the template buttons will only appear when editing a nonexistent page.
==The infobox==
{{details|Template:Infobox|the infobox template}}
Some fields in the infobox are mandatory, and some are optional. In general, the more information you can provide, the better. If any mandatory fields are missing, the page will automatically be added to [[:Category:Pages needing an infobox]]. Optional fields can either be left blank or removed entirely. Whenever possible, use a simple wikilink (i.e. <nowiki>[[</nowiki>''Page name'']]). Most fields link to categories, and the normal link usually redirects to the category page. If it doesn't, use {{t|c|''Page name''}} to link directly to the category.


Unless an article is very short, it should start with a "lead" comprised of one or more introductory paragraphs. The lead should ''not'' be explicitly entitled <nowiki>==Introduction==</nowiki>.
;Mandatory fields
*''title'': Automatically filled in when using the "Main game page" preload, but you may need to adjust it if the page title contains disambiguation.
*''developer'': Add links to developers if they are companies. For an individual, just put the person's name in plain text.
*''publisher'': Add links to publishers if they are companies. For an individual, just put the person's name in plain text.
*''released'': Using [[:Category:Release date templates|release date templates]], add release dates by region. The minimum amount of information is the year of release.
*''genre'': Add links to applicable [[:Category:Genres|genres]].
*''systems'': Add links to all [[:Category:Systems|systems]] for which the game was produced. Systems are actual hardware on which the game is played. For digital distribution, e.g. [[WiiWare]] or [[PlayStation Network]], use the ''distributor'' field.


The subject of the article should be mentioned in '''bold text''' (not '''''bold and italicised text''''' as on Wikipedia) in the first sentence of the introduction.
;Optional fields
*''image'': Put cover art here for console releases, arcade flyers for arcade games, or logos for online games or games that weren't released in retail stores. The field takes the name of the file and its extension, i.e. ''Filename.ext''.
*''distributor'': If the game has been released on a digital distribution service (e.g. [[Steam]], [[GameTap]], etc.), put links to them here.
*''designer'': Put the plain text name of the designer or designers. Do not put their specific jobs in parentheses afterward. Use the introduction paragraph to expand on the designers if need be.
*''engine'': Add a link to the [[:Category:Engines|engine]] used by the game.
*''version'': Add the latest version to this field. This is meant for games that get usually downloadable updates.
*''players'': Add the number of players. Don't add the ''modes'' field if this one is used.
*''ratings'': Using [[:Category:Rating templates|ratings templates]], add any ratings the game has received from official organizations.
*''modes'': Add links to any [[:Category:Modes|modes]] for the game. Don't add the ''players'' field if this one is used.
*''media'': Put any non-standard media on which the game can be played here. Don't add standard media here – a player would know that [[Nintendo 64]] games come on a cartridge, for example.
*''input'': Put any non-standard input here, such as alternate controls and accessories. Don't add standard inputs here – a player would know that computers use keyboards and the [[PlayStation 2]] uses a controller.
*''requirements'': Using the {{t|pcreq}} template, add relevant software and hardware considerations for computer games.
*''website'': If there is an '''official''' website, the URL goes here in the form of <tt><nowiki>[http://</nowiki>www.gamepage.com Official site]</tt>. This field is not for links to forums or retailers, but can be used for the original page where a flash game or online game is played.
*''expansion'': If there are expansions to the game, list links to them here separated by <nowiki><br /></nowiki> tags.
*''series'': If the game belongs to a series of games, put the series name here '''not inside a wikilink''' – this field is linked automatically.
*''preceded by'': If the game is following a previous one from the same series, put a link to the previous one here.
*''followed by'': If the game comes before a later one from the same series, put a link to the next one here.


Normally, the first paragraph clearly explains the subject so that the reader is prepared for the greater level of detail to follow. If further introductory material is needed before the first section, this can be covered in subsequent paragraphs.
;Helpful templates
* {{t|sys}}: Use this template to separate fields by system. For instance, if a game was released at different times on two separate systems, you would use {{t|sys|''System one''}} then the release dates for that system, followed by {{t|sys|''System two''}} then the second system's release dates.
* {{t|co}}: Use this template to show which company developed or published the game for a particular system or region.
* {{t|pcreq}}: Use this template in the ''requirements'' field to show nicely formatted requirements for computer games.
* {{t|c}}: Use this template to link directly to categories when a plain wikilink doesn't get there. For example [[[[Racing]]]] goes to a guide page, while <nowiki>{{c|</nowiki>{{c|Racing}}}} goes to the category.
* {{t|collapsible list}}: Use this template for overly long fields, such as release dates, ratings or requirements when they create too much whitespace on the page.
* {{t|sys/nocat}}, {{t|co/nocat}} and {{t|rd/nocat}}: Use these templates to show information for systems, companies and release dates, respectively, while not automatically categorizing the page. Useful when there is a categorized redirect to the page.


The lead is automatically followed by the {{t|Continue Nav}} template, then a story or gameplay section, the {{t|ToC}} template and finally the categories. The {{t|infobox}} for the game should also be located in the introduction.
==Text==
Unlike in individual guide pages, when writing the lead and plot synopsis for a main game page, use a third-person voice and include links to other pages on the wiki. This means you should refer to a "player" instead of saying "you", and link to the first instance of companies, dates, other games, etc. All links use no extra formatting, meaning don't use italics or bold when linking to other games.


==Further tips, hints and other suggestions==
Each page should start out with a lead, which immediately follows the {{t|infobox}} and any optional templates, such as {{t|game disambig}} or {{t|marquee}}. The subject of the article should be mentioned in '''bold text''' (not '''''bold and italicised text''''' as on Wikipedia) in the first sentence of the introduction. It is also important to list any alternate names in bold, as those names should redirect to the page and need to be easily identified by anyone who was searching by them. Use the {{t|nihongo}} template to format the addition of a Japanese title and include a link to Wikipedia's help page on Japanese.
===Writing guidelines===
The primary purpose of StrategyWiki is to inform, not entertain. Guides should contain a minimum of "fluff" (also known as "[[#What is "drivel"?|drivel]]") and focus on being as detailed and descriptive as possible. Similarly, all guides must be objective and devoid of personal opinion. Different techniques and strategies may be suggested with the goal of determining the best technique or strategy.


When writing, always maintain a single focused "voice". Do not refer to yourself ("I", "me", etc.) in the guide.
The first paragraph clearly explains the history and development of the game, much of which is simply a written version of what is contained in the infobox. If there is anything notable or unusual about the production of the game, or you can provide a higher level of detail than the infobox, this is the place to put it. The information in the lead is mainly for meta information on the game, meaning very little or nothing about gameplay or plot.


Always give alternate options. Many solo guide writers often choose what they say is the best way to complete a certain objective, but another gamer might choose another route. If there are multiple ways to do something, writing them all out could be useful to the reader.
The next section of writing, separated from the lead by the {{t|Continue Nav}}, is for a plot synopsis or overview on the game's mechanics. This section should include '''no spoilers''', and is meant to inform readers who may have no idea what the game is about. This is not the place to divulge what happens in the game, but merely information on the game's "universe" or backstory so that a reader can understand what the game is about.


Spelling and grammar should be checked by contributors before an edit is saved. The newer versions of [http://www.mozilla.com/en-US/firefox/ Mozilla Firefox] automatically mark spelling mistakes in text boxes. You can also copy the text into Microsoft Word or another word processor and run a spell check. If proper nouns specific to a game are used, please ensure that they are correctly spelled and capitalized.
==Images==
Box artwork goes in the infobox, and should be at least 250px wide to prevent stretching. Also ensure that the cover image includes no watermarks, no borders and no "pending" rating symbols. Box art should also present a directly faced image, meaning it shouldn't be a 3-D box shown at an angle. For games which are unreleased, use [[:Image:Future box art.png]] in the infobox. Game logos and artwork are not acceptable substitutes for box artwork when a box for the game exists. If the game was never released in physical form, or never in a box, make sure the artwork chosen is official – either a logo, welcome screen or start screen. For games that are released on multiple systems, it is unimportant which version of the cover you use, as long as the actual artwork is the same. This means you can use the Xbox 360, PlayStation 3 or Windows version of the cover, as long as the only differences are logos and symbols ''on top'' of the artwork. When this is the case, '''do not''' upload multiple versions.


===Crediting sources===
For extra images not being used in the infobox, include them in a <nowiki><gallery></nowiki> between the plot synopsis and the {{t|ToC}} template. Images to include here are actual alternative covers (meaning the art is different, not the systems/developers/ratings/etc.), flyers, screenshots, or other interesting images. Don't go overboard with these, as they still need to add something to the reader's understanding of the game to comply with fair use.
If you find yourself in the situation that you need to credit information, do so in the edit summary. Because information (''including'' cheat device patch codes) cannot be copyrighted or otherwise protected, you can take cheat codes or item stats from other guides as long as your wording and presentation of those details are sufficiently different.


===Organize well===
==Categories==
Keep paragraphs short. Their size will vary depending on screen resolution and font size, but as a general rule you should start a new paragraph whenever something major takes place or it just seems like a good time. For example, in an [[:Category:adventure|adventure]] game, using a paragraph for each major location or location change is probably a good idea. Whatever is most fitting and appropriate for the guide while not being redundant is welcome.
{{details|StrategyWiki:Guide/Categorization|categorizing}}
* ''Use {{t|sidebar}} for notes that accompany a page that aren't a necessary feature of it.'' Use the sidebar to indicate the location of ancillary information which will help those looking for those things, while not interrupting those only interested in the core subject of the page.
Most of the categories by which a main game page should be categorized, are found in the infobox. Categories go below all the visible content on the page, usually just below the {{t|ToC}} template or series nav, if it exists. Categories are added by putting <nowiki>[[</nowiki>Category:''Category name'']]. You will then see the category at the bottom of the page after you save the page or use Show preview.
* ''Take notes on paper or in Notepad while playing the game'', as it is a lot easier than playing back through whole portions of the game just to describe something you didn't before. You can, of course, refer to other guides to refresh your memory of the specifics, but remember not to copy directly from other guides.
* ''Don't bother using tabs or multiple spaces to align text.'' These don't appear in the final page or don't have the desired effect. If you want to lay something out in a specific way, use proper wiki formatting instead.
* ''Don't use more than a single blank line between sections.'' Any more than one will create obvious blank space in the saved page, which generally looks bad. This applies to the tops and bottoms of pages as well.
* ''Don't use ASCII artwork on StrategyWiki.'' Use images instead.
* ''Don't use any form of JIS (e.g. [[wp:JIS encoding|JIS encoding]] or [[wp:Shift-JIS|Shift-JIS]]) for Japanese.'' Instead, use normal Unicode characters (e.g. ゼルダの伝説). Modern browsers support both, but Unicode works immediately, whereas JIS requires the user to first manually change the character encoding in order for the characters to display correctly.
 
===Avoid spoilers===
Revealing main plot points such as the identity of a main boss at a point in the walkthrough earlier than that at which it occurs in the game is generally considered bad form. However, in some cases plot points are revealed by the game box, manual, or introduction. These are not considered spoilers as it is highly likely the player knows of them. An example would be the death of a central character in ''[[Grand Theft Auto Advance]]'' – this is stated right on the back of the box.
 
==Other considerations==
===Alternate titles===
If a game is known under other names, redirect those names to the most common one and mention them there, e.g. "'''Grappler''' (known as '''Bad Bros''' in Japan) is a beat-'em-up for the [[Sega Genesis]]". To help people find it using that other name, include the game's categories on the redirect page. This will make it show up in those categories under both names. Redirecting common misspellings (e.g. Megaman instead of [[Mega Man]]) is also a good idea, but because these involve a misspelling, not an alternate title, they do not need categories.
 
===Versions===
If a particular version of the game has changes (such as more/fewer characters or remixed levels) this should be explained on the appropriate pages. If a feature with an identical name is different enough in particular versions that it cannot be covered on the same page, disambiguate it at the top something like this:
:''For the [[Game Boy Advance]] stage see <nowiki>[[Game/Level 1 (GBA)]]</nowiki>.''


If the other version is significantly different enough that it should be covered separately, use a similar disambiguation on the cover page only and name the other guide with that system's common abbreviation.
To be systematic, so you don't miss any and others can easily verify they're all there, simply go down the fields of the infobox and add applicable categories. The following should be added if they're in the infobox (if they apply but aren't in the infobox, go ahead and add them!):
* Developers
* Publishers
* Genres
* Systems
* Distributors
* Engines
* Modes


==Formatting==
There are two fields which you don't have to worry about: release dates and series. In the case of the former, you should only be using [[:Category:Release date templates|release date templates]], and they all automatically categorize by year and date. The series field automatically inserts the series category through the infobox template. Finally, the [[:Category:Games|Games]] category is also added to the page, through the Header Nav template.
MediaWiki formatting is more involved than plain text, but much easier than HTML. See [[StrategyWiki:Guide/Wiki markup]] for more details.


==FAQ==
Some of the helpful templates used in the infobox will also add categories for you. These are the {{t|sys}}, {{t|co}} and {{t|series disambig}} templates. When using these templates, don't also add categories manually, as they're redundant. On the other hand, if you need to show system and/or company information without adding a category, use the {{t|sys/nocat}} and {{t|co/nocat}} templates. (There's no logical reason to use the {{t|series disambig}} template without also adding the category.)
===Can I use others' info?===
Yes, but always rewrite anything you use unless the source allows you to quote them (but a rewrite is still best). It's considered good form to credit the source, but by no means is it mandatory. Regardless of statements to the contrary, authors have no rights whatsoever to the information they are conveying, they only own their specific wording and presentation of that idea.


===What is "drivel"?===
Be sure to use Show preview to look at the categories being added before saving. Many of the wikilinks used in the infobox redirect to categories with different names. For instance [[[[Commodore 64]]]] redirects to [[:Category:Commodore 64/128]]. Categories themselves are never redirected, so you ''must'' put the exact category name in category tags.
"Drivel" is defined as unnecessary information or the wrong case. Saying "this character sucks" or "I usually go with the girl" is drivel. Because guides don't have fixed authors, using first-person wording is a bad idea. You could instead try wordings like "some players recommend" or "it is recommended". Similarly, while you might think a particular character or feature is bad or good others might not; instead, try to give good reasons why that particular thing isn't good (e.g. "his attack is good, but he has too little health to survive long against bosses").


===What about history pages?===
==Redirects==
No. MediaWiki keeps an automated history list, so you can enter things like "spellchecked" or "rewrote incorrect controls list" in the edit summary to easily keep a history list. As a general rule, use the talk page of the appropriate page for everything else. Such pages may not be part of the main guide nor may they be linked from them, but including one on the appropriate talk page is a useful way to find others interested in working on the game. Describing your role (e.g. "working on the food items list") will help others know what you're mainly working on.
In the case of main game pages, having many redirects to the page can be very helpful. Alternate names that don't have their own guides ''always'' get redirected. It's also a good idea to redirect common abbreviations and acronyms, such as [[[[Uncharted 2]]]] or [[[[FF7]]]]. Names '''not''' to redirect are misspellings. When making redirects, always be careful not to redirect something ambiguous to one guide over another. For instance, a general term like "tree" shouldn't necessarily redirect to [[Magical Tree]], [[Money Tree]] or [[The Tree Stones]]. It's also unnecessary to create redirects with uncapitalized versions of game names, as the wiki redirects on its own when all lowercase is used in the search box.


==Starting your guide==
In some cases, you'll need to categorize the redirect. In this case, you'll put categories below the redirect just like you do on the game main page. Redirects to main game pages only need categories if the game was released under that name by different companies, for different systems or at different times. Categorized redirects need all the same categories as the main game page, as well as [[:Category:Games]].
The main page of a game acts as a sort of "cover", serving as an introduction to the game. As a rule there won't be actual guide content on this page, but things like the storyline or description of acronyms/abbreviations to be used in the sub-pages might be a good idea.


If the cover doesn't already exist, use the [[#Creating the main page|"Main game page" preload button]] to populate it with all the needed templates. You can then edit the page and fill in the details. There should be a brief introduction describing the game (much like the start of a Wikipedia article). In fact, it is recommended that you copy the appropriate sections from the Wikipedia article if it exists, making sure to put the link to the article or its history page in the edit summary.
The purpose of categorized redirects is to get the redirect's name into the proper categories. For instance, if a game was released as Game A on the PlayStation and as Game B on the GameCube, and the main game page was going to reside at Game A, Game B would need the GameCube category on its redirect, or it wouldn't show up in the GameCube category. If Game A got the GameCube category, then Game A would show up when it was never released for GameCube under that name. To still display information about Game B on Game A's page, you can use {{t|sys/nocat}}, {{t|co/nocat}} and {{t|rd/nocat}}, which won't put those categories on Game A's page.


===Helping others find your guide===
==Single-page vs. multi-page==
To help other people find your new guide, you should place its main page in several categories. We already have categories set up for systems and genres. To add a page to a category, simply put the following into your page:
All StrategyWiki guides have either a single-page or multi-page layout. A platform game with a few levels may be simple enough to cover on a single page, while a strategy game or [[RPG]] will usually require many pages. The advantage of the wiki format is that any number of pages can be added and removed as the guide evolves from basic notes into a heavily detailed resource.


<nowiki>[[</nowiki>Category:''Category name'']]
===Single-page===
A single-page guide contains all its information on the main game page under multiple sections. In this case, the {{t|Continue Nav}} and {{t|ToC}} templates aren't used. The single-page layout covers absolutely everything on a single page. Such games might include:
* {{c|Racing}} games
* [[Puzzle]] games
* [[Platformer]]s
* Games with very simple gameplay
If the game can be feasibly covered in full on a single page, add the <tt>onepage=true</tt> variable to {{t|Header Nav}}; this will disable the [[#Walkthrough|Walkthrough]] and [[#Table of Contents|Table of Contents]] links that appear by default. [[Boxing]] is an example of a single-page guide.


Replace ''Category name'' with the category name you would like to use. To put your page into more than one category, just duplicate that line and change the name. Check out other guides to see the categories they use. Generally, the game should be in categories relating to its platforms, single/multiplayer support, publisher/developer, series, release dates… basically, the categories will be mostly the same as the information in the {{t|infobox}}. More information on categorization is available [[StrategyWiki:Guide/Categorization|here]].
===Multi-page===
Multi-page guides are most often used, as ubiquitous game elements such as controls, characters, cheat codes, etc. usually get their own pages. The guides for such games contain [[../Table of contents|tables of contents]] and multiple individual pages, all of which are sub-paged from the main game page like so: ''Game Name''/''Page name''. The multi-page layout starts with the main game page and can feature any number of sub-pages, each of which focuses on a single aspect of the game. Such games include:
* [[RPG]]s
* [[Adventure]]/[[Action-adventure]] games
* [[FPS]]s
* Games with many levels
If the game is too complex to feasibly be covered on a single page it will need a [[../Table of contents|table of contents]] linking to all the sub-pages it encompasses. [[Phoenix Wright: Ace Attorney]] is an example of a multi-page guide.


{{Footer Nav|game=StrategyWiki:Guide|prevpage=Walkthrough|nextpage=Researching more information}}
{{Footer Nav|game=StrategyWiki:Guide|prevpage=Walkthrough|nextpage=Table of contents}}

Revision as of 21:35, 26 January 2010

The first step to working on any guide is finding the guide on the wiki. After searching for the guide you want to work on, you may find that it doesn't yet exist. If that's the case, you should start out by creating the main page. See the scope policy first to make sure the game qualifies for inclusion on the wiki.

Naming

Note
Due to server configuration, the percent symbol (%) does not work correctly in page titles.

Each game gets its own page. When naming a guide, attempt to use the official name given by the game developer or publisher. In most cases, it's not a good idea to go by how the title is presented on the cover art, which uses artistic typesets and splits titles across multiple lines. If no official name is available, all words except for internal closed-class words should be capitalized.

Disambiguation

If there are multiple games with the same name that require different guides, the first release that was given the name should get the title. To help users find guides for other games with the same or similar names, disambiguation links should be added to the front page, with one blank line separating them from the end of the infobox. These links should either point to a series category which contains all the relevant guides using the {{series disambig}} template, or directly to each game using the {{game disambig}} template). For example, the Super Punch-Out!! page has a link at the top to the SNES version, and the Batman page has a link to the Batman category.

For games with the same title that are not the original, titles are disambiguated by following them with the game's system, year or other identifying characteristic in parentheses. In the case of simultaneous releases of different games with the same title, the first guide to be written gets the main title and any guides that follow will be disambiguated. Another occurrence may be a game that is released under two different names in different regions or for different consoles. In this case, the main title also goes to whichever guide is started first. The alternate name would then be redirected to the main game so that anyone searching for it would end up in the right place.

Exceptions to the above rule exist for games that became popular under a certain name or were originally released with a non-English title. If the game was released under multiple names, it is common practice to use the name most known globally. If there is a tie, it is up to the discretion of the guide's original writer. As an English wiki, English titles take precedence over foreign ones. Common examples are games released first in Japan, which get the English title for their guides here.

Article disambiguation can be complicated, so when in doubt, bring candidates for disambiguation to the attention of other editors and admin by posting in the staff lounge.

Versions

If a particular version of the game has changes (such as more/fewer characters or remixed levels) this should be explained on the appropriate pages. However, if a game is substantially different from other versions, it may warrant having its own guide, in which case it would use the standard disambiguation in its title. In general, combining guides should be tried first to avoid duplication of effort.

It is also possible to share the guide up to a certain point, then put any extra information on the guide to which it applies. See the Table of contents page for how to use the {{subtoc}} to accomplish this.

Page creation

Use the "Main game page" button to start a new main page.

There are many ways to get to the page creation screen:

  1. Search box: Put the name of the game in the search box and press "Go" or "Search". If the game doesn't exist, you'll see a red link to it at the top of the results page where it says "You searched for Your Game". If you pressed "Go", there will also be a link under the "No page title matches" section, and the link will say "create this page".
  2. Address bar: You can type the URL of the page you want to create directly into your browser's address bar by putting in http://strategywiki.org/wiki/Your Game. This takes you to a splash screen letting you know the page doesn't exist. Click the link that says "edit this page" to create it.
  3. Red link: Any time you see a red link on the wiki, it means the page being linked to doesn't exist. If you find a link to the main page you want to create, it will take you directly to the editing screen where you can begin to create the page.

Setting up the main page for a new guide has been simplified with the use of the preload buttons above the edit box. Simply click on the "Main game page" button to be given a basic layout, then just fill in the blanks.

Content

The main page of a guide should be set up as contained in the main page pre-load template, with the following in this order:

  1. Any tags, such as {{future}}, {{stub}}, etc.
  2. The {{Header Nav}}.
  3. An {{infobox}}.
  4. Any disambiguation templates, such as {{game disambig}} or {{series disambig}}.
  5. The {{marquee}} template for arcade games with a marquee image.
  6. Introduction section without a heading. It should be a paragraph or so in length and provide a general introduction to the game and its development. The first occurrence of the game name should be emboldened using ''', and the {{nihongo}} template should be used to add Japanese text where applicable. The first occurrences of items such as dates, systems, companies or other games should be linked.
  7. {{Continue Nav}}
  8. A short story or gameplay section, also without a heading. This section is not meant to be comprehensive, but should give a broad overview of the story or gameplay, or contain the relevant backstory for the game.
  9. An optional <gallery> of alternate box art, game flyers, etc.
  10. {{ToC}}.
  11. An optional external links (==External links==) section. See the external links policy for information on appropriate content for this section.
  12. The series navigation template, if one exists. These are in the form of {{Series Name}}.
  13. {{DEFAULTSORT:}} where applicable.
  14. Categories located at the bottom. See Categorization for more information.

The infobox

For more details on the infobox template, see Template:Infobox.

Some fields in the infobox are mandatory, and some are optional. In general, the more information you can provide, the better. If any mandatory fields are missing, the page will automatically be added to Category:Pages needing an infobox. Optional fields can either be left blank or removed entirely. Whenever possible, use a simple wikilink (i.e. [[Page name]]). Most fields link to categories, and the normal link usually redirects to the category page. If it doesn't, use {{c|Page name}} to link directly to the category.

Mandatory fields
  • title: Automatically filled in when using the "Main game page" preload, but you may need to adjust it if the page title contains disambiguation.
  • developer: Add links to developers if they are companies. For an individual, just put the person's name in plain text.
  • publisher: Add links to publishers if they are companies. For an individual, just put the person's name in plain text.
  • released: Using release date templates, add release dates by region. The minimum amount of information is the year of release.
  • genre: Add links to applicable genres.
  • systems: Add links to all systems for which the game was produced. Systems are actual hardware on which the game is played. For digital distribution, e.g. WiiWare or PlayStation Network, use the distributor field.
Optional fields
  • image: Put cover art here for console releases, arcade flyers for arcade games, or logos for online games or games that weren't released in retail stores. The field takes the name of the file and its extension, i.e. Filename.ext.
  • distributor: If the game has been released on a digital distribution service (e.g. Steam, GameTap, etc.), put links to them here.
  • designer: Put the plain text name of the designer or designers. Do not put their specific jobs in parentheses afterward. Use the introduction paragraph to expand on the designers if need be.
  • engine: Add a link to the engine used by the game.
  • version: Add the latest version to this field. This is meant for games that get usually downloadable updates.
  • players: Add the number of players. Don't add the modes field if this one is used.
  • ratings: Using ratings templates, add any ratings the game has received from official organizations.
  • modes: Add links to any modes for the game. Don't add the players field if this one is used.
  • media: Put any non-standard media on which the game can be played here. Don't add standard media here – a player would know that Nintendo 64 games come on a cartridge, for example.
  • input: Put any non-standard input here, such as alternate controls and accessories. Don't add standard inputs here – a player would know that computers use keyboards and the PlayStation 2 uses a controller.
  • requirements: Using the {{pcreq}} template, add relevant software and hardware considerations for computer games.
  • website: If there is an official website, the URL goes here in the form of [http://www.gamepage.com Official site]. This field is not for links to forums or retailers, but can be used for the original page where a flash game or online game is played.
  • expansion: If there are expansions to the game, list links to them here separated by <br /> tags.
  • series: If the game belongs to a series of games, put the series name here not inside a wikilink – this field is linked automatically.
  • preceded by: If the game is following a previous one from the same series, put a link to the previous one here.
  • followed by: If the game comes before a later one from the same series, put a link to the next one here.
Helpful templates
  • {{sys}}: Use this template to separate fields by system. For instance, if a game was released at different times on two separate systems, you would use {{sys|System one}} then the release dates for that system, followed by {{sys|System two}} then the second system's release dates.
  • {{co}}: Use this template to show which company developed or published the game for a particular system or region.
  • {{pcreq}}: Use this template in the requirements field to show nicely formatted requirements for computer games.
  • {{c}}: Use this template to link directly to categories when a plain wikilink doesn't get there. For example [[Racing]] goes to a guide page, while {{c|Racing}} goes to the category.
  • {{collapsible list}}: Use this template for overly long fields, such as release dates, ratings or requirements when they create too much whitespace on the page.
  • {{sys/nocat}}, {{co/nocat}} and {{rd/nocat}}: Use these templates to show information for systems, companies and release dates, respectively, while not automatically categorizing the page. Useful when there is a categorized redirect to the page.

Text

Unlike in individual guide pages, when writing the lead and plot synopsis for a main game page, use a third-person voice and include links to other pages on the wiki. This means you should refer to a "player" instead of saying "you", and link to the first instance of companies, dates, other games, etc. All links use no extra formatting, meaning don't use italics or bold when linking to other games.

Each page should start out with a lead, which immediately follows the {{infobox}} and any optional templates, such as {{game disambig}} or {{marquee}}. The subject of the article should be mentioned in bold text (not bold and italicised text as on Wikipedia) in the first sentence of the introduction. It is also important to list any alternate names in bold, as those names should redirect to the page and need to be easily identified by anyone who was searching by them. Use the {{nihongo}} template to format the addition of a Japanese title and include a link to Wikipedia's help page on Japanese.

The first paragraph clearly explains the history and development of the game, much of which is simply a written version of what is contained in the infobox. If there is anything notable or unusual about the production of the game, or you can provide a higher level of detail than the infobox, this is the place to put it. The information in the lead is mainly for meta information on the game, meaning very little or nothing about gameplay or plot.

The next section of writing, separated from the lead by the {{Continue Nav}}, is for a plot synopsis or overview on the game's mechanics. This section should include no spoilers, and is meant to inform readers who may have no idea what the game is about. This is not the place to divulge what happens in the game, but merely information on the game's "universe" or backstory so that a reader can understand what the game is about.

Images

Box artwork goes in the infobox, and should be at least 250px wide to prevent stretching. Also ensure that the cover image includes no watermarks, no borders and no "pending" rating symbols. Box art should also present a directly faced image, meaning it shouldn't be a 3-D box shown at an angle. For games which are unreleased, use Image:Future box art.png in the infobox. Game logos and artwork are not acceptable substitutes for box artwork when a box for the game exists. If the game was never released in physical form, or never in a box, make sure the artwork chosen is official – either a logo, welcome screen or start screen. For games that are released on multiple systems, it is unimportant which version of the cover you use, as long as the actual artwork is the same. This means you can use the Xbox 360, PlayStation 3 or Windows version of the cover, as long as the only differences are logos and symbols on top of the artwork. When this is the case, do not upload multiple versions.

For extra images not being used in the infobox, include them in a <gallery> between the plot synopsis and the {{ToC}} template. Images to include here are actual alternative covers (meaning the art is different, not the systems/developers/ratings/etc.), flyers, screenshots, or other interesting images. Don't go overboard with these, as they still need to add something to the reader's understanding of the game to comply with fair use.

Categories

For more details on categorizing, see StrategyWiki:Guide/Categorization.

Most of the categories by which a main game page should be categorized, are found in the infobox. Categories go below all the visible content on the page, usually just below the {{ToC}} template or series nav, if it exists. Categories are added by putting [[Category:Category name]]. You will then see the category at the bottom of the page after you save the page or use Show preview.

To be systematic, so you don't miss any and others can easily verify they're all there, simply go down the fields of the infobox and add applicable categories. The following should be added if they're in the infobox (if they apply but aren't in the infobox, go ahead and add them!):

  • Developers
  • Publishers
  • Genres
  • Systems
  • Distributors
  • Engines
  • Modes

There are two fields which you don't have to worry about: release dates and series. In the case of the former, you should only be using release date templates, and they all automatically categorize by year and date. The series field automatically inserts the series category through the infobox template. Finally, the Games category is also added to the page, through the Header Nav template.

Some of the helpful templates used in the infobox will also add categories for you. These are the {{sys}}, {{co}} and {{series disambig}} templates. When using these templates, don't also add categories manually, as they're redundant. On the other hand, if you need to show system and/or company information without adding a category, use the {{sys/nocat}} and {{co/nocat}} templates. (There's no logical reason to use the {{series disambig}} template without also adding the category.)

Be sure to use Show preview to look at the categories being added before saving. Many of the wikilinks used in the infobox redirect to categories with different names. For instance [[Commodore 64]] redirects to Category:Commodore 64/128. Categories themselves are never redirected, so you must put the exact category name in category tags.

Redirects

In the case of main game pages, having many redirects to the page can be very helpful. Alternate names that don't have their own guides always get redirected. It's also a good idea to redirect common abbreviations and acronyms, such as [[Uncharted 2]] or [[FF7]]. Names not to redirect are misspellings. When making redirects, always be careful not to redirect something ambiguous to one guide over another. For instance, a general term like "tree" shouldn't necessarily redirect to Magical Tree, Money Tree or The Tree Stones. It's also unnecessary to create redirects with uncapitalized versions of game names, as the wiki redirects on its own when all lowercase is used in the search box.

In some cases, you'll need to categorize the redirect. In this case, you'll put categories below the redirect just like you do on the game main page. Redirects to main game pages only need categories if the game was released under that name by different companies, for different systems or at different times. Categorized redirects need all the same categories as the main game page, as well as Category:Games.

The purpose of categorized redirects is to get the redirect's name into the proper categories. For instance, if a game was released as Game A on the PlayStation and as Game B on the GameCube, and the main game page was going to reside at Game A, Game B would need the GameCube category on its redirect, or it wouldn't show up in the GameCube category. If Game A got the GameCube category, then Game A would show up when it was never released for GameCube under that name. To still display information about Game B on Game A's page, you can use {{sys/nocat}}, {{co/nocat}} and {{rd/nocat}}, which won't put those categories on Game A's page.

Single-page vs. multi-page

All StrategyWiki guides have either a single-page or multi-page layout. A platform game with a few levels may be simple enough to cover on a single page, while a strategy game or RPG will usually require many pages. The advantage of the wiki format is that any number of pages can be added and removed as the guide evolves from basic notes into a heavily detailed resource.

Single-page

A single-page guide contains all its information on the main game page under multiple sections. In this case, the {{Continue Nav}} and {{ToC}} templates aren't used. The single-page layout covers absolutely everything on a single page. Such games might include:

If the game can be feasibly covered in full on a single page, add the onepage=true variable to {{Header Nav}}; this will disable the Walkthrough and Table of Contents links that appear by default. Boxing is an example of a single-page guide.

Multi-page

Multi-page guides are most often used, as ubiquitous game elements such as controls, characters, cheat codes, etc. usually get their own pages. The guides for such games contain tables of contents and multiple individual pages, all of which are sub-paged from the main game page like so: Game Name/Page name. The multi-page layout starts with the main game page and can feature any number of sub-pages, each of which focuses on a single aspect of the game. Such games include:

If the game is too complex to feasibly be covered on a single page it will need a table of contents linking to all the sub-pages it encompasses. Phoenix Wright: Ace Attorney is an example of a multi-page guide.