Changes

Always try to group and categorize your information in a logical and user-friendly way. Prevent redundancies: only create subcategories if there are more of them at the same level (levels are indicated by number of = signs before and after the header), otherwise just collapse to the parent.

Always try to group and categorize your information in a logical and user-friendly way. Prevent redundancies: only create subcategories if there are more of them at the same level (levels are indicated by number of = signs before and after the header), otherwise just collapse to the parent.

You can add many levels of subheaders as you like, but after level 3 they become quite hard to distinguish and will clutter the TOC. If a subject requires many sub-subcategories, consider giving the subcategory its own page. Alternatively, if the sub-subcategories are only small in content, you could make non-TOC headers with simple '''bold text'''.

You can add many levels of subheaders as you like, but after level 3 they become quite hard to distinguish and will clutter the TOC. If a subject requires many sub-subcategories, consider giving the subcategory its own page. Alternatively, if the sub-subcategories are only small in content, you could make non-TOC headers with simple '''bold text'''.

==Images==

==Images==

[[File:placeholder.png|thumb|200px|Right-floating image thumbnail with description.]]

[[File:placeholder.png|thumb|320px|Right-floating image thumbnail with description.]]

To optimize screen space, images should be placed in a floating window, aligned to the right side of the screen. Larger images can be automatically resized to thumbnails, by specifying the thumbnail width. 200px is the preferred thumbnail size. Adding a description underneath the image is appreciated.

To optimize screen space, images should be placed in a floating window, aligned to the right side of the screen. Larger images can be automatically resized to thumbnails, by specifying the thumbnail width. 300px is the preferred thumbnail size. Adding a description underneath the image is appreciated.

For more image formatting guidelines, visit the [http://www.mediawiki.org/wiki/Help:Images MediaWiki Images Guide].

For more image formatting guidelines, visit the [http://www.mediawiki.org/wiki/Help:Images MediaWiki Images Guide].

'''Inline Images'''

'''Inline Images'''

Images that are used, for instance, as part of a step-by-step tutorial can be placed inline, with larger size to make them more readable.  

Images that are used, for instance, as part of a step-by-step tutorial can be placed inline, with larger size to make them more readable. The exact size is up to you, but the width should not exceed 720px.<ref>Thumbnails 720px wide still fit comfortably within a browser window on half a 1920px desktop monitor.</ref>

[[File:placeholder.png|frame|left|300px|Inline Image]]<br clear=all>

[[File:placeholder.png|thumb|none|480px|Caption]]

You can prevent text that is placed after the image from flowing next to the image by placing an HTML break behind it.

You can prevent text that is placed after the image from flowing next to the image by placing an HTML break behind it.

If you want to add code, the syntax might interfere with the Mediawiki syntax. To prevent this from happening, place your code in one of the following preferred ways:

If you want to add code, the syntax might interfere with the Mediawiki syntax. To prevent this from happening, place your code in one of the following preferred ways:

<tt>Fixed format text for short, single-line code.</tt>

<code>Fixed format text for short, single-line code.</code>

 

 

<br/>

<syntaxhighlight lang="text" line style="height:15em; overflow:auto;">

<syntaxhighlight lang="text" line style="height:15em; overflow:auto;">

If your code is longer than, say, 50 lines, you can add a style attribute to introduce a scrollbar, as sampled here. For a 50-line cutoff, use style="height:50em; overflow:auto;".

If your code is longer than, say, 50 lines, you can add a style attribute to introduce a scrollbar, as sampled here. For a 50-line cutoff, use style="height:50em; overflow:auto;".

I might fix that, but if it's really crucial to have an entire page full of code, you should probably give it a separate page.

I might fix that, but if it's really crucial to have an entire page full of code, you should probably give it a separate page.

<!-- start slipsum code -->

<!-- Commence Bacon Ipsum -->

Normally, both your asses would be dead as fucking fried chicken,  

Exercitation beef ribs short loin veniam pig, incididunt spare ribs. In ipsum biltong ex enim, boudin chuck andouille velit duis cow prosciutto elit.

but you happen to pull this shit while I'm in a transitional period so I don't wanna kill you, I wanna help you.

Duis tongue laborum veniam do meatloaf porchetta boudin minim aute in meatball ex turkey occaecat. Dolor kevin officia shoulder corned beef.

But I can't give you this case, it don't belong to me.  

Besides, I've already been through too much shit this morning over this case to hand it over to your dumb ass.

Pork irure non, et nulla qui prosciutto boudin. Pancetta in turducken magna doner do dolor anim ad meatball prosciutto. Officia excepteur drumstick kielbasa ullamco,  

It moves like it has a mind. Like it knows it killed the world once and got a taste for murder.  

velit qui capicola aliquip. Cillum commodo nulla elit drumstick kevin turducken ut consectetur. Frankfurter in in boudin jerky. Do in anim ut sunt voluptate bresaola sed.  

After the avalanche, it took us a week to climb out.

Est leberkas nulla, incididunt biltong bacon boudin rump dolore dolore kielbasa proident kevin aliqua.

Now, I don't know exactly when we turned on each other, but I know that seven of us survived the slide... and only five made it out.  

</syntaxhighlight>

Now we took an oath, that I'm breaking now.  

 

http://slipsum.com

</syntaxhighlight>

<code style="background-color:#000; color:#fff; padding:1px 3px;">ping 127.0.0.1 -n 50 -l 1024</code>

You could also use the <nowiki><code> and nowiki </nowiki> tags, but they are displayed in different ways depending on the content, so use with care.

You could also use the <nowiki><tt> <pre> and nowiki </nowiki> tags if better suited for your needs, whatever works best to present the code as clear and readable as possible.

==Downloads==

==Downloads==

Any information that you want to present as a download link should be placed under this header. This includes manuals, drivers, software installs, etc. Sub-categorize where needed. Download links are presented as list items and are '''descriptive'''. This means you don't waste space by pasting the entire url or writing something like "Click [http://tsgdoc.socsci.ru.nl/index.php?title=Sample here] to download the documentation". Examples:

==References==