Date: Fri, 29 Mar 2024 09:27:39 +0100 (CET) Message-ID: <1484970298.17860.1711700859026@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_17859_1599812979.1711700859026" ------=_Part_17859_1599812979.1711700859026 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Tools to render informati= on based on queries at view-time.
The following documents are tagged with this tag.
Name | Short Description | Doctype |
---|---|---|
Agile Documentation |
Agile documentation is not another buzzword. There is actually a set of rul=
es to follow which will lead to meaningful documentation. Writing helpful d=
ocumentation is not easy, but it gets a lot easier with the agile mindset -=
and with the projectdoc Toolbox.
|
topic
|
Annotate Dynamic Lists |
It is pretty easy to annotate dynamic lists with the projectdoc Toolbox on =
Confluence.
|
topic
|
Display List Macro |
Lists references to projectdoc documents in a list. List contain names and =
optional short descriptions.
|
macro
|
<= span class=3D"pd-document-property-value">Di= splay List Template Macro |
Lists references to projectdoc documents in a list. List items are defined =
by templates referencing properties.
|
macro
|
Display Table Macro |
Lists references to projectdoc documents in a table. Allows to select docum=
ent properties for columns. Also non-list representations are provided.
|
macro
|
Inde= x Card Macro |
Renders transcluded content fetched from documents of a result set.
|
macro
|
Index Entri= es Table Macro |
Renders a table of index entries.
|
macro
|
= Reporting |
A short introduction on compiling projectdoc documents in dynamic lists usi=
ng constraints.
|
topic
|
The hidden Section |
The Content Marker Macro identifies content that can be displayed using the=
Display Table Macro. This is a short tip on how to transclude content from=
a projectdoc document.
|
topic
|
Renders transcluded content fetched from documents of a result set.
|
macro
|
Macros that generate a dynamic list automatically should be used as prop= erty values carefully. As long as the property value should be displayed at= the time the page is rendered, everything is fine. But since the value ren= dered at the time of saving the page is set into the Lucene index, searchin= g for this page yields only under certain contexts the required results.
Suppose the Di= splay Table Macro is used as a value for a property in the Document Propert= ies Marker Macro. At the time of saving the page the list shows the row= s A and B. On a query on that property with value A, B or A AND B, the page= will be part of a result set.
Later on the the page is displayed (but not again saved) and now shows B= , C, D. The page will still be on the result set for the query with value A= , B or AND B. This is because the Lucene Index is not updated unless the pa= ge is saved.
The terms dynamic list and automatic list are synonyms= .
The term dynamic value is more general than dynamic list. It is= a dynamic list with only one item or may refer to any other tool that gene= rates a value at request time.
Resources related to automatic / dynamic lists.