Formatting

Formatting is - without a doubt - one of the most important things on any wiki. All information on a page should cover every single thing. All wiki pages should look as organized, attractive and precise as possible. A wiki that's attractive enough must attract more users and edits, and even create more interest in the game itself. A disorganized and sloppy wiki can push users away.

There must be a near-perfect consistency between pages, especially for pages of the same type. For example, all pages of a certain resource should be presented similarly, as well as use the same categories, making page searching even easier. They should also be using the exact same type of infobox, which should also be formatted carefully and consistently.

Proper sentence structure and capitalization should always be taken into account at all times when editing a page. Make sure that paragraphs are not too long as to not create an unattractive wall of text. Line breaks into a new paragraph should (but not always, in some cases) occur when speaking of a new factor about something. Much like this page, the very word(s) the topic is about should be bolded only when mentioned for the very first time per page.

Some pages, like the metal one, have icons alongside the text. Images are highly encouraged for almost all pages, but only if they're necessary and properly fit the page.

Categories

A category is, by definition, a class or division of things regarded as having particular shared characteristics. In the case of this wiki, categories are pages that share a similar theme or themes as mentioned before. For example, pages like wood and stone would have the category of Category:Resources. Categories can be added to a page by typing [[Category:category_name]] the bottom of a page.

Templates

Templates are pre-made bits of code that can be inserted into pages. Editing the template page will change the template as it appears on all pages, so it's wise to do some testing before using them. All template pages should include instructions on how to use and properly format them.

All templates are added with two left curly brackets, and end with two right ones. So all templates added to a page look like this: {{template_name}}.

Page combining

Some topics can fit into one single page, while others should have multiple pages or in some cases, have both. If something has a mid-to-high amount of important information by itself, it can have its own page unless it's more of a sub-topic of something else that doesn't need a page of its own. A good example of this topic are the races in Songs of Syx. You'll notice the wiki has a page for all three races: the Cretonians, Dondorians and Cantors. However, these races are also mentioned on the citizens page. This is because the citizens page encompasses the three races, but each race has more than enough information for their own pages. You'll also notice that the citizens page doesn't contain as much information on each race nearly as much as the individual pages about them, this is because adding all of the info of those separate pages would make the citizens page far too long.

If each individual race didn't provide much information, there wouldn't need to be separate pages for them, and the only information about them would only be on the citizens page.

Editing and discussions

Pages can be edited in two ways. Simply clicking "Edit" will make the page editable in the sense of how the page will be seen. The second way of editing is clicking "Edit source", which puts the page into its bare-bones makeup by turning the page into just text. In some cases, editing the source of a page is more helpful when there are more detail-oriented edits to make, such as the properties of a template.

Either way you edit the page, you can click the "Show preview" button, which will show the end result of the edits made. This should always be used to check for mistakes before saving a page. You can also click "Show changes" to compare your changes to what the page had in the previous edit.

Text Editing Syntax

Common format syntax options are as follows:

Syntax	Output
''This is text in italics.''	This is text in italics.
'''This is text is bold.'''	This is text in italics.
<sup>This is superscript text.</sup>	This is superscript text.
<sub>This is subscript text.</sub>	This is subscript text.
<s>This is strikethrough text.</s>	This is strikethrough text.
<code>This is code preview text.</code>	This is code preview text.
<u>This is underlined text.</u>	This is underlined text.
<small>This is small text.</small>	This is small text.
<big>This is big text.</big>	This is big text.
[[Formatting|This is an internal link.]]	This is a link.
[https://en.wikipedia.org/wiki/Main_Page This is an external link.]	This is an external link.
<span style="color: yellow;">This is yellow text.</span>	This is yellow text. (with some CSS)
<span style="color: #ffaefa;">This is pink text.</span>	This is pink text. (with some CSS)

Lastly, you can put many lines of text in <pre> tags. Which creates the following:

This is a bunch of text surrounded in pre tags.
But note that this takes up the entire width of the page.
Always take note of that.
Again, this is done by putting <pre> and at the start and end of the text respectively.
The <pre> tag at the end has a slash in it, like other tags.

Tables (first variant)

Some information may need to be added in the form of a table. A standard table follows this format:

{| class="wikitable" 
|-
! Header 1
! Header 2
! Header 3
|-
| Info 1.1
| Info 1.2
| Info 1.3
|-
| Info 2.1
| Info 2.2
| Info 2.3
|-
| Info 3.1
| Info 3.2
| Info 3.3
|}

Which would produce the following:

Header 1	Header 2	Header 3
Info 1.1	Info 1.2	Info 1.3
Info 2.1	Info 2.2	Info 2.3
Info 3.1	Info 3.2	Info 3.3

With some CSS knowledge, tables can have some interesting customization, such as this:

{| class="wikitable" style="width: 500px; text-align: right; border: 2px solid #00ff00"
|-
! Header 1
! Header 2
! Header 3
|-
| Info 1.1
| Info 1.2
| Info 1.3
|-
| Info 2.1
| Info 2.2
| Info 2.3
|-
| Info 3.1
| Info 3.2
| Info 3.3
|}

Which produces this:

Header 1	Header 2	Header 3
Info 1.1	Info 1.2	Info 1.3
Info 2.1	Info 2.2	Info 2.3
Info 3.1	Info 3.2	Info 3.3

Tables (second variant)

There is another way tables can be made, and the format is as follows:

{| class="wikitable"
! colspan="2" | Header
|-
| colspan="2" | Data 1.1
|-
| colspan="2" | Data 1.2
|-
|| Info A || Info B
|-
|| Part 1 || Part 2
|-
| colspan="2" | Data 1.3
|}

Which produces the following:

Header
Data 1.1
Data 1.2
Info A	Info B
Part 1	Part 2
Data 1.3

The format of this second table makes CSS customization much easier for, as seen here:

{| class="wikitable" style="width: 300px;"
! colspan="2" style="background-color: darkred;" | Header
|-
| colspan="2" style="background-color: #559955;" | Data 1.1
|-
| colspan="2" style="color: yellow; background-color: #336633;" | Data 1.2
|-
| style="color: grey; background-color: #555; text-decoration: underline;" | Info A || style="color: blue; background-color: #555; text-decoration: underline;" | Info B
|-
| style="background-color: #999; | Part 1 || style="background-color: #999; | Part 2
|-
| colspan="2" | Data 1.3
|}

...which creates the following:

Header
Data 1.1
Data 1.2
Info A	Info B
Part 1	Part 2
Data 1.3

Discussions

There might be a disagreement between users about what content should be added to a page. This can be rectified by using the "discussion" tab of a page and asking what information is okay to add. When you add a post, make sure to sign it. This is done by typing ~~~~ at the end of your text in source mode.

Headers

Headers, in "edit source" mode, are made by using the equals key, like this: ==Header==. The more equals signs added to each sign, the smaller the header will become. The example text you see here...

==Big header==
===Getting smaller===
====And smaller====
=====Still going...=====

Produces this...