- Created by Robert Reiner on 10. Apr 2017
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
Version 1 Next »
All publishing organizations define a style guide for their published information. Such a guide supports teams to write in a similar tone, making it easier for readers to digest the information.
- Domain
- Type
- Principles
Context
Readers need to assume that the documentation is written by s single person. This reduces distraction so that readers are able to concentrate on the content and find information easily.
Problem
How can a team organize themselves to document in a common style?
Structure
Publishing content from different authors is conducted by newspapers and magazines on a regular basis. These organizations employ style guides to deliver quality content. But style guides exists for many other industries, too.
Consistency in written documents increases the ease of reading.
A style guide provides answers to questions to support writers. These include
- Word choice and controlled vocabulary
- Mood and tone
- Product names, Abbreviations, and acronyms
- Capitalization and Punctuation
- Spelling and grammar
- Use of text formatting and typographical conventions
- Use of diagrams and graphics
- Use of templates and categories
- Information Architecture
- Maintenance procedures
- Source code organization, naming, and formatting
There may be different or adjusted style guides for different types of text. For instance the tone of answers in social media networks may be different to that found in printed manuals.
A style guide are constantly adapted and expanded. Problems authors encounter while writing should be noted and discussed. These discussions may result in an updated version of the style guide.
Advantages
The use of style guides has the following advantages:
- Easy reading
- Improves the perceived quality of the product
- Supports authors and therefore decreases the resource consumption to create quality texts
Disadvantages
Creating a style guide or just selecting one is time consuming
Applying a style guide also takes time. Typically documents also have to be proof read. But it may save time because authors, especially unexperienced ones, do not loose time by making style decisions. Think of an author trying to find similar text in the documentation to check how things have been decided in the past. A style guide is an easy to access resource.
For some documents, especially those only used internally, adhering to a rigid style guide may not be necessary. But even for those documents a style guide, loosely applied typically enhances the documentation and makes it easier to read.
Resources
- Style guide
- Definition on Wikipedia
- Developing Quality Technical Information
- A Handbook for Writers and Editors - Direct from IBM's own documentation experts, this is the definitive guide to developing outstanding technical documentation--for the Web and for print. Using extensive before-and-after examples, illustrations, and checklists, the authors show exactly how to create documentation that's easy to find, understand, and use. This edition includes extensive new coverage of topic-based information, simplifying search and retrievability, internationalization, visual effectiveness, and much more.
- The Insider's Guide to Technical Writing
- Every complex product needs to be explained to its users, and technical writers, also known as technical communicators, are the ones who do that job. A growing field, technical writing requires multiple skills, including an understanding of technology, writing ability, and great people skills.
- Information Architecture for the World Wide Web
- The post-Ajaxian Web 2.0 world of wikis, folksonomies, and mashups makes well-planned information architecture even more essential. How do you present large volumes of information to people who need to find what they're looking for quickly? This classic primer shows information architects, designers, and web site developers how to build large-scale and maintainable web sites that are appealing and easy to navigate.
- Rule-Based Writing – English for Non-Native Writers
- With their new guideline "Rule-Based Writing – English for Non-Native Writers", tekom offers a reliable set of rules especially for all non-native speakers of English who write technical English texts either often or occasionally. The guidelines compile, in English, the most important terms, concepts and rules of standardization for technical writing in English on the level of text, sentence and words.
- Read Me First! A Style Guide for the Computer Industry
- The definitive reference for technical writers, editors, and documentation managers, Read Me First! A Style Guide for the Computer Industry, Third Edition,has been revised and updated to cover everything from creating screencasts and referencing web sites to writing for wikis.
- No labels