Build a navigation to related and associated information by the use of document properties and dynamic linking.

Organize information physically in flat hierarchies. Add views to put these documents in different contexts.

Consider content by the frequency of change. Group content in information sets that change in the same frequency. The most important category for changes is the record, which implies no change.

In order to take personal notes on one's own work and to reflect upon what has to be done or has been done, keep a journal. The information in the journal should be shareable at least with all team members.

Store information physically only by properties that are invariant.

The product and the documentation of the product should be in different release cycles.

Users require a single point of access to all information relevant for a project.

A standard layout makes it easier for new members of a team to find information. A standard layout is project independent and is typically defined by an organisation.

Define a basic structure for all artifacts of a given type. Readers will have an easier job on finding and learning about the information in your documentation.

If documents are added as children to a document, these documents share the lifespan of the parent. If the parent is removed, so are the children.