Pokémon GO Wiki:Styling Guide

There are some style guidelines to follow when editing or creating new pages for. All editors are expected to agree and follow this guidelines when editing in order to ensure content consistency and quality in all 's articles.

General Guidelines

 * Try to use a simple register as you write.
 * People from all around the world are probably going to read this wiki, and their first language is not always English. Do not use colloquialisms.


 * Try to be as impersonal as possible.
 * Remember you are giving out information, not your own point of view. Refrain from writing biased walls of text about your experience with something in the article, do that in blogs or in the comment section at the bottom of the page instead.


 * Humor in the content section is not tolerated.
 * Avoid being funny or witty as you write, people are here for pieces of information, not for a laugh.


 * Avoid inserting unconfirmed content or any speculations.
 * If an unconfirmed content is significant that it has to be shown to the public for testing, please state so clearly by adding  next to the text.


 * Link words to articles.
 * If a word in an article has its own page, link it to the page. However, that page should not be linked more than once in a particular section of the page, over-linking a page is unnecessary if the linked page can be viewed at least once on a single section.


 * Be professional – use formal writing rules.
 * Avoid contractions like "don't" and "isn't". Use the full spelling.


 * Correct and revise.
 * Feel free to correct spelling and grammar mistakes if you see any, and help expanding Stub Articles and Outdated Articles. Editorial help is always needed!

Using Source Mode
Source mode is generally preferred over Visual mode when editing on this wiki. Editors can switch to Source mode by switching between "Visual" and "Source" tabs on the top of the Editor Window.

Source mode enable the use of features such as Templates, commenting, easier formatting and most importantly, the browser's spell check. If Visual mode is used, unnecessary formatting elements would sometimes appear, which contributes nothing but distorts the main content.

You can always use the Preview button on the top right corner of the Editor Window before you Publish.

Here are some basic tips in using Wiki markup and HTML tags in Source mode:

Headers are section titles used throughout any page with more than one attributes.
 * Headers

Headers can be added by typing  in source mode.

If smaller headers are needed, such as a sub section in one of the sections in the same page, editors can type. Smaller headers can be created by adding more "=", with a maximum of five.

If a specific word refers to a page anywhere in this, such as Bulbasaur editors can type brackets, like  in Source mode. No additional parameters are required.
 * Links

Note that this feature is case sensitive. If the word "bulbasaur" has to be used, then typing  will produce bulbasaur. Note that the link links to the same page but appears without the uppercase "B".

If a word has to link to a specific section in a page, editors can type, which produces Attacks of Bulbasaur. The "#" defines the section(header) name.

Some pages with a namespace such as Category:Attacks or File:Substitute.png cannot be linked with the above method. Editors can link to these pages by typing. Otherwise typing without the ":" will categorize the page into the linked category or display linked file.

For any links that link to external sites, type, which produces Pokémon GO.

Editors can type bold text by typing, and Italic text by typing   in Source mode.
 * Bold and Italic

Commenting is creating hidden text that only editors can see in source mode.
 * Commenting

Usually this is used for embedding instructions when working with layouts, or hiding a large amount of text that is subjected for deletion.

Editors can comment out a line of text by putting.

Bullets can be added by typing  in front of a line of text. Typing  will produce a first-degree "sub-bullet" and so on.
 * Bullet lists

generates this: However, it is preferred not to create second or higher degree sub-bullets in the articles for aesthetic and readability reasons.
 * Bullet 1
 * Sub-bullet 1-1
 * Bullet 2
 * Sub-bullet 2-1
 * Sub-bullet 2-2
 * Sub-bullet 2-2-1
 * Sub-bullet 2-2-2
 * Sub-bullet 2-2-3
 * Sub-bullet 2-3
 * Bullet 3
 * Bullet 4
 * Bullet 1
 * Sub-bullet 1-1
 * Bullet 2
 * Sub-bullet 2-1
 * Sub-bullet 2-2
 * Sub-bullet 2-2-1
 * Sub-bullet 2-2-2
 * Sub-bullet 2-2-3
 * Sub-bullet 2-3
 * Bullet 3
 * Bullet 4

Ordered lists can be created with  in front of a line of text. Typing  will produce a first-degree sub-ordered list item and so on. It can be combined with bullet lists.
 * Ordered lists

generates this: Similarly to bullet lists it is preferred not to create second or higher degree sub list items.
 * One
 * Two
 * 1) Two-One
 * 2) Two-Two
 * 3) Three
 * 4) *Three-Bullet 1
 * 5) *Three-Bullet 2
 * One
 * Two
 * 1) Two-One
 * 2) Two-Two
 * 3) Three
 * 4) *Three-Bullet 1
 * 5) *Three-Bullet 2

Typing  or   at the end of any text will produce a line break like this.
 * Line Break

If you type  in front of the line, the description-term will be created. If you type  description-information will be created.
 * Description list


 * Kanto
 * Bulbasaur, Squirtle, Charmander


 * Unova
 * Snivy, Tepig, Oshawott

gives:
 * Kanto
 * Bulbasaur, Squirtle, Charmander
 * Unova
 * Snivy, Tepig, Oshawott

