Halo Esports Wiki:Tutorial/Part 3

Page Organization
We already know how to use headers, but what about more advanced page organization? This section will go over several organizational things and contain some wiki code that you may want to save so you can copy-paste in the future.

Box
This is how Picks and Bans pages work. Items will autofill into a grid left to right and then top down depending on the dimensions of the viewer's browser. You can also control how much space there is in between elements in the grid. Here's how to use a box:  Whatever you want in the first "cell"

Whatever you want in the second "cell"

etc

The ?? is the amount of space you want in between elements. This can scale from 1 upwards, and you will probably never want a number bigger than 10.

Here's the code used to generate the above: 

You can read the documentation about Boxes here.

Col (Columns)
Columns, like Boxes, are used to make things display side-by-side; however, instead of lining everything up in a grid, the content is forced into columns. Columns have one advantage over boxes, which is that you're guaranteed to have one column left-aligned and also one column right-aligned (so for example if you only have two columns, and you want whitespace in the middle, Columns will work better than Box). However, columns can be forced to overlap each other at small browser resolutions, and so it is not recommended that you use them very much. If you're not sure which to use, use a Box.

Columns are very straightforward, so see their documentation here.

Table of Contents
If you have at least 4 headings on a page of any level, a table of contents will be created automatically. By default, it's placed right above the first heading and aligned left. But what if you don't want a table of contents? Or what if you want it aligned right?

To hide a table of contents, put the following code anywhere in the page (recommended at the very top):  (That's two underscores, then "NOTOC," then two more underscores.)

To show the table of contents elswhere, put the following code exactly where you want the table of contents: 

If you want to align the table of contents to the left side of the page, simply make a div and put the table of contents inside of it. And by that, we mean insert this code where you want the TOC (i.e. immediately after the infobox):



If you're putting a table of contents on a page with an infobox and want to align it perfectly, instead use:



And finally, if you're putting a table of contents on a team or tournament page and want to be considerate to people with small browser resolutions, add one final piece of code to restrict the maximum width: 

Expandable Section
Click [show] on the right to view

We use these expandable sections for several purposes, whenever we want to include information that might take up a lot of unnecessary vertical space otherwise.

Here's the base code for an empty box:  [Title] Content

Here's the code for an empty box with our standard formatting:

 Click [show] on the right to view

There's a lot of parameters you can change though. Let's go through:

Miscellaneous
This section includes a list of things that are important for you to know how to use and interact with that don't fit well into another section. Topics vary from basic to advanced.

The Team Template
In section 2, we went over how to link a team. However, there are several modifiers you can use, and we will go over them here. You may also find full documentation on the team template and how to use it here.

Pulling Rosters from One Place to Another
When you read about Templates in the next part, you'll learn why this works, but for now just recognize that it does. We'll use CLG's roster as an example:


 * }
 * }

The important thing to notice here is and. What these tags do is allow you to type

{|class="sortable prettytable" ! !ID !Name


 * }

on another page and generate the same table. Just be aware of those tags and this capability, and when you read about templates you'll understand why it works - and be able to apply it in other situations, too.