[Guide] Everything about Guides [Guide]
Index:
I: Introduction
II: Guide Format
-Colors
-Font
-Indentation and Spacing
- Font Size
III: Topics
-Good
-Bad
IV: Guide Writing
-Length
-Grammar
-Sources
V: Constructive Criticism
-How to take it
-How to give it
VI: Guide Ripping
-How to find it
-Reporting it
-Which websites
VII: User Education Team
-What it is
-Links
I: Introduction
I made this guide to explain pretty much everything you need to know when making a well structured and high-quality guide. I have seen many guides look terrible just because they missed key guide making points such as: Indenting, changing font size, or even basic grammar. Numerous guides are ruined by lack of grammar and spelling, people can choose the most interesting and creative topic ever but have it ruined by bad spelling. “How to wright ur gudes” is an example, not only do you look like a 1st grader trying to type but barely anyone will even read your guide. Now read on for some guide formatting!
II: Guide Format
This part of the guide will go over the mechanics on making your guide as well as tips to make it more professional looking.
Colors:
I personally don’t like using colors but it seems the User Education Team encourages this so I will go on a basic description on the colors to use and not use. As Sythe’s forum has a dark layout of dark blue and blue, you may want to stay away from colors that are dark i.e.: brown, dark blue, blue, black, purple, etc. You want to go for more of the light toned colors like: yellow, red, orange, green, etc. HOWEVER! This does not mean spam your guide with ridiculous colors, your guide ends up looking like a circus forum instead of that professional guide you are trying to aim for. Try using colors only for titles, headers, picture titles, etc. Just try not to use color for body paragraphs but if you do stick with one color, its easier on the eyes.
Font:
If used correctly you can make your guide look professional. Try sticking with texts that are around the same or the guide ends up looking really messy. Example: Tahoma and Arial –Good. Comic Sans MS and Monotype Corsiva –Bad.
Indentation and Spacing:
Since Sythe only has basic formatting tools I strongly suggest you type it up on Microsoft word or whatever other word processing application you use as it has spell check, and all other key editing tools. Anyways as for indentation just use it when you start a new paragraph. For spacing, you want to use it every time you start a new body and every time you switch to a new topic so people can easily follow what you are trying to say. If you combine two different topics into one body without spacing, it will end up looking cluttered and mismatched. This can also go hand in hand with the Index. You want to create your large points and within those points you create smaller ones. Example:
II: Guide Format <------- This would be the general topic while
-Colors <------- Would be the sub-topic
-Font Guide
Font Size:
This will be short and to the point: Only use big font for titles and topics and use small font for small descriptions such as pictures in your guides. Other than that stick with the default font.
After reading this, you should have a pretty good base for guide writing. Now onto Topics!
III: Topics
I generally see users stumped and not knowing what to write about, this section should help you get passed that.
Good Topics:
The User Education Team has provided us with a list of do’s and don’ts on topics to write about.
Most people concentrate on Misc. Fun Guides because of their knowledge on that subject.
Bad Topics:
Here is a quote from Macroman the Head User Educator:
Now that you understand what topics are okay and not, why not read about how to write your guide?
IV: Guide Writing
Length:
Depending on the guide you are trying to write the guide can vary in length, from being pretty long (like this one) or a short and simple one. Short guides don’t mean that they are bad, they merely mean the thing that the user is trying to explain doesn’t need quite a lot of explanation thus a guide would be bad on that subject. If you find that your guide comes short, ask yourself “Do people already know how to do this?” If your answer is yes you should try and choose a different topic, if no then just add more detail and add pictures.
Grammar:
Pretty self explanatory, download Mozilla Firefox since it has a built in word corrector and you won’t look like a dumbass with simple spelling mistakes. Nevertheless Mozilla is a program, not a real person so it won’t be able to pick up on your grammar mistakes: sentence structure, mistaken words, wrong use of commas, etc. That’s why I highly recommend typing your guide first on a word processor then putting it on Sythe.
Sources:
If you are applying for the User Education Team, you cannot use any sources whatsoever as stated in the rules and requirements:
Now that doesn’t mean you can’t use simple sources. Finding a word in the dictionary and stating its definition is okay, copy and pasting another persons guide and claiming as your own is not okay.
Now that you’ve got your guide written other people will probably comment on it, which leads me to the next section.
V: Constructive Criticism
I am going to use this term lightly since people will try and use it as an excuse for openly flaming other peoples guides.
How to take criticism:
When you write your guide, don’t expect it to be perfect and everyone to be like “OMFG THIS GUIDE IS FUCKING AWESOME!” actually people might say that but in a sarcastic way, but the point is you have to learn to be able to take criticism and not flame them and be like “WELL YOU TRY WRITING A GUIDE FUCKHEAD!” If its obvious that their post is open flaming then just use the report post button. Don’t post back yelling at them as this will only encourage other members to help the user. If it is constructive criticism like “Good guide, but you should add more detail about so and so” then that’s fine and reply with your opinion, whether you do add more detail about so and so or not always be polite.
How to give criticism:
Read their guide first. If you don’t read their guide you have no idea what they are talking about, just because the title says something doesn’t mean the whole guide is directly on that subject. When giving constructive criticism, frankly state their errors, don’t sugarcoat it or make it sound like the user is retarded, just simply state it and maybe add a compliment. “Great guide, now I know how to do so and so but you spelled search wrong.” Something like that is fine.
VI: Guide Ripping
I love catching someone ripping a guide because of their reaction and the immense satisfaction you get out of catching someone. Users who guide rip are smart enough to know not to copy and paste so they will take the time to reword the whole entire guide instead of writing their own. So it eliminates the point of finding a phrase and googling it.
Finding it:
I will use a ripped guide to point out examples of how to spot one. This is from wikihow:
Wiki:
User:
You can see that the user reworded this section, you can tell its ripped by the almost identical likeness and the order that it is in. Wiki starts with the opponent is a better fighter, backup, weapon, and be hit. You notice that the user has it in the exact order except reworded it a little. User emulates with the opponent being a better fighter, has backup, weapon, being ready to take a hit. Now you can see the similarities
Reporting it:
Since there is no “Report a ripped guide” thread anymore, simply post the source that they used in their guide. Make it easier for the moderators by pointing out the ripped parts by quoting what the original site said and what the user wrote in his or her guide.
Which websites:
Very simple, Google it. But you should always check these two websites:
Wikihow.com
This is the most common website from where you will find ripped guides. Check their title and search it, you should come up with something.
eHow.com
Pretty much the same as wikihow, you will find less ripped guides from here but more than others.
Now that you understand all the guide writing basics and tips on how to write a first-rate guide why don’t you try and apply for the User Education Team?
VII: User Education Team
What it is:
Sythe created the User Education Team to educate fellow Sythe members on miscellaneous topics but generally computer related. From then on, the section has expanded and is a sub-forum that all of the members enjoy reading and learning from.
Links:
http://sythe.org/showthread.php?t=419962 Things to know before and after applying by The Dark
http://sythe.org/showthread.php?t=413690 Application rules and requirements by Macroman
http://sythe.org/showthread.php?t=427244 What Head User Educators do by BootyLove
That’s my everything guide. I think this may be the longest guide ever written on sythe and is over 1900 words long. No sources were used except the links directed to sythe. Sticky pl0x?
Index:
I: Introduction
II: Guide Format
-Colors
-Font
-Indentation and Spacing
- Font Size
III: Topics
-Good
-Bad
IV: Guide Writing
-Length
-Grammar
-Sources
V: Constructive Criticism
-How to take it
-How to give it
VI: Guide Ripping
-How to find it
-Reporting it
-Which websites
VII: User Education Team
-What it is
-Links
I: Introduction
I made this guide to explain pretty much everything you need to know when making a well structured and high-quality guide. I have seen many guides look terrible just because they missed key guide making points such as: Indenting, changing font size, or even basic grammar. Numerous guides are ruined by lack of grammar and spelling, people can choose the most interesting and creative topic ever but have it ruined by bad spelling. “How to wright ur gudes” is an example, not only do you look like a 1st grader trying to type but barely anyone will even read your guide. Now read on for some guide formatting!
II: Guide Format
This part of the guide will go over the mechanics on making your guide as well as tips to make it more professional looking.
Colors:
I personally don’t like using colors but it seems the User Education Team encourages this so I will go on a basic description on the colors to use and not use. As Sythe’s forum has a dark layout of dark blue and blue, you may want to stay away from colors that are dark i.e.: brown, dark blue, blue, black, purple, etc. You want to go for more of the light toned colors like: yellow, red, orange, green, etc. HOWEVER! This does not mean spam your guide with ridiculous colors, your guide ends up looking like a circus forum instead of that professional guide you are trying to aim for. Try using colors only for titles, headers, picture titles, etc. Just try not to use color for body paragraphs but if you do stick with one color, its easier on the eyes.
Font:
If used correctly you can make your guide look professional. Try sticking with texts that are around the same or the guide ends up looking really messy. Example: Tahoma and Arial –Good. Comic Sans MS and Monotype Corsiva –Bad.
Indentation and Spacing:
Since Sythe only has basic formatting tools I strongly suggest you type it up on Microsoft word or whatever other word processing application you use as it has spell check, and all other key editing tools. Anyways as for indentation just use it when you start a new paragraph. For spacing, you want to use it every time you start a new body and every time you switch to a new topic so people can easily follow what you are trying to say. If you combine two different topics into one body without spacing, it will end up looking cluttered and mismatched. This can also go hand in hand with the Index. You want to create your large points and within those points you create smaller ones. Example:
II: Guide Format <------- This would be the general topic while
-Colors <------- Would be the sub-topic
-Font Guide
Font Size:
This will be short and to the point: Only use big font for titles and topics and use small font for small descriptions such as pictures in your guides. Other than that stick with the default font.
After reading this, you should have a pretty good base for guide writing. Now onto Topics!
III: Topics
I generally see users stumped and not knowing what to write about, this section should help you get passed that.
Good Topics:
The User Education Team has provided us with a list of do’s and don’ts on topics to write about.
My suggestion to you is, write more complex guides about other thing's that may interest everybody, like Eric said:
* SCAR/Pascal
* Programming in general. (C/+/++/Ruby/Delphi/Java/JavaScript/etc)
* The internet. This includes HTML, XHTML, and markup languages such as that.
* Computer Basics/Science.
* Software.
* Hardware.
* Tweaks/Hacks.
* Operating system information/guides/hotkeys. (Linux/Windows/MacOSX)
* Internet Security
* Misc. Fun Guides. Anything that isn't internet related that other members would appreciate.
Remember.. It's not about the quantity of guides, but the quality
Most people concentrate on Misc. Fun Guides because of their knowledge on that subject.
Bad Topics:
Here is a quote from Macroman the Head User Educator:
Now that you understand what topics are okay and not, why not read about how to write your guide?
IV: Guide Writing
Length:
Depending on the guide you are trying to write the guide can vary in length, from being pretty long (like this one) or a short and simple one. Short guides don’t mean that they are bad, they merely mean the thing that the user is trying to explain doesn’t need quite a lot of explanation thus a guide would be bad on that subject. If you find that your guide comes short, ask yourself “Do people already know how to do this?” If your answer is yes you should try and choose a different topic, if no then just add more detail and add pictures.
Grammar:
Pretty self explanatory, download Mozilla Firefox since it has a built in word corrector and you won’t look like a dumbass with simple spelling mistakes. Nevertheless Mozilla is a program, not a real person so it won’t be able to pick up on your grammar mistakes: sentence structure, mistaken words, wrong use of commas, etc. That’s why I highly recommend typing your guide first on a word processor then putting it on Sythe.
Sources:
If you are applying for the User Education Team, you cannot use any sources whatsoever as stated in the rules and requirements:
Now that doesn’t mean you can’t use simple sources. Finding a word in the dictionary and stating its definition is okay, copy and pasting another persons guide and claiming as your own is not okay.
Now that you’ve got your guide written other people will probably comment on it, which leads me to the next section.
V: Constructive Criticism
I am going to use this term lightly since people will try and use it as an excuse for openly flaming other peoples guides.
How to take criticism:
When you write your guide, don’t expect it to be perfect and everyone to be like “OMFG THIS GUIDE IS FUCKING AWESOME!” actually people might say that but in a sarcastic way, but the point is you have to learn to be able to take criticism and not flame them and be like “WELL YOU TRY WRITING A GUIDE FUCKHEAD!” If its obvious that their post is open flaming then just use the report post button. Don’t post back yelling at them as this will only encourage other members to help the user. If it is constructive criticism like “Good guide, but you should add more detail about so and so” then that’s fine and reply with your opinion, whether you do add more detail about so and so or not always be polite.
How to give criticism:
Read their guide first. If you don’t read their guide you have no idea what they are talking about, just because the title says something doesn’t mean the whole guide is directly on that subject. When giving constructive criticism, frankly state their errors, don’t sugarcoat it or make it sound like the user is retarded, just simply state it and maybe add a compliment. “Great guide, now I know how to do so and so but you spelled search wrong.” Something like that is fine.
VI: Guide Ripping
I love catching someone ripping a guide because of their reaction and the immense satisfaction you get out of catching someone. Users who guide rip are smart enough to know not to copy and paste so they will take the time to reword the whole entire guide instead of writing their own. So it eliminates the point of finding a phrase and googling it.
Finding it:
I will use a ripped guide to point out examples of how to spot one. This is from wikihow:
Wiki:
User:
You can see that the user reworded this section, you can tell its ripped by the almost identical likeness and the order that it is in. Wiki starts with the opponent is a better fighter, backup, weapon, and be hit. You notice that the user has it in the exact order except reworded it a little. User emulates with the opponent being a better fighter, has backup, weapon, being ready to take a hit. Now you can see the similarities
Reporting it:
Since there is no “Report a ripped guide” thread anymore, simply post the source that they used in their guide. Make it easier for the moderators by pointing out the ripped parts by quoting what the original site said and what the user wrote in his or her guide.
Which websites:
Very simple, Google it. But you should always check these two websites:
Wikihow.com
This is the most common website from where you will find ripped guides. Check their title and search it, you should come up with something.
eHow.com
Pretty much the same as wikihow, you will find less ripped guides from here but more than others.
Now that you understand all the guide writing basics and tips on how to write a first-rate guide why don’t you try and apply for the User Education Team?
VII: User Education Team
What it is:
Sythe created the User Education Team to educate fellow Sythe members on miscellaneous topics but generally computer related. From then on, the section has expanded and is a sub-forum that all of the members enjoy reading and learning from.
Links:
http://sythe.org/showthread.php?t=419962 Things to know before and after applying by The Dark
http://sythe.org/showthread.php?t=413690 Application rules and requirements by Macroman
http://sythe.org/showthread.php?t=427244 What Head User Educators do by BootyLove
That’s my everything guide. I think this may be the longest guide ever written on sythe and is over 1900 words long. No sources were used except the links directed to sythe. Sticky pl0x?