Creating New Pages
Pages are considered as formal content of the Wiki. The purpose of a page is to deliver information about Pokémon GO to the public in a detailed, accurate, formal and unbiased way. Nothing more, nothing less. Pages showcasing defects, bugs, or problems with Pokémon GO are not permitted to be made into pages and must instead be contained in user blogs if general, or in the 'bugs' section in already existent articles.

When new contents are being introduced to the game, new pages should be created. Before creating one, editors should familiarize the proper layout, must make sure there are no duplicated pages that have already been created, and the content are relevant to the canon of Pokémon GO.

Page Styling
Manny articles on this wiki uses layout respective to their contents, especially articles on game elements. Such articles share common format of having:
 * an image at top of the page, or in the top-right corner
 * first paragraph explaining basics of the article's topic
 * at the bottom of page sections in this order: Gallery, Trivia, References and External links.

Other articles have set layouts depending on their topic.
 * Layout of Pokémon article, the best examples: Bulbasaur, Ivysaur and Venusaur.
 * Layout of Attack article, the best examples: Splash, Body Slam and Parabolic Charge
 * Layout of Type article, the best examples: Grass, Fire and Water
 * Layout of Event article, the best examples: Dragon Week, Enigma Week and Unova Week.

When in doubt, feel free to refer to existing pages or contact an Admin.

Using Templates
Using templates are a great way to save time and hassle when editing. Most pages in are associated with a particular template, and it is often mandatory to use the appropriate template, so that pages on the same topic will have a unified format and can be edited easily in the future.

Templates can be edited in both Visual Editor and by switching to Source mode, however it is recommended to use Source Mode in which templates exist in the following format:

Editors can consult the template page by searching the template name, which in this case is Template:Infobox/Pokémon. Template pages often include crucial information, documentation and usage that editors need to know about before using them.

Some templates do not require any inputs, such as Delete, Outdated, etc. These are often used as public service announcement templates.

Infoboxes
These are the most common and recognisable templates on wiki projects that serve to give crucial information on article's topic. They are in most cases placed at the very beginning of articles and can be only preceded by notice templates and top navigation bars.

We have following infoboxes:
 * Infobox/Pokémon
 * Infobox/Attack
 * Infobox/Type
 * Infobox/Event
 * Infobox/Product

Some articles need more than one infobox and then we display them as a tabber using Multi Infobox template. For example:

Navboxes
Navboxes are the second most common kind of templates on wiki projects, these ones are used at the very bottom of the pages to give a shortcut navigation to the other articles on the directly similar topic. They shouldn't be followed by anything but interlanguage links.

We have following navboxes:
 * Navbox – general use navbox that serve as base for other navboxes
 * Navbox/Pokémon – navbox for articles in Pokémon category
 * Navbox/Attacks – navbox for articles in Attacks category
 * Navbox/Types – navbox for articles in Types category
 * Navbox/Events – navbox for articles in Events category
 * Navbox/Items – navbox for articles in Items category

Lists Templates
Following are frequently used design, data or content templates in articles of our wiki to create various listings, including features lists in Events articles. For all lists-related templates, see: category:Lists-related templates. Read their documentations to know how to properly use them and where.
 * I – general Icon link template – to display any page link with the associated icon image next to it
 * TI – general Type Icon link template – customizable way to link types with associated icon
 * P – general Pokémon list item template
 * PH – general header list template
 * PS – general Shiny Pokémon list item template
 * PE – general Pokémon Egg hatchling list item template
 * RB – Raid Boss list item template
 * RE – Region-excslusive Pokémon list item template
 * FT – Field Research task item template
 * ST – set of Special or Timed Research tasks item template
 * AI – Avatar item list template
 * SI – Shop offer list item template
 * Attack – Attack list item template

For proper displaying of most of these templates we are using additional box element: CONTENT It has a couple of customisation options, when using appropriate classes such as:
 * color backgrounds:
 * picture backgrounds:
 * – uses this file as a background
 * – uses same background file as, but is colored green
 * – uses same background file as, but is colored orange
 * – uses same background file as, but is colored pink
 * – uses same background file as, but is colored purple
 * – uses this file as a background
 * – uses this file as a background
 * widths:
 * – makes the whole list container as wide as the content inside
 * – makes the whole list container 100% of the page wide
 * – makes the whole list container 80% of the page wide
 * – makes the whole list container 70% of the page wide
 * – makes the whole list container 50% of the page wide
 * widths:
 * – makes the whole list container as wide as the content inside
 * – makes the whole list container 100% of the page wide
 * – makes the whole list container 80% of the page wide
 * – makes the whole list container 70% of the page wide
 * – makes the whole list container 50% of the page wide

However, to list event features and bonuses on their particular pages, we use BI – bonus item template with this box element: CONTENT

