A projectdoc Document demands a Name and a Doctype to be set. All other document properties are recommended, especially the Short Description, but are not necessary.

Since Nameless Documents the name of a projectdoc Document may be derived from the Title. Since the title is mandatory for a Confluence page, the only property still required being part of the table within the Document Properties Marker Macro was the Doctype.

The Doctype property's value also needed to be provided in plain text. The projectdoc Toolbox does not a macro here since the value is required before any property value resolvement takes place.

This version of the projectdoc Toolbox allows to specify the doctype as a parameter to the Document Properties Marker Macro. This way the property cannot be accidentally be removed or changed. Since the property is hardly ever changed, it will not take space in the editor, too.

Note that a property with name Doctype still overrides any value set with the macro parameter. This is to ensure backward compatibility. It is not meant to be a standard use case.

Here is an example showing the doctype 'todo' as part of the macro.

Image Added

When opening the macro in the editor, the Doctype parameter shows the type if the document.

Image Added

The projectdoc Toolbox provides support to render the contents of an attached file. This allows template authors to design document types (blueprints) that show contents from files easily. From the moment a user attaches a document, the contents will automatically been shown.

The Attachment Link Macro makes it easy to reference an attachment as a property value. Use the Reference Attachment Code Block Placeholder Macro to render the attached file (or a part of the file) in a code box. In case there is no need to have the attached file as a property, use the Attachment Code Block Placeholder Macro.

The Autocomplete with this version also supports selecting attached files.

When a transclusion macro renders content, the layout may be affected. This is typically because the transcluded content is rendered inside a HTML div element. This way CSS selectors on first element may not be applied or (not applied) as expected.

The users now can add additional CSS rules by referencing the selector "projectdoc-transcluded-content" which is rendered with the transcluded content.

The Section Macro and the Content Marker Macro allow to control the rendering dependent on the evaluation of document and space properties. Prior to this version all listed properties have to meet the constraints (i.e. they were ANDed). With this version authors can specify that at least one property must match (i.e. they are now ANDed or ORed).

Currently we do not support more sophisticated queries using AND and OR in one specification.