A directory of resources inthe field of technical communication.

Articles>Documentation>Style Guides

12 found.

About this Site | Advanced Search | Localization | Site Maps
 

 

1.
#35525

Consistency and Community-Generated Content

I’ve been collecting examples of wildly inconsistent writing lately. I’m not sure why these have stuck out to me, but when I think of book sprints and community writing events, consistency is an important, though sometimes difficult, goal and outcome.

Gentle, Anne and Janet Swisher. Just Write Click (2009). Articles>Documentation>Style Guides>Wikis

2.
#23401

Do Not Forget Bibliographical Data in Technical Documentation!

Information products, e.g. manuals, drawings etc, must, besides the technical message, contain certain formal data, which too often is left out. Proper formal data contributes to good order and favours the producer as well as the user of information products.

Rullgård, Åke. TC-FORUM (1999). Articles>Documentation>Style Guides

3.
#14753

Documentation through the Discovery Process   (PDF)

Kloss describes a process of composing documentation that requires the writer's involvement at every phase of product development.

Kloss, Marilyn B. Intercom (2002). Articles>Documentation>Style Guides

4.
#14699

Elegant Documentation   (PDF)

Blank discusses the benefits of using consistent styles in documentation.

Blank, William. Intercom (2001). Articles>Documentation>Style Guides

5.
#23435

An Exchange of Views

A discussion about INTECOM's project for researching and establishing English-language documentation guidelines.

Fuchs, Amo and Ronald S. Blicq. TC-FORUM (2000). Articles>Documentation>Style Guides

6.
#34039

How to Use the Bulleted Lists Properly in Your Technical Document?

Bulleted lists are important in technical writing. They summarize information in a manner that is easy to read and absorb. Use them whenever you can to get your information across quickly. Bullets are ideal for things-to-do, equipment, sets, collections, cooking ingredients, and all kinds of other lists.

Akinci, Ugur. Technical Communication Center (2009). Articles>Documentation>Style Guides>Technical Writing

7.
#35126

The Missing Manual Authors’ Guide   (PDF)

This Authors’ Guide tells you everything you need to know to write Missing Manual. It starts out by giving you a brief introduction to the Missing Manual way of explaining things and then takes you through the nitty gritty of style guidelines, figure formatting, and so on.

Missing Manuals (2009). Articles>Documentation>Style Guides>Technical Writing

8.
#20707

Style Guides and Technical Writing

A style guide consists of formats used when creating documentation. Some companies maintain a formal style guide and adhere to strict documentation standards. Other companies may be more informal, but still maintain some semblance of a style guide, even if it is only an example of the documentation they create.

Taylor, Vicki M. Suite101 (2001). Articles>Documentation>Style Guides

9.
#38010

Use a Style Guide as a Strategic Tool

You can use a corporate style guide to enforce the strategic development of your documentation.

Weber, Kai. Kai's Tech Writing Blog (2011). Articles>Documentation>Style Guides

10.
#24277

Using a Doc Spec for Printed Books   (PDF)

All technical documentation projects benefit from a good content plan or 'doc spec.' The doc spec is a blueprint for a document. It identifies the product, users, source materials, and subject matter experts (SMEs). It also provides a preliminary outline of topics and estimates the work effort to produce the document. The doc spec template is simply a tool that guides you through the document planning and estimating process. Your customized doc spec serves as a record of the who, what, when, why, and how of your project.

Wing, Elizabeth. STC Proceedings (1998). Articles>Documentation>Style Guides

11.
#23783

Using Manual Quality Tables To Improve Manual Quality   (PDF)

Technical writers need to decide what information is to go into a manual, and in how much detail. Such decisions can have a crucial effect on manual quality. Poor decisions can result in published manuals that lack required information, contain unsuitable or unnecessary information, or repeat information in other manuals. To help make better decisions, Hitachi technical writers use Manual Quality Tables. The tables specify what type of information is to go into a manual, the required level of detail, and sources for the information. These tables enable writers to itemize the required contents of a manual before starting to write the manual. In addition, during later revisions, the tables enable writers or reviewers to easily discover any topics that were left out in the original version.

Sudo, Hideki. STC Proceedings (2003). Articles>Documentation>Style Guides

12.
#35709

Writing Great Documentation: Technical Style

Now that I’ve discussed what kinds of technical documentation to write, I can move on to the question of how to actually develop a writing style that produces great technical documentation. So how do you learn to write (anything) well? There’s only one answer: you’ll learn to write well if you write. A lot.

Kaplan-Moss, Jacob. Jacobian (2009). Articles>Documentation>Style Guides>Technical Writing

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon