We need to allow users to render the properties values in their rendered from without normalization. Due to the fact that ${...} indicates the normalized value, we need to introduce $<...> as the non-normalized reference.

$[Name]: $<Subject> - ${Audience}

Note that $[...] indicates that a link to the document should be rendered on the normalized value.

We should allow a request to dynamically define the transclusion. Request parameters may override parameters from a transclusion macro iff the id matches the parameter.

This way a call can compose a page that otherwise needs to be materialized for each combination.

Allow to specify queries where a property must make an exact match with one of the elements in a list.
This includes

$<Xyz>~(a, b, c)

$<Xyz>~(${Abc})

$<Xyz>~(${Abc}, a, b, ${Def})

Recursion using display properties is a problem on empty caches (otherwise the cache quickly terminates the recursion). Therefore we need to detect circles to render a proper failure messages.

Support single sourcing with the Content Marker Macro should add an HTML ID element when the content is rendered on the enclosing DIV element.

Currently only the start is rendered as a span element.

Check if there as an easy way to provide sort orders breadth- and depth-first on the page hierarchy for running queries.

Every projectdoc section created by the projectdoc-section-macro supports to change the color of the heading and the text within the section. Moreover the section shall be surrounded by a box with rounded edges.

In order to support phantom references for property references in future we need to change the string representation for property references. Currently the format is PAGE_ID:PROPERTY_NAME. This needs to be changed to SPACE_KEY.PAGE_TITL:PROPERTY_NAME.

This change requires a reindex. Therefore this should be applied to 2.0 of the projectdoc Toolbox which already requires a Lucene reindex.

Confluence 6.x allows to copy a page with its descendants. Transclusions or references may need to refresh the page tree from its root. This is not necessary for all use cases, but should be done automatically.

The Display Document Property Reference Macro fails in following links to another space. The macro should be agnostic to the location of the page.

Provide a control to signal that a property is mandatory.

If a mandatory property is not specified, an error message should be rendered.

The control is only on the document instance. The property cannot be forced to be provided. If a user removes the control, it is no longer mandatory for the given document.

Allow users to control whether unresolved placeholders with the Display Document Properties Macro should be rendered or not.

Rows with a smaller row count should be written verbatim instead of being skipped.

The toplevel elements of a projectdoc document should add a CSS selector to allow doctype-specific styles to be applied.

The CSS selector is prefixed with projectdoc-doctype- and appends the lower-cased doctype ID.

The currently used pattern projectdoc-

is deprecated and will be removed from future versions.

A '\' in front of a $ that introduces a placeholder should prevent the replacement. Another '\' in front of the '\' should prevent the escaping.

This is quite crude but should hold for most of our use cases.

Support Doctype Names and provide mode for subdocuments.

Subdocuments need to have page titles handled two-way: Check with parent title appended, but add the raw title to the button.

Currently the Display Parent Property Macro shows the value only if the parent doctype matches the one given (or its own doctype if empty).

We need a simple solution to accept any document type.

Provide  data attribute to the rendered artificial property 'Space'.

For each property (rendered in a td) in the result of a display table two HTML data attributes are rendered:

• data-projectdoc-pageid
• data-projectdoc-property-name

e.g.:

The Section Macro renders the doctype ID as part of the CSS class on the enclosing HTML DIV element. If the section is on a non-projectdoc page, this value resolves to 'null' so that the class 'projectdoc-null' is rendered.

The 'null' sequence may seem as a bug. Therefore we need to change the sequence to 'projectdoc-not-a-doctype'.

This change breaks the runtime if users have specified CSS styles where the use the old 'projectdoc-null' CSS class.

When directing a new document to its homepage that won't work for different spaces.

This is due to changes to the way Confluence handles the page creation process.

Eager updates cause transaction problems on some environments.

If the document cache is invalid, reindexing may fail.

We need to make the reindex robust by not relying on the existence of the document cache. Therefore the document cache should be cleared before the indexer is started.

The fragment cache fails to cache fragments without target heading properly.

The fragment is matched with blank level, but written to with a default level 1. This results in poor cache usage since the new value for level 1 clears all fragments.

The cache must be filled with the correct heading level to improve cache usage.

Exact match queries fail if Lucene derives a valid word stemp.

This will require a reindex to fix exact match queries.

The rendering of the CSS classes is done as HTML attributes without value.

We should provide a projectdoc- prefix for all our CSS selectors.

A delegating document passes an already rendered body to the delegation document renderer. This results to a (swallowed) exception if the rendered content is no valid XML.

In some contexts the rendering of the attribute data-projectdoc-id fails to render a space in front. This causes trouble with parsers that do not expect to have the name of an XML attribute attached to the quotes of the previous attribute value without a space.

The table section rendering mode (e.g. 5+) of the Display Table Macro renders on HTML div element too much.

Currently the space property projectdoc.doctype.(doctype).home only allows plain text links (e.g. My Page or SPACEKEY.My Page). We should also allow a link to another page in this wiki.

The definition list mode of the Tour Macro does not change the title with the name property if instructed to do so. With the table macro everything works fine.