Never be limited to the vendor's ideas: Create your own spaces, templates/blueprints/doctypes and macros based on components provided by the projectdoc Toolbox!

The projectdoc Toolbox for Confluence is a set of tools to support you and your team to define your own page blueprints and space blueprints. It also allows you to build your own macros based on the infrastructure the projectdoc Toolbox provides.

 

Note that the Java API is currently not stable. Therefore we recommend to do the integration work for your tools by the use of the Web API Extension.

If you do need to use our Java API we recommend to get in touch!

To define your blueprints, you could use any approach that allows you to use macros from the projectdoc Toolbox. Make sure that your page blueprint creates a projectdoc Document!

 

Consider to use the Doctype Maven Plugin to define your project based on the projectdoc Toolbox on models. These models hide some of the more complex requirements to build your blueprint add-on.

Note that we call page blueprints doctypes since these doctypes provide some more features than blueprints do.

Also note that you need programming skills, especially you need to know how to work with Maven to create a deployable artifact from a project.

Resources

More information on this feature.

projectdoc Document
Document Type
A document type (doctype) defines the properties and section for document instances. It also provides home and index pages. In Confluence these doctypes are implemented as page blueprints, usually with one template. This template is used to create new pages in Confluence.
Web API Extension
Doctype Maven Plugin
Create doctype add-ons (OBRs) for the projectdoc Toolbox with Confluence Blueprints based on XML model descriptions easily!
Guided Writing & clutter-free Reading
Document Types

More Features

List of features of the projectdoc Toolbox for Confluence.

The query matched no documents.