Do not render text to the reader that has no information value.

A team needs to maintain the documentation for a product or project collaboratively.

How can the team ensure that the information from their documentation can be consumed by readers easily? Even despite the fact that documentation is continuously evolved.

Structure

Noise is visual garbage that distracts the reader without giving any useful information. Examples for such noise are:

  • Decoy text is text without information such as

    • Titles for sections whose function is obvious
    • Intro text that describes what is obvious
  • Skeleton text are text fragments where information may be added at a later time (this noise is typically introduced by templates)
    • Section titles without section body
    • Documents with only auto-generated content without information
    • Dead links which are not recognizable as such
  • Tedious representation (compact representation would be easier to recognize with one glance)
    • Two-column tables instead of definition lists
    • One-element lists
    • Short descriptions as part of the metadata

Keep in mind that the reader is happy for every sentence s/he does not need to read.

Authors should remove noise and be sensible for the problem of superfluous content that transmits no valuable information.

The projectdoc Toolbox provides tools to reduce the noise in documents. The Section Macro defines the structure of a document but do not show up if empty. It can also be hidden if the section is not yet ready to be displayed to the reader. The rendering of the title can be suppressed for sections whose function is obvious from the location in the document in order to reduce decoy text. Properties within the Document Properties Marker Macro also do not show up if there is no value (or can also be hidden). Properties may also control which sections are shown.

Advantages

Document without noise are easier and quicker to read. Since reading occurs more often, the additional investment for removing noise is almost always a good idea.

Disadvantages

For inexperienced authors removing noise typically takes more time. To reduce this resource investment these authors should work with a professional or pair with more experienced authors to catch up quickly and with more fun.

Resources

For more information regarding this practice please refer to:

projectdoc Document
projectdoc is based on projectdoc documents. Creating a projectdoc document is easy: A projectdoc document is a Confluence page using document properties and sections.
Document Properties
Properties are metadata that can be added to every projectdoc document. If you require a set of metadata for each instance of a document type, you should write your own doctype.
Document Properties Marker Macro
A table containing document properties. Three columns: name, value and meta data (aka controls) to a property.
Section Macro
Renders a section, if the body is not empty. Supports authors to create content, clutter-free rendering without empty sections. Allows to transclude the content.
Definition List Macro
Renders term and definition information as a definition list. Currently Conflucene does not easily support authors to write definition lists. But definition lists allow to render this form of information efficiently.