One of the 'revolutionary' use cases of Databases I see (and use) is for the management of a group of pages, eg. in the context of documentation. You create an interface for easy management of page status, labels, showing in one grid other important metadata (owner, last update, ...), providing means to add other, extra metadata.
It is fine that you can add pages from everywhere in Confluence as entries in this database, but it is also a good alternative to have the ability to add pages starting from the database itself - Title field: create page, adding the page as a child to a predefined parent page.
Using Databases for the management of a bunch of pages, I experienced this confusing context:
- I can add pages under a parent page, starting from the Title field in the database.
But if child pages are added in another way (eg. via the default Create button, or + sign in the page tree, or via a macro adding the page under that parent page), my database is no longer showing these newly made pages, except if I add these manually to the database. But it is just hard to know what child page is not yet in the database. If there are many pages, you just cannot verify this.
Therefore it would be great to have an option (in the Title field properties in Database) that, if a new page is created under the predefined parent page , it is added as entry to the database. This would guarantee that my list is complete and up to date. Without this option, this list is just not manageable.
We're in the early stages with a new product. Introducing Panorama: Your All-in-One Solution for Content Management in Confluence!
I wanted to share our landing page here incase it is of interest - https://www.kolekti.com/getpanorama
Please feel free to reach out with any questions!