Documentation guidelines

Documentation is not optional

You won't do it "later"...

GNOME Documentation Style Guide

Style

Golden rules

Tone

Things to avoid:

Terminology

Writing for the web

http://www.nngroup.com/articles/how-users-read-on-the-web/

http://www.nngroup.com/articles/be-succinct-writing-for-the-web/

International audience

Easy to read, easy to write :)

International audience

Think about translators

Process

  1. Get involved in the design (terminology, UI)
  2. Write the doc early (usability bugs)
  3. Brainstorm content (check with coders)
  4. Write, rewrite, and rewrite
  5. User review

Example 1

The Foobar applet is a handy little screen grabber.

Example 1

The Foobar applet is a handy little screen grabber.

You use the Foobar applet to take screenshots.

→ be neutral, be consistent

Example 2

In the menu tree you will notice that there are two main menu lists.

Example 2

In the menu tree you will notice that there are two main menu lists.

The menu tree contains two main menu lists.

→ use present tense, and active voice, avoid "there are"

Example 3

If you would like to place a menu item onto the panel, you can drag and drop from the menu to the panel and it will place a launcher there with all the appropriate properties set for you.

Example 3

If you would like to place a menu item onto the panel, you can drag and drop from the menu to the panel and it will place a launcher there with all the appropriate properties set for you.

You can drag a menu item from the menu to the panel. The drag action places a launcher on the panel with all the appropriate properties set.

→ split big sentences, be factual, keep it short

Ressources