You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Description
We use projectdoc for a number of projects. For each topic we work on, we create a new space with projectdoc.
If the project requires documentation, we create a space with a blueprint provided by the Core Doctypes. If it contains records that create a result, we use projectdoc Developer Diaries to organize our daily information. The Doctypes for Agile Planning are used to organize project related information to collaborate as a team. If we want to document a software project, we use Software Development Doctypes.
So here come a few live examples that use projectdoc.
Maven Plugins
We decided to move our documentation from the XDoc format to projectdoc on Confluence. This allows us to update the information independent of the release cycles of the products. We also take advantage of templates and macros that make it much easier to create the documentation collaboratively.
Plugin | Short Description |
---|
| Tools to manage apps on a Confluence server remotely via the UPM REST API
based on Maven. |
buildmetadata-maven-plugin | Generates build metadata and provides it as Maven build properties. The properties are written to a properties file that can be included in the generated artifact. The information can also be added to the manifest file. |
doctype-maven-plugin | Create doctype add-ons (OBRs) for the projectdoc Toolbox with Confluence Blueprints based on XML model descriptions easily! |
smartics-ea-maven-plugin | Integrates the Enterprise Architect (Sparx Systems) into a Maven build process. This allows to export diagrams to be used for documentation in other tools, such as projectdoc. |
Demo Spaces
We provided some space online to help you visualize some space you