projectdoc Toolbox

Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.

Doctypes help authors to add their information in a uniform way. This uniform way support the authors to concentrate on the content and not be distracted by formatting or coarse structuring issues. It also helps readers to find the information more quickly.

Teams should only write documentation that is essential and valueable


Templates are only a tool. If the information demands it, authors are free to add or adapt the templates to their needs. It is the ease of accessing information that counts, not the adherence to standards.

Please keep in mind to discuss deficiencies with your team members and documentation architects to continuously improve the documentation structure and tools.

Keep your documentation essential, valuable and write it just-in-time!

We assembled some quotes according to documentation writing on the projectdoc homepage. Get inspired on how to design your project documentation!

Doctypes are implemented as page blueprints, which Confluence allows to adjust to your needs. Teams should decide what elements are worthy to use and which should be discarded. After all there must be a return of investment and every asset, which includes documents, is also a (potential) liability.

To get you started with projectdoc quickly we recommend to install the Core Doctypes. With this basic set of blueprints you may start spaces to document topics that are relevant for your team. We also provide (and plan to provide) additional doctype add-ons for other  areas of project documentation.

The projectdoc Add-on provides only a demonstration space and the Blank Document doctype.

Related Documentation

The following links direct you to related documentation within this wiki.

English and German by Default


All doctype add-ons are available in English and German language (except for the V-Modell XT add-on for which only German is supported).

For more information on this topic please refer to Localization.

Take an alternative introduction to the Core Doctypes

Or have a look at Doctypes Introduction.

Create a Space

To get started with the Core Doctypes, we recommend to create an Agile Documentation Space.

This provides the basic structure to add new documents easily by the use of home and index pages. This is how the space looks like:

List of Space Blueprints

Addressbook Space

Manage information about people and their roles and interests in a product or project. This space contains information about roles, persons, and organizations.

Glossary Space

Manage information about a domain. Add glossary items and associate them with domain information.

Index Space

Collect commonly used information like spaces properties or type documents. You may also include fragments to be used by transclusion or other information that is relevant for all dependent spaces.

Library Space

Manage information about resources. This includes books, articles, podcasts, as well as information about the authors of these resources.

Main Space

Create a space to organize information for your agile team. Combine single-sourced modules with dynamic lists and transclusion to support collaboration.

Topic Space
Create a space to collect and organize information on a topic.
Workspace Space

Create a space to collaboratively collect information on a specific topic. A workspace does not demand for updating information. It is a place to work with until a goal is reached. Move the result of your research to topic spaces and discard or archive this space.

Core Doctypes

The following document types are part of the Core Doctypes Add-on.


You may also take an alternative introduction to the Core Doctypes by a Prezi presentation. The presentation provides a good overview by grouping closely related doctypes.

The core doctypes provide the base for your agile documentation work. You may also use them as an inspiration for designing your own templates that meet exactly the requirements of your project.

Please refer to Tour for Document Authors for an introduction on how to use these templates and to Tour for Template Authors for information on how to design your own templates.

# Name Short Description Categories
Associates two documents.
Categorize associations by a type.
Categories allow to set document instance of different doctypes in a hierarchy.
Categorize categories by a type.
Describes an information need and use this description as a basis to create and maintain a document.
Categorize charters by a type.
Excerpts are abstracts of information found in a resource, such as a book. If you want to go into more detail for a given resource, there may be multiple excerpts as subpages of the resource document.
Categorize excerpts by a type.
Defines the context through which readers acquire skills. The level sets the expectation on the author's techniques to teach.
Categorize experience levels by a type.
FAQs help to record an answer to a frequently asked question concerning the project, the product, the system or the process.
Categorize FAQs by a type.
Generic Documents provide information where no other doctype matches.
Categorize generic documents by a type.
Glossary items are part of the domain glossary for the project. Glossaries support the team to use terms of the domain consistently in conversations and documentation.
Categorize glossary items by a type.
Resources are identified by their media type. This may be the MIME type, but also a human readable string, that identifies the syntactic format.
Categorize media types by their type.

Metadata documents provide tables of simple key/value pairs. This information can be used as an aspect or as additional space properties to be available for reference on your wiki.

