(The following is a companion to this list. Please read both for the full Tutorials Rules list.)
Civility (very important!)
We're trying to keep this a civil forum. In addition to the general forum rules, please follow these when replying to tutorials.
1. If you see a tutorial you think is really bad, and you feel that you MUST say something, just post once. Say something constructive about WHY it's bad, and then leave it alone. And don't start fighting if someone disagrees with you. As Rick said, "Humiliation is hardly the best remedy. If a tutorial sucks, then don't even bother commenting on it. Or, if you must say it sucks then post once and then leave it alone. If you keep whining and crying on a tutorial that's bad all you're doing is bumping it and forcing it to stay at the top of the list."
2. Please don't dig up 2+ month- old tutorials, just to reply with "This is too simple," "this sucks," etc. Why bring the tutorials you don't like back on the top? If you can do better, show us. Write your own tutorial.
You will get a warning the first time you start fighting; the second time, you will get banned for 24 hours or more.
Posting In General:
1. This forum is for Tutorial Publishing only; not requests for tutorials or general "how do I..." type questions.
2. Please post questions about a specific tutorial in the thread for that tutorial.
Every question that is not about a tutorial needs to be published in the General Discussion and Questions forum. If your thread is misplaced, we will either move or lock it.
Tutorial Replying Guidelines
No replies to this topic