Transclusion allows to use (possibly parametrized) information in different contexts. Not only reduces this feature the cost by reusing what is already there, it also reduces the maintenance costs since changes can be applied in only one location.

Adding new information must not require to edit existing documents. This is the Open/closed Principle for documentation. Documentation should be open for extension but closed for modification. Each new document is an extension of the whole documentation. By adding tags and other meta-information, the new document should be listed in existing contexts automatically. This is done with automatic lists, which are sometimes called dynamic lists.

With these automatic lists teams are able to provide alternative views on their documentation with minimal maintenance costs. Simply define queries on metadata and list all information for this context in one document.

Document properties define document metadata and information about the documented entity. This information can be accessed to be displayed or to control the rendering of sections. Again, the information is specified in one place and can be reused by transclusion.

Space properties make information accessible and therefore reusable within a space or a hierarchy of spaces. This reuse makes it easy to change a value - such as a version information - in one place and have other information updated immediately.

Metadata can be derived from multiple artifacts created by a software development team. This includes classical metadata like dependencies or project properties, but also test result reports or error codes documentation. Since this information is already available in different locations, it has to be made available from within the documentation system.

The PDAC1 allows to import information as space properties and makes it easily accessible for team members creating documents.

While it is important to be able to import metadata into the documentation system, some resources may be better stored in specific information systems.

For instance

• a team may use an artifact repository to manage the artifacts of a project.
• a team may create an API documentation with a rich user experience.
• a team may need to provided access to all forms of living documentation (for instance test results or online system information).

In these cases it seems not feasible to reproduce the information in the documentation system, but rather link to it. But these links must not be maintained individually. By using space properties, the links may be updated to point to new locations by adjusting the configuration in one location.