This page covers more in-depth the layout of pages in different namespaces. It adds to the guidelines set on the manual of style, so please read it first if you have not already. If you would like to propose changes to this guideline, you can do so here.
This page will not guide you on how to do any of the stuff mentioned here. To learn about that, refer to our wikitext guide.
(Main) namespace
Page layout will differ from page to page according to the category of the article. If it is a page that covers an ample group of items, you can freestyle. Individual articles, though, may contain the following sections:
| Title | Description | Header? |
|---|---|---|
| Notices | Templates which will tell the reader any relevant information before reading the article. In general, they talk about the current state of the page. A list of them can be found at Category:Notice templates. | No |
| Infobox | Template which display data about the article. In general, it displays some data characteristic of the category it represents. A list of them can be found at Category:Infobox templates. | No |
| Introduction | A small but informative paragraph that says a little about what the reader is about to read. It should follow the rules estabilished on the Content section of this page. | No |
| Page Content | The content here is determined by the category of the page. Currently, in order to get a grasp of what to add here, you need to see pages of similar nature to the one you're editing. | Yes? |
| Appearance | What the thing in question looks like. Not necessary if self-explanatory or without the need of in-depth analysis. | Yes |
| Trivia | A section divised for you to add information about the topic that is mostly obscure or hard to get by normal gameplay. Not necessary if there isn't much to say. | Yes |
| See Also | A little section that lists other pages for further reading. Not necessary in case there aren't pages that can be added here. | Yes |
| Navboxes | Templates which link to pages of same category to the page currently being read. A list of them can be found at Category:Navbox templates. | No |
Categories
In it, you should add a brief description about what the category is. In case it is added by a template, do note it with the help of the {{T}} template. You should also categorize it if possible, just because that makes everyone's life easier when locating articles.
Templates
<includeonly>
This section has the code of the template when transcluding it to a page (by adding {{Template name}}). It may break any rules estabilished on the manual of style, granted with good reason. You may start this section by adding <includeonly>, and may end it by adding </includeonly>.
<noinclude>
This section is the code when seeing the page of the template. As a rule of thumb, you should put the template and its documentation in different pages, but in case there isn't much to document, you can put them in the same page. In case you are writing the documentation in a separate page, the noinclude section should only have the {{Documentation}} template. You may start this section by adding <includeonly>, and may end it by adding </includeonly>.
Documentation
The documentation should be written in the /doc subpage of the template (like Template:Stub/doc). It should have these following sections:
Usage
A brief description of the template and when to use it.
Parameters
An article table that contains details about all the parameters. Every parameter in the table should have the following properties, though you may add more of them:
- Parameter: the name of the parameter
- Description: a brief description of the parameter
- Default: the value of the parameter when nothing is inputted
An example table would look like this:
| Parameter | Description | Default |
|---|---|---|
1
|
Today's current day | Monday |
2
|
Today's current month | June |
3
|
Today's current year | 2025 |
Sample Output
A little sample showing how to use the template. It should have the template code embedded in a <pre> element, and the template output alongside it.