(adsbygoogle = window.adsbygoogle || []).push({}); It seems that now, more than ever, you are looking around the site and you see a cool how-to post. You click on it, try to interpret the instructions, then give up completely.

I've seen some pretty horrible tutorials around here (namely in the MW2 glitching section!) which are pretty frustrating, because the one person who knows how to do the thing can't explain how to do it. At all. So I figured now was a good time for the tutorial of tutorials.

***

1. Always use a numbered list.
Nobody wants to read a huge block of text. Using a list makes it easier for the reader to follow, and it looks a lot nicer too.
Your list should be in normal order, using "1.", "1)", or "1:".
Another good format is to use a title and then a paragraph of text. For example, here "Always use a numbered list" is the title and the rest is the paragraph.

Hint: If your tutorial only has one or two steps, it's not a tutorial. It's a tip/hint.

2. Separate Sections.
Notice how above step one I put "***"? That's how I separate sections in my tutorials. It's good to separate your intro from your tutorial from your summary (if you have one). Also separate other major parts of your tutorial. For example, if one part is on the computer and the other part on the PS3, put a separator in between the two parts.

3. Use Examples if You Need Them.
Look at the sentence I underlined in the last step. You may not know what I meant by "other major parts", so I included an example. Examples are good to clarify a point you made, but keep in mind that you might not always need them.

Hint: Imagine you were reading the tutorial you've written, without any prior knowledge of what the tutorial is about. If you wouldn't understand one part, an example may be in order.

4. Use Proper Spelling and Grammar.
This is one of the major differences between a well-written tutorial and a not-so-well-written one. Maybe you aren't the best grammar user ever, but really try on spelling. Seriously, NGU has a built in Spell Checker. How much easier can it get?

5. Choose the Right Thread Title.
First off, your tutorial should start with [TUT] or How to... (If not Both) that is the easiest way to let someone know it's a tutorial thread. Make sure the title is not misleading (imagine you're the reader again, does the title say what the tutorial is about?). Also, spelling and grammar are important in the title too.

6. Do Research for the Readers.
Don't say this:
"If you don't know how to do this part, look it up on youtube"
Before you post, do the youtube search yourself. Find a good video and use it in your thread:
"If you don't know how to do this part, watch this:
[Video]

Same thing goes for other websites. Don't tell the reader to search for some software on google. Just give them the link to the software instead.

7. Emphasize!
It is really important that you emphasize important parts of the tutorial, such as a very important step, or a warning that could mess up the entire tutorial is not followed.
For example:
Do not write a block of text in your tutorial!
Italics, Bold, Underline, and Bright Colors can be used to emphasize a word or phrase.

8. Know what you're talking about.
Don't write a tutorial on how to get a 10:1 K/D on Modern Warfare 2 If you have never played that game before in your life.
(Maybe you've never played but your friend has told you all of his MW2 secrets? Then you should be all right, as long as you know what you're talking about!)

9. Don't make it Long and Boring.
I'm afraid that I made this tutorial a little long, but there is just a ton of information that I needed to write down. If you can, try to make the tutorial as short and sweet as possible. Keep in mind: If a tutorial is short, it won't be boring.

***

A Quick, Final Summary:

1. Always use a numbered list.

2. Separate Sections.

3. Use Examples if You Need Them.

4. Use Proper Spelling and Grammar.

5. Choose the Right Thread Title.

6. Do Research for the Readers.

7. Emphasize!

8. Know what you're talking about.

9. Don't make it Long and Boring.

***

Hopefully this helps you out!

If you see a tutorial who's writer really should have read this, foreword them here

Thanks for reading, and good luck writing some nice tutorials!