Formatting:
1. Tutorials must have screenshots in almost every case.
-1a. Screenshots must be .GIF, .JPG, or optimized PNG (such as with the OptiPNG plugin) files less than 800 pixels at their largest dimension, at a reasonable filesize. Not everyone has a network connection as good as yours.
2. Please post a finished tutorial. Don't say "I'll finish later" or "I'll add screenshots when I have time." Unfinished tutorials will be locked immediately.
3. Please post the tutorial you've created in the correct sub-forum. If they're posted in the wrong place, we'll move them if we're feeling generous. Otherwise, we'll lock it.
Content:
4. Always use search before writing tutorials, to see if it has been done before. (Forum search or Google Custom Search )
5. Don't write tutorials on something everyone can learn by reading the help file .
-5a. Don't write tutorials on something everyone can learn by fiddling with effects. If it just takes a couple clicks, don't post it.
6. Please don't be in a rush to write tutorials. As a rule of thumb, if you have very few posts (i.e. only a few dozen), think twice before posting a tutorial. As BoltBait famously wrote, "Noobs should be reading tutorials, not writing them." Stick around and learn more before trying to teach; Paint.NET is far more powerful than you think! Start posting your work in the Pictorium, and if your work really wows us, many users will ask you for a tutorial.
-6a. Keep in mind, even if you're not a newbie with Paint.NET but are a newbie to this forum, this rule still applies. As a newbie to the forum, you don't know what's new, what's old, what's been done to death, and what we'll make fun of. Stick around a little bit, learn about how this forum works, and then you might have people asking for a tut.
7. Think HARD before posting a tutorial that includes Polar Inversion or run the risk of being mocked.
8. If you are tempted to put the word 'simple' or 'easy' in your thread title, ask yourself why you are writing that tutorial in the first place. Your 'tutorial' is probably not necessary.
9. If you're making a tutorial about how to create a sig with a video game render in it, it had better be darned good and unique. We have locked hundreds of them, and we're tired of looking at them. Make sure it's original.
10. By and large, you should lean toward publishing tutorials that depict concepts and procedures well, and not just a specific result. We don't want to lead people by the hand; we want to help them become better. You know the old adage, "If you give a man a fish, he'll eat for a day. If you teach a man to fish, he'll eat for the rest of his life." Let's teach, not just show.
Civility:
11. When you put any work for the world to see, you will get praise & criticism.
If you only want praise and can't take criticism, don't post a tutorial.
12. Don't start fights if someone posts constructive criticism.
Any tutorials or authors not following the above rules will be locked.
Please understand that having your thread locked is not necessarily a bad thing. We lock tutorials that do not follow these guidelines not to squelch discussion, but to prevent fighting and bickering. We're trying to keep this forum friendly and happy, and locking tutorials that will cause fighting is part of that. It's nothing personal, so please don't take offense. Thank you!
Where's my tutorial?!?
If you recently posted a tutorial, and now you can't find it, it may have been moved. For instance, if you posted a really nifty tutorial about cutting images out the easy way, and put it in the Photo Manipulation forum, we might think it was better suited to the Newbie Playground and flipped it over. :-)
1. Tutorials must have screenshots in almost every case.
-1a. Screenshots must be .GIF, .JPG, or optimized PNG (such as with the OptiPNG plugin) files less than 800 pixels at their largest dimension, at a reasonable filesize. Not everyone has a network connection as good as yours.
2. Please post a finished tutorial. Don't say "I'll finish later" or "I'll add screenshots when I have time." Unfinished tutorials will be locked immediately.
3. Please post the tutorial you've created in the correct sub-forum. If they're posted in the wrong place, we'll move them if we're feeling generous. Otherwise, we'll lock it.
Content:
4. Always use search before writing tutorials, to see if it has been done before. (Forum search or Google Custom Search )
5. Don't write tutorials on something everyone can learn by reading the help file .
-5a. Don't write tutorials on something everyone can learn by fiddling with effects. If it just takes a couple clicks, don't post it.
6. Please don't be in a rush to write tutorials. As a rule of thumb, if you have very few posts (i.e. only a few dozen), think twice before posting a tutorial. As BoltBait famously wrote, "Noobs should be reading tutorials, not writing them." Stick around and learn more before trying to teach; Paint.NET is far more powerful than you think! Start posting your work in the Pictorium, and if your work really wows us, many users will ask you for a tutorial.
-6a. Keep in mind, even if you're not a newbie with Paint.NET but are a newbie to this forum, this rule still applies. As a newbie to the forum, you don't know what's new, what's old, what's been done to death, and what we'll make fun of. Stick around a little bit, learn about how this forum works, and then you might have people asking for a tut.
7. Think HARD before posting a tutorial that includes Polar Inversion or run the risk of being mocked.
8. If you are tempted to put the word 'simple' or 'easy' in your thread title, ask yourself why you are writing that tutorial in the first place. Your 'tutorial' is probably not necessary.
9. If you're making a tutorial about how to create a sig with a video game render in it, it had better be darned good and unique. We have locked hundreds of them, and we're tired of looking at them. Make sure it's original.
10. By and large, you should lean toward publishing tutorials that depict concepts and procedures well, and not just a specific result. We don't want to lead people by the hand; we want to help them become better. You know the old adage, "If you give a man a fish, he'll eat for a day. If you teach a man to fish, he'll eat for the rest of his life." Let's teach, not just show.
Civility:
11. When you put any work for the world to see, you will get praise & criticism.
If you only want praise and can't take criticism, don't post a tutorial.
12. Don't start fights if someone posts constructive criticism.
Any tutorials or authors not following the above rules will be locked.
Please understand that having your thread locked is not necessarily a bad thing. We lock tutorials that do not follow these guidelines not to squelch discussion, but to prevent fighting and bickering. We're trying to keep this forum friendly and happy, and locking tutorials that will cause fighting is part of that. It's nothing personal, so please don't take offense. Thank you!
Where's my tutorial?!?
If you recently posted a tutorial, and now you can't find it, it may have been moved. For instance, if you posted a really nifty tutorial about cutting images out the easy way, and put it in the Photo Manipulation forum, we might think it was better suited to the Newbie Playground and flipped it over. :-)
No comments:
Post a Comment
Your Comment will be visible after approval. Post Free classified ads at www.pkbazaar.com to increase your traffic