-
Suggestion
-
Resolution: Duplicate
-
None
-
None
(via Nick Minutello)
It would also be very useful is to be able to set user-defined metadata for a given snip/page. This metadata could added to the indexing for full-text search. It could also be used to drive generation of hierarchical navigation tree (cross-space).
Something along the lines of:
Defining Menu (perhaps as macro-registration config):
<Menu category="type" values="Documentation" render="html"> <!-- defines
specific menu – >
<!-- will resolve to all categories with type of documentation, and
category values for "product" – >
<Menu category="product" values="*" render="dhtml">
<Menu category="Services" values="Services*" render="dhtml"/>
<!-- will resolve to any snip with categories matching hierarchy -->
</MenuList>
</Menu>
Could give either a static hml (or even DHTML) navigation menu
Documentation->
Jira ->
Services ->
Backup Service
POP Service
Confluence ->
Services ->
RSS Service
This means that you can have live navigation (ie add a new snip, it automatically appears in the nav under the correct categories). It also means you could access the same snip under different category navigation directions (when it rightly satisfies both categorisations).
Even cooler would then be the next step of auto-generation of categorisation metadata from the snip/page contents (if you happened to have some natural language (bayesian) means of categorisation - ala Autonomy)
As a long time Confluence user I used to organise all of the company's page using page properties and labels.
Although it is a working solution, I had discovered it is not robust enough and missing some essential capabilities.
This is why we have created Metadata for Confluence Cloud !
It breaks the limitations of labels and page properties for organising pages, lets you configure your own fields with various types, input and query them.
Additionally, it includes a few macros to integrate the metadata inside the page.
Give it a try with a free trial