by Gerry McGovern
- View article on one page
- Page 1 2
What's a style guide? Why do you need one?
A style guide helps you to quickly and cost-effectively publish content that is of a consistent quality. It is particularly important when lots of editors and authors involved are in the publishing process.
A good style guide takes a lot of time and effort to create. Also, unless its implementation is policed, it will not achieve its objectives.
“As before, this guide is to help Microsoft writers and editors maintain consistency within and across products. It is not a set of rules.”
This is part of an introduction to a Microsoft style guide.
Imagine for a moment that this was a guide for how Microsoft writes software. Let's paraphrase it: This guide is to help Microsoft programmers maintain consistency in how code is written; it is not a set of rules.
Most organizations are accidental publishers. Managers look around one day and find their intranets and public Web sites full of content. And they wonder how they are to manage all this content.
Encouraging people to do the right thing is one approach. It doesn't always work. It is also very time consuming. Most traditional publications I have worked for were run in a dictatorial manner. The editor ruled.
Editors need to make decisions quickly because it is very hard to make publishing pay. It is also the case that writers have huge egos. If you pander to them too much, you will never get the product out the door. Or you will end up with content that is all compromise and no style.
A style guide is a “rules of the road” for a particular publication. It covers…
- Definition of target reader
- Description of style and tone
- Description of key Web-writing conventions
- A-Z of usage
- References
- Page 1 2
- View article on one page