Maintenance Templates

 * Delete If you see a page that is inappropriate or irrelevant to, and should be subjected for deletion, insert this template on the top of the page.
 * Outdated If you see a page that is incomplete and can use some editing, insert this template on the top of the page.
 * Stub If you see a page that only consists of two lines of text or less, insert this template on the top of the page.
 * CleanUp If you see a section or page that could use some clean up on grammar and content, insert this template in the appropriate area.
 * Cite If you see a statement that needs confirmation, insert this template in the appropriate area.
 * Main If the section refers to another article for more details, insert this template in the appropriate area and attach the target page name using the correct format.

Magic Words
Aside from regular templates there are also Magic words that can be used on this wiki. These are most common ones:
 * – removes any Table of Content (TOC) in the page.
 * – forces Table of Content (TOC) to appear even if there are only few sections.
 * – removes any clickable "Edit" links next to headers.
 * – outputs the name of this wiki community.
 * – outputs the name of the page the word is placed on.
 * – changes the displayed title at the top of the article.

Using Tables
If there is no respective template for an information to be displayed on the page, and such information should be displayed in a uniform table there is possibility to use a special table designed for general use on this wiki. Its class is  and it has various customisation options for itself and its headers, rows and cells.

Basics
To generate a table in Wiki markup there are several character combinations that are very similar to using templates in source mode editor. Each of this character-combination has to begin from the new line after hard line-break (Enter key)


 * Markups
 * Table begins with  and ends with.
 * Each row of the table begins with  and it does not require any character to end it.
 * To create data cell add  (pipe) at the beginning of the line, you can also input custom classes, styles or attributes to it and then use another   to begin inputting content to the cell
 * To create header which works similarly to the data cell, add  at the beginning of the line.


 * Attributes
 * Two most common and useful attributes in the table building are  and , # is the number of rows or columns that the header or data cell should expand into.
 * There is also  attribute which defines the width of the header or data cell, # can be either static value in pixels (e.g. 200px) or value relative to the table's full lenght in percents (e.g. 25%).

Classes
Aside from general attributes for basic tables there are plenty classes that can be added to the table with core class
 * Table
 * These classes can be added to the table itself:


 * – all text is centered in the table
 * – data-cells are underlined in all rows except the last one
 * – width of table is 100% of the article or parent element
 * – width of table is 90% of the article or parent element
 * – width of table is 80% of the article or parent element
 * – width of table is 50% of the article or parent element
 * – width of table is reduced to fit its content
 * – text in first data-cell in each column is aligned to the left
 * – text in first data-cell in each column is aligned to the center
 * – text in first data-cell in each column is aligned to the right
 * – text in last data-cell in each column is aligned to the left
 * – text in last data-cell in each column is aligned to the center
 * – text in last data-cell in each column is aligned to the right
 * – text in first data-cell in each column is italic
 * – text in first data-cell in each column is bold
 * – text in last data-cell in each column is italic
 * – text in last data-cell in each column is bold
 * – dark theme is applied to the table
 * – headers in table have green background
 * – headers in table have orange background
 * – headers in table have pink background
 * – headers in table have purple background
 * Header cells
 * These classes can be added to table header cells:


 * – smaller size of the font
 * – yet smaller size of the font
 * – text in the header cell is aligned to center
 * – text in the header cell is aligned to left
 * – text in the header cell is aligned to right
 * – all corners of header cell are rounded
 * – right corners of header cell are rounded
 * – left corners of header cell are rounded
 * – top-left corner of header cell is rounded
 * – bottom-left corner of header cell is rounded
 * – top-right corner of header cell is rounded
 * – bottom-right corner of header cell is rounded
 * – header cell does not have a color background
 * Table rows and data cells
 * These classes can be applied to particular data cells or whole table row which affects all data cells in it:


 * – text is aligned to center
 * – text is aligned to left
 * – text is aligned to right
 * – underlined cells

Examples
These are examples featuring most of the features in these tables. gives:

gives:

gives:

Images and Videos
Screenshots and gameplays are welcomed. Generally, if your uploaded media refers to a specific line of text in an article, make sure to add it next to the related text. For any media that are for showcasing only, make sure to add it in the Media section of the page.

Plain images are generally preferred over Thumbnails. However thumbnails can be used if a caption is really necessary.

To add an image or a video, upload it to the Wikia database via the contribute button on the top right corner of any page, and then insert the following syntax in the appropriate page: Note that the parameters  and   are used in thumbnails only, and should be omitted in most media;   defines the position, in which   and   can also be used;   defines the widths of the media. If the height needed to be defined instead of widths, insert  in place of widths.

If too much media are added to a page there should be a Gallery section added and following gallery code used: Because of the  tag there is no need for extra attributes or parameters to the gallery, except for   or   if you want to set widths or heights of displayed images and   or   to set number of images in a row of a gallery. Aside from regular  there can be also additional class   added to make displayed gallery have a light theme. To set width of gallery you can use classes such as,  ,  ,   or.

Conclusion
Please feel free to take a peek on other pages for editing guidelines. Use your Profile Page as a testing ground or sandbox. Create testpages under your username, Special:Mypage/testpage (testpage can be any word).

If you have any questions or want to go beyond simple editing such as creating templates or even a page overhaul please don't hesitate to contact an Administrators.

Have fun editing Trainers!