[G] GuidesKnow what you are talking aboutGuides are complete, detailed, and comprehensive advice for a specific strategy or tactic that can be generally executed and is not situational. Guides are held up against the highest standards of quality in this forum. They are the most valuable resource for the average player. Writing a good guide may yield you wide appreciation and e-fame, but comes with a lot of work and responsibility.
Naturally, do not write a guide about something you are not experienced with. If you have come up with a new build and you just won 6 games in a row with it, do not start writing a guide. Play your build more, tweak it, find out it’s weaknesses and follow-ups and branches. A good rule of thumb is to play a strategy until you lose a couple of times with it against different counters, then modify it until you win most games again, then start to think about writing a guide.
A good guide does not necessarily have to be written about a build in a specific matchup, although that is most common. If you have found a new, incredibly effective way to micro Helions you can write a generic Helion micro guide.
Most of the time guides will introduce builds in specific matchups though. Look through our legacy Strategy forum to get an idea on how to write good matchup build guides. There is no perfect recipe, but a few things to take care of: State the goal of the build, strengths, weaknesses, possible follow-up, and adaptations to what the opponent does. Dedicate a chapter to scouting and how to react to what you see within your build.
To give you an idea of the quality we are eventually aiming for have a look at this incredible SC:BW guide:
http://www.teamliquid.net/forum/viewmessage.php?topic_id=89265Feedback on GuidesBe respectful and remember Rule No 1A guide is always evolving as the game is being more and more understood and as people find counter strategies. As the author it is your job to keep the guide up to date. If other players find weaknesses or suggest changes to the build, it is your job to alter it accordingly. If you disagree, fall back to Rule No 1: Post a replay or some other form of proof that the criticism isn’t valid.
If you think you found a hole in a posted guide, describe your findings and why you think the guide is weak there. It makes your point incredibly more believable if you post a replay along. Also don't be lazy: Make a suggestion on how to adapt the guide to address your criticism. This is how the best guides that stand the test of time are created.
EPT