A documentation module is a fragment which is usually transcluded by other documents. The lifetime of a module document is independent of the lifetimes of the documents that reference it.
Categorization of document modules for single sourcing.
Information about organizations that take a part in the project. You may collect common information here for all persons that belong to an organization, such as address or homepage.
Categorize organizations by a type.
Provides information about a person. This includes contact information (important if the person is relevant for the team) or information about the competences (if the person is an author about a topic relevant for the project).
Categorize persons by a type.
Profiles provide views on documents via delegation.
Categorize profiles by a type.
Quotes relevant for the project. Allows to store the content and metadata to the quote.
Categorize quotes by a type.
Organizes glossary items.
Categorize relations by a type.
Resources are books, webpages, videocasts relevant for the project. Add important information to your project about resources that lie outside the control of your team.
Resources are identified by their type. This is not the MIME type, but human readable string, that identifies the semantic, rather than the syntactic format.
Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents.
Categorize roles by a type.
Sections of a document are typically part of a document. But the size of sections may vary. To support a team to write collaboratively on the documentation, a larger document may be subdivided into external section documents.
Categorize sections by a type.
Compile other documents, yet space indices are themselves projectdoc documents. So they can be tagged and grouped.
Categorize space indexes by a type.
A party that takes interest in a project. The stakeholder is either a real person, an organization or group, or represents a class of individuals, groups or organizations.
Categorize stakeholders by a type.
Describes a single step of an activity. A step is a generic document that is associated with a document that describes a process. It may be a test log or a howto.
Categorize steps by a type.
Subject documents allow to set document instance of different doctypes in a common context.
Categorize subjects by a type.
Document the semantics of a tag. May also be used to document Confluence labels.
Categorize tags by a type.
A description of a given topic. A topic may describing or explaining a concept, a task to accomplish or a reference. There are a couple of topic types that set the expectations for the reader. Instances of the topic doctype usually have independent lifetimes from any referencing documents.
A topic type is a semantic type of the topic. It helps to set the expectations of potential readers.
Guided tours through existing information. This allows to aggregate topics for a given question or audience, thus providing a view on a topic.
Document a version of a product or service.
Categorize versions by a type.

Find more doctypes in the extensions!

Extension Doctypes

The following doctypes are not part of the Core Doctypes Add-on, but are (or will soon be) available in separate packages.

Separate add-ons make it easy for teams to select those doctypes that are useful for them and their specific project requirements.


Please make sure to check those extension doctypes. Maybe they are not provide exactly to what you require, but they can be a good starting point.

For minor changes Confluence allows to adjust the templates easily. For larger changes we recommend to create a blueprint project and build your own add-on. If you have developers on your team, this may be much easier than you think. Please refer to Tour for Template Authors for an overview on how to do this. We plan to release some of our doctype projects on GitHub to make you get started with your own add-on extensions more quickly.

Name Status Short Description
Provides doctypes to create documentation in software development projects. The focus is on documenting the architecture of the product, but it includes templates for other software development documentation requirements as well.
Provides doctypes to document a system or software architecture based on the arc42 Template.
Provides doctypes to collborate with your team. Run iterations and record discoveries that may be of interest at the end of the iteration or for even later reference. Quick notes are more easily added as records to the team's space than to the official documentation tree. Defer the talk to the documentation architect to the end of the iteration (if the discovery is still of interest).
Provides doctypes to organize the developer's work by the employment of a diary. Take you personal planning and professional records to the next level!
A collection of blueprints for Confluence to create and work with documentation for Java projects.

A collection of blueprints for Confluence to create and work with documentation for Maven projects.

Provides doctypes to define the checklists, processes, patterns, tools, and rules your team agrees upon. Writing them down makes them accessible for anyone - especially for new team members. Keep these documents short and to the point!
Mission, vision, strategy for business planning and execution.
Provides doctypes to document services and systems for IT service management (ITSM).
Provides doctypes for documenting decisions, risks, open issues, and meeting minutes.
Provides doctypes for documenting and tracking risks.
Document macros, page blueprints, space blueprints, and components of your Confluence add-on.
Use products (templates) from the V-Modell®XT in your Confluence wiki as blueprints!
Use CFRs to implement continuous performance management in your wiki.
Analyse the impact you can make.
State assumptions and hypotheses to run your experiments. Document your output and plan for outcome and impact.
Use OKRs to define your objectives and focus on your key results.

Install additional Doctypes!

Some doctype and extension add-ons are currently still under development. They will be available for download on the Atlassian Marketplace soon.

Add-ons labelled as AVAILABLE SOON are already published on Bitbucket.

ABOUT TO BE AVAILABLE indicates that the add-on has been released to the Atlassian Marketplace and is waiting for approval.

Add-ons with status AVAILABLE are published on the Atlassian Marketplace and on Bitbucket.

Add-ons marked as NOT YET PUBLISHED are currently under development. Please get in touch if you need to know about the release plan!

POSTPONED indicates that the add-on is no longer under active development to be released on the Atlassian Marketplace, but still available on Bitbucket.


Document Types and Templates
Document types (or doctypes for short) define a set of properties and sections. Each doctype matches at least one Confluence Page Blueprint. Confluence Page Blueprints are a collection of templates, but often the collection contains only one element.
Doctypes Overview
List of all doctypes provided by add-ons. Provides an overview over doctype IDs and blueprint keys.
projectdoc Toolbox Online Manual
The online manual for version 1 of the projectdoc Toolbox for Confluence.
Think Repositories
To organize your documentation place documents in a typed repository and add additional views on demand.
Topic is not meant to be multi-purpose
Despite the name of the Topic Doctype, it is not supposed to be used for any topic. Use the Generic Doctype or the Section Doctype for general purposes.