You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Use or define page blueprints with properties / metadata and sections that render only if they actually contain information. Use or define space blueprints with homepages for document types for dynamic organization.
In order to stop the Blank-Page-Syndrome authors need to know where to put a piece of information. Therefore they need to locate
- the appropriate space
- the appropriate location within the space
- the appropriate document type / page blueprint
The wizard of the selected page blueprint will then guide the author to put the information where the reader will expect it to be.
Cannot find content to transclude!
Please check the reference (ids= / tags=main) to the document 'PDAC:Templates' to transclude from.
If you want to silence this message on missing content, check 'Missing Content Message'.
Please refer to the Transclusion Macro documentation for more information about this macro.
Cannot find content to transclude!
Please check the reference (ids= / tags=main) to the document 'PDAC:Default Locations' to transclude from.
If you want to silence this message on missing content, check 'Missing Content Message'.
Please refer to the Transclusion Macro documentation for more information about this macro.
Resources
More information to get started with the projectdoc Toolbox:
- projectdoc Toolbox Online Manual - The online manual for version 1 of the projectdoc Toolbox for Confluence.
- projectdoc Introduction - A short introduction into the concepts and features of the projectdoc Toolbox.
- Hands-on Tutorial - Get started with the projectdoc Toolbox: learning by doing
- Introduction for new Users - Provides information to get new users of projectdoc get started with projectdoc documents and spaces.
- Basic Concepts and Conventions for projectdoc - Concepts central to projectdoc. Things users have to understand to get the most out of using projectdoc.
- Tours - Guided views on topics for different audiences.
- Doctypes - Doctypes define properties and sections for documents. They are essentially Confluence Blueprints that help to create pages in your wiki based on templates.
More information on macros used in the examples.
- Section Macro - Renders a section, if the body is not empty. Supports authors to create content, clutter-free rendering without empty sections. Allows to transclude the content.
- Document Properties Marker Macro - A table containing document properties. Three columns: name, value and meta data (aka controls) to a property.
- Wiki Link Macro - Allows to render a link to a wiki page.
