You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Topics
| Name | Short Description |
|---|
| Aspects light | Add a document as a child and automatically make supplied properties available in the parent. |
| Changing Names | A name in projectdoc used to identify a document is not considered a hard reference. When changing the name of a particular document, the references to the original name do not automatically change. This is by design. It may also by the cause of annoyance. This tip provides information how to deal with this. |
| Create Doctypes with a Model | A short introduction the the Doctype Maven Plugin to generate Confluence Blueprints for projectdoc Doctypes based on an XML description. |
| Monitoring Confluence | Have you ever experienced performance problems with your Confluence on premise (Server) installation? This tip might help you. |
| projectdoc Bulk Changes to Documents | The Web API Extension for the projectdoc Toolbox can be employed to make bulk changes to documents. Since there is no safety net, these actions need to be take with care. This tip introduces a way to conduct this task. |
| Space Groups | The projectdoc Toolbox supports organizing collections of spaces. Some of these spaces provide general information, some are specific for a product, a project, or a team. Teams may organize their spaces in groups with shared configuration and information. |
| Supply Documents | Show how to import properties from other projectdoc documents into a projectdoc document. |
| Using Aspects | Add a document as a child and automatically make supplied properties and sections available in the parent. A short walk-through to use the Aspect Feature in your information architecture. |
