Wikitext is the main markup language used on FANDOM. Although it is not a substitute for HTML, and more of a complement to it, most things you can do with HTML are implemented in some form as wikitext - which is far more readable, making its use preferable over HTML. A deeper control over it can be granted by using the source editor, and this guide will assume that is your editor of choice.
The presence of any of the wikitext below is not to be meant as an endorsement to use it in article pages. The purpose of this page is to educate you on how to use wikitext so that you can have a deeper understanding of it. If you'd like a thorough list of what is recommended and what is not on what scenarios, refer to the manual of style. In general, though, anything is allowed on templates.
Finding Templates
Wikitext may be easier to use than HTML, but by itself, it cannot do a lot of what HTML can. The solution is not to use HTML directly, but rather use templates. They take some parameters and output some HTML. Using them makes it much easier for other editors to understand what your code means.
Templates are categorized in a couple main categories, namely:
- Data templates, that show some sort of information.
- Design templates, meant to facilitate creating designs.
- Infobox templates, meant to facilitate creating infoboxes.
- Notice templates, that show messages to the reader about a page.
- Navbox templates, that link pages related to one another.
Search what you're looking for or, if you still can't find one, ask someone else to create them for you.
Text Formatting
- Expanded from Help:Wikitext
| Description | Code | Output |
|---|---|---|
| Italicized text | ''Italic''
|
Italic |
| Bolded text | '''Bold'''
|
Bold |
| Underlined text | <u>Underline</u>
|
Underline |
| Strikethrough text | <s>Strikethrough</s>
|
|
| Superscript | 1<sup>st</sup>
|
1st |
| Subscript | O<sub>2</sub>
|
O2 |
| Small Text | Small <small>text</small>
|
Small text |
| Big Text | Big <big>text</big>
|
Big text |
| Internal link | [[Taming.io Wiki]]
|
Taming.io Wiki Not Taming.io Wiki haha |
| Interwiki link | [[w:c:starwars:Wookie]]
|
w:c:starwars:Wookie |
| Category linking | Adds the category to the page: [[Category:Guidelines]]Links the category in the text: |
Category:Guidelines |
| External link (to other websites) |
[https://www.example.org]
|
[1] |
| Redirect to another page | #REDIRECT [[Taming.io Wiki]]
|
Sample: Home |
| Cite link | <cite>https://www.fandom.com/</cite>
|
https://www.fandom.com/ |
| Sign your posts on talk pages (username only) | ~~~ (3 tildes)
|
Williek11 (talk) |
| Sign your posts on talk pages | ~~~~ (4 tildes)
|
Williek11 (talk) 18:52, 15 June 2025 (UTC) |
| Insert the current date and time (UTC). Generally only used on talk pages. | ~~~~~ (5 tildes)
|
18:52, 15 June 2025 (UTC) |
| Display wikitext code | <nowiki>'''This is not bold 🤔🤔🤔'''</nowiki>
|
'''This is not bold 🤔🤔🤔''' |
| Display text as source code | <code>Source Code</code>
|
Source Code
|
| Description | Code | Output |
|---|---|---|
| Headings (Skip level 1; it's used for the page name.) |
|
Level 2
Level 3
Level 4
Level 5
Level 6
|
| List heading | ;Heading
|
|
| Indented paragraph or line | No indent
|
No indent
|
| Bullet list |
|
|
| Numbered list |
|
|
| Mixed list |
|
|
| Preformatted text with working wikitext | [[Taming.io Wiki]] (note space at start)
|
Taming.io Wiki |
| Preformatted text that shows underlying wikitext | <pre>[[Taming.io Wiki]]</pre>
|
[[Taming.io Wiki]] |
| Syntax Highlighting | <syntaxhighlight lang="javascript">
while (true) {
console.log("yes")
}
</syntaxhighlight>
|
while (true) {
console.log("yes")
}
|
Transclusion and variables
| Description | Code | Output |
|---|---|---|
| Transcluding templates (full list) | {{Normal}} - calls template from Template:Normal
|
 Normal Type
|
| Transcluding pages (full list) | {{:Category:Taming.io Wiki}} - takes page from Category:Taming.io Wiki
|
This category page contains pages or categories intrisically related to the Taming.io Wiki. |
| Transcluding Lua modules | {{#invoke:String|join|Bark|Quack|Meow}} - calls module from Module:String, calls method join and passes arguments:
|
Bark, Quack and Meow |
Substituting expressions ({{<expression>}}) to wikitext upon re-editing the page
|
{{subst:Water}} - {{subst:#invoke:String|join|Bark|Quack|Meow}}
|
 Water Type - Bark, Quack and MeowSource code: |
| Magic Words (full list) | {{LOCALMONTHNAME}} {{LOCALDAY}} of {{LOCALYEAR}}
|
June 15 of 2025 |
| Parser Functions (full list) | {{#switch: {{CURRENTDOW}}
| 0 = It's Sunday!!! ☀️☀️☀️
| 1 = It's monday.
| 2 = It's tuesday today...
| 3 = It's the middle of the week!!!
| 4 = It's that other day after wednesday!
| 5 = Friday!!!!!
| 6 = Hohohohohoh! It's saturday!
}}
|
It's Sunday!!! ☀️☀️☀️ |
| Dynamic Page List 3; note that this a Mediawiki extension disabled by default. Documentation can be found in its page: Help:DynamicPageList. Use only as last resort. | <dpl>
category = Taming.io
</dpl>
|
|
| Variables; note that this a Mediawiki extension disabled by default. Documentation can be found in its page: Extension:Variables | {{#vardefine:DefaultText|This is default text.}}
{{#vardefine:Title|DefaultText variable:}}
;{{#var:Title}}:
:{{#var:DefaultText}}
|
|
| Reader's username; note that this is a site-wide enhancement, not standard wiki behavior. Documentation can be found in its page: InputUsername (This feature is supported on desktop, but will not be rendered at all on mobile devices.) | Hello {{USERNAME}}!
|
Hello Anonyomous Guy! |
| Countdown; note that this is a site-wide enhancement, not standard wiki behavior. Documentation can be found in its page: Countdown (This feature is supported on desktop, but will not be rendered at all on mobile devices.) | <span class="countdown">2022 started <span class="countdowndate">January 1 2022 00:00:00 UTC</span> ago.</span>
|
2022 started January 1 2022 00:00:00 ago. |
Tables
{| and |}
They start and end a wikitext table, respectively. Their HTML equivalent is <table><tbody> and </table></tbody>. In order to add attributes to the table node, you must add the attributes after the {|. It would look like this:
{| style = "width:100%" class = "generic-table"
...
|}
There are three classes with default styling in this wiki. Those are article-table, wikitable and fandom-table. Those look like this:
{| class = "wikitable"
|+ wikitable
! Animal !! Type !! Biome
|-
| Cow || {{Normal}} || Forest Biome
|-
| Black Cat || {{Spectrum}} || Dark Forest
|}
| Animal | Type | Biome |
|---|---|---|
| Cow | Normal Type |
Forest Biome |
| Black Cat |  Spectrum Type |
Dark Forest |
{| class = "article-table"
|+ article-table
! Animal !! Type !! Biome
|-
| Ice Golem || {{Ice}} || Winter Biome
|-
| Armadillo || {{Rock}} || Desert Biome
|}
| Animal | Type | Biome |
|---|---|---|
| Ice Golem |  Ice Type |
Winter Biome |
| Armadillo |  Rock Type |
Desert Biome |
{| class = "fandom-table"
|+ fandom-table
! Animal !! Type !! Biome
|-
| Cow || {{Normal}} || Forest Biome
|-
| Black Cat || {{Spectrum}} || Dark Forest
|}
| Animal | Type | Biome |
|---|---|---|
| Cow | Normal Type |
Forest Biome |
| Black Cat | Spectrum Type |
Dark Forest |
For wiki pages, you should always use the article-table. For other uses, such as user pages or talk pages, choose whichever you prefer.
|-
It will create a new row. Its HTML equivalent is <tr>. To add attributes to it, add them after |-.
{| class = "article-table"
| Row 1 Column 1 || Row 1 Column 2 || Row 1 Column 3
|- style = "background:#f0f8;font-weight:bold"
| Row 2 Column 1 || Row 2 Column 2 || Row 2 Column 3
|}
| Row 1 Column 1 | Row 1 Column 2 | Row 1 Column 3 |
| Row 2 Column 1 | Row 2 Column 2 | Row 2 Column 3 |
|+
It will create a table caption. Its HTML equivalent is <caption>. To add text to it, write it after the |+. To add attributes to it, you must add it after |+, and insert the text with a | prefix. It would look like this:
{| class = "article-table"
|+ style = "background:#0f08" | This is the caption of an article-table.
|}
! and !!
They will both create a table header. Their HTML equivalent is <th>. The only difference is that the ! only works on the start of a line, while !! works inline after another header. Here is what it means for source code:
{| class = "article-table"
! Cell 1 !! Cell 2 !! Cell 3
|}
{| class = "article-table"
! Cell 1
! Cell 2
! Cell 3
|}
... Are the same thing.
Inline cells should only be used in case they can fit in one line. In order to add attributes to these, you need to write the attributes after the ! and add a | prefix before the text. It would look like this:
{| class = "article-table"
! style = "background:#00f8" | Animal !! style = "background:#0f08" | Type !! style = "background:#f008" | Biome
|}
| Animal | Type | Biome |
|---|
| and ||
They will both create a table cell. Their HTML equivalent is <td>. The only difference is that the | only works on the start of a line, while || works inline after another cell. It's the same situation as !.
Inline cells should only be used in case they can fit in one line. In order to add attributes to these, you need to write the attributes after the | and add a | prefix before the text. It would look like this:
{| class = "article-table"
! Animal !! Type !! Biome
|- style = "font-weight:bold"
| style = "background:#f008" | Boar || style = "background:#0f08" | {{Rock}} || style = "background:#00f8" | Forest Biome
|- style = "font-weight:bold"
| style = "background:#f008" | Rabbit || style = "background:#0f08" | {{Plant}} || style = "background:#00f8" | Forest Biome
|}
| Animal | Type | Biome |
|---|---|---|
| Boar | Rock Type |
Forest Biome |
| Rabbit |  Plant Type |
Forest Biome |
Sorting
- Restructured and summarized from Help:Sorting
Tables can be made sortable, in the sense that each column can be alphabetically listed. See the following example:
{| class="article-table sortable"
! Fruit !! Price
|-
| Apples || £0.95
|-
| Oranges || £0.85
|-
| Pears || £1.15
|-
| Purple Mangosteen || £1.05
|}
| Fruit | Price |
|---|---|
| Apples | £0.95 |
| Oranges | £0.85 |
| Pears | £1.15 |
| Purple Mangosteen | £1.05 |
By adding the sortable class, you make the table alphabetically sortable, ascending or descending. Additionally, more fine-grained control can be earned by using the data-sort-value attribute on individual cells:
{| class="article-table sortable"
! Sword !! Damage
|-
| data-sort-value = "1" | Stone Sword
| 30 damage
|-
| data-sort-value = "2" | Golden Sword
| 34 damage
|-
| data-sort-value = "3" | Ruby Sword
| 37 damage
|-
| data-sort-value = "4" | Amethyst Sword
| 40 damage
|}
| Sword | Damage |
|---|---|
| Stone Sword | 30 damage |
| Golden Sword | 34 damage |
| Ruby Sword | 37 damage |
| Amethyst Sword | 40 damage |
Additionally, if you want to add a footer and don't want that to be sorted, you can add the sortbottom class to the row you want to keep there:
{| class="article-table sortable"
! Sword !! Damage
|-
| data-sort-value = "1" | Stone Sword
| 30 damage
|-
| data-sort-value = "2" | Golden Sword
| 34 damage
|-
| data-sort-value = "3" | Ruby Sword
| 37 damage
|-
| data-sort-value = "4" | Amethyst Sword
| 40 damage
|- class = "sortbottom"
! Average:
! 35 damage
|}
| Sword | Damage |
|---|---|
| Stone Sword | 30 damage |
| Golden Sword | 34 damage |
| Ruby Sword | 37 damage |
| Amethyst Sword | 40 damage |
| Average: | 35 damage |
Images
- Oversimplified from Help:Images
Rendering Images
The syntax to using images is the following:
[[File:filename.extension|<options>|<caption>]]
Where options can be zero or more of the following:
[[File:Badge-normal.png | 25px | link = Types]], where the link doesn't show when hovering: 
. Another thing is that the following options must not be capitalized, because capitalization could be ignored by the interpreter.| Title | Syntax | Description |
|---|---|---|
| Formatting | [[File:...|<format>]]
|
Can be border, frameless, frame (or framed) or thumb (or thumbnail). |
| Horizontal alignment | [[File:...|<alignment>]]
|
Can be left, right, center or none. If multiple are present, the first one will be used. |
| Vertical alignment | [[File:...|<alignment>]]
|
This will only work if the image is in inline display (will be displayed alongside text), which can be achieved by not specifying horizontal alignment. Can be baseline, sup, super, text-top, middle, bottom, text-bottom. If multiple are present, the first one will be used. |
| Link | [[File:...|link=<text>]]
|
Supports any type of link; external, interwiki and internal. |
| ||
| Text when image fails to load | [[File:...|alt=<text>]]
|
Adds the alt attribute to the image. HTML documentation for this attribute can be found at the MDN Web Docs. |
| Classes | [[File:...|class=<text>]]
|
Adds the class attribute to the image. |
| Resizing | [[File:...|<resize>]]
|
<width> and <height> must be whole numbers. Can be one of the following:
|
Galleries
- This section only showcases gallery types. If you'd like a more thorough guide on the usage of galleries, check this blog.
Galleries are a way of displaying multiple images in a single, connected block. The general syntax is:
<gallery type = "type">
File:filename.extension|options|caption
File:filename.extension|options|caption
{...}
</gallery>
Note the lack of brackets; they should not be present. Also do note that some options will not work as expected with galleries; formatting, alignment and resizing will be displayed as caption text for the images, if they come after the actual caption. Classes will not work altogether. For images, the only options available are alt and link.
Types
There are three gallery types:
| Type | Description | Example |
|---|---|---|
gallery
|
This type will display the images in a series of separate blocks. This is the default type if no type or an invalid one is typed. | <gallery type = "gallery">
File:MP-MrNoice.png|MrNoice
File:MP-Asttro.png|Asttro
File:MP-BubTheTamer.png|BubTheTamer
</gallery>
|
slideshow
|
This type will display the images in a single block, allowing the reader to browse through the images in the gallery. Captions are displayed on hover. | <gallery type = "slideshow">
File:MP-MrNoice.png|MrNoice
File:MP-Asttro.png|Asttro
File:MP-BubTheTamer.png|BubTheTamer
</gallery>
|
slider
|
This type will display the images in a single block, automatically scrolling through and taking the entire space of the page. Captions are displayed on hover as titles. If you want to add additional descriptions to the images, use |linktext= at the end of every image.
|
<gallery type = "slider">
File:MP-MrNoice.png|MrNoice|linktext=This is MrNoice
File:MP-Asttro.png|Asttro|linktext=This is Asttro
File:MP-BubTheTamer.png|BubTheTamer|linktext=This is BubTheTamer
</gallery>
|
You can add links to images in a gallery, as previously estabilished. The following code will work as expected:
<gallery type = "gallery"> File:MP-MrNoice.png|MrNoice|link=User:MrNoice File:MP-Asttro.png|Asttro|link=User:Asttro File:MP-BubTheTamer.png|BubTheTamer|link=User:BubTheTamer </gallery>
But if the main point of adding the gallery is to navigate between pages (link them), then you should use the navigation="true" attribute. Now what does it change? To the desktop user, nothing. To the mobile user, it makes the galleries look nicer. Let's see it here:
<gallery type = "gallery" navigation = "true"> File:MP-MrNoice.png|MrNoice|link=User:MrNoice File:MP-Asttro.png|Asttro|link=User:Asttro File:MP-BubTheTamer.png|BubTheTamer|link=User:BubTheTamer </gallery>
If you use your phone or enter the mobile view mode in your desktop, you can see the difference; the first one is unorganized, while the second one is in a grid shape.
Tabbers
To start a tabber, write the <tabber> tag, and to end it, use the </tabber> ending tag. To add sections to it, write |-| <title> = <text>. Here's what that looks like:
<tabber> |-| Section 1 = I |-| Section 2 = like |-| Section 3 = jelly </tabber>
Nesting Tabbers
You can also add a tabber inside a tabber. And add a tabber inside that tabber. And even add a tabber inside that other tabber. To start it, add {{#tag:tabber|, and to end it, add }}. It acts very similarly to a template; except parameters will each be a section. To add a new section to it, write <header> = <text> {{!}}-{{!}}. The {{!}}-{{!}} tells the interpreter that a new section is starting. Here's what all this looks like:
<tabber>
|-| Section 1 =
This is the first section of the tabber.
{{#tag:tabber |
Section 1.1 = This is the 1.1th section of the tabber. {{!}}-{{!}}
Section 1.2 = This is the 1.2th section of the tabber.
}}
|-| Section 2 =
This is the second section section of the tabber.
{{#tag:tabber |
Section 2.1 = This is the 2.1th section of the tabber. {{!}}-{{!}}
Section 2.2 = This is the 2.2th section of the tabber.
}}
</tabber>
This is the first section of the tabber.
This is the 1.1th section of the tabber.
This is the 1.2th section of the tabber.
This is the second section section of the tabber.
This is the 2.1th section of the tabber.
This is the 2.2th section of the tabber.
Page Indicators
- Simplified from Help:Page status indicators
Page status indicators (also known as top icons or heading icons) are icons located at the very top of a page, used to display information about a given page in the wiki. It can be used for a variety of things, since it accepts any wikitext that can be parsed.
Usage
Its wikitext usage is as follows:
<indicator name="foo">
[[File:Foo.svg|20px]]
</indicator>
Notes
- It is common practice to use indicators along with images, but it can render any valid wikitext input.
- The name attribute is a unique identifier of the indicator. If there are two or more indicators of the same name, only the last one will be added.
- The indicators are sorted not by the order in which they were added, but by alphabetical order. This allows for complex hierarchical structures.
- The name will also be used as the title attribute of the indicator element, which means it must also serve as a short description of the indicator.
- Indicators are not tracked by MediaWiki software, like for example in a special page that you can search where they are found. It is expected that they be used together with other software that can be tracked, such as categories.