Create an index space to learn what it is and what it is used for.

Start with projectdoc by creating a space with the standard blueprint.

Categories that are defined to be used with any doctype. So any document instance defined for these categories has to make sense for any doctype.

Macros to help authors to reference other documents that are relevant to the current document.

A template assists authors in writing documents of a given type. Templates help that documents are similar in structure and therefore are also easier to read by members of the project team. projectdoc only renders table rows and sections, if they actually contain information. This reduces clutter to distract readers.

Adjust your Confluence personal space to work as a personal space for projectdoc.

Macros to help authors to a document structure so that the information is easier to understand.

Add roles to your space and set the audience of a topic document to one of the roles.

Doctypes to help organize the space. This includes homepages for particular information (like the homepages for each doctype) and tours that provide a specific view on existing documentation.

Create a space to work on a given topic. This spaces uses an index space to reuse content.

Home and index pages help to organize documents by type. For each doctype there is a homepage and and index page. The homepage shows the central documents that are added to it (immediate children). Index pages list all documents of the space, regardless of their location.

Macros to support single sourcing for creating modular documents.

The Display Table Macro allows to specify queries on documents. The documents are listed in a tabular form per default. Authors declare the document properties to be displayed in the columns of the table

Doctypes that help to write modular documentation and therefore support single sourcing.

Authors use the Display Table Macro to list documents that match a query. This screencast shows how to add one to a document.

These are the generic working horses that are used whenever no specific doctype matches the intention of the author.

Learn about the central most heavily used macros of your projectdoc Toolbox.

Resources describe relevant information for a project. The essential parts are noted to make it easier for finding the most relevant parts quickly. Excerpts allow to add the information as subdocuments.

Macros to support a team to write their documentation collaboratively.

Subdocuments are associated with the lifetime of the parent document. The section doctype is the most generic type of document, but there are others, that are specific to a certain doctype.

A list of doctypes that have a specific purpose. The core doctypes are none-the-less quite generic so that they can be used in almost any project.

The lifetime of a subdocment is associated with that of its parent. Subdocuments help to organize content within a document by externalizing it. This makes it easier for teams to work on a document together. Referencing parts of the document is also easier.

What if no existing doctype matches the purpose of the document? Here are some tips how to handle this situation.

Instead of a table listing the name and properties of the subdocuments, transclude the content into the parent document.

Autolist macros allow to display a list of documents dependent on a set of properties. This screencast shows how to use the Display Table macro to select all documents tagged with a given keyword.

Screencast to show how the Definition List Macro is used to create definition lists in Confluence.

Screencast to show how the Definition List Macro is used to create definition lists in Confluence.

Property values should only change when a document is saved. They should not be dependent on request-time. If they are, then they are called 'dynamic'.

With the doctypeBorderImageServlet and some custom CSS it is possible to render a border image that contains the doctype name of the currently displayed Confluence page.

The projectdoc Toolbox provides an interface for template authors to replace placeholders with space and context properties.