The Content Tree helps to navigate a repos content and gives some structure to the backend. It can include Collections, Folders and Document Links that can be nested to reflect a certain logic or structure and help editors to recognize parts of a website or app, or simply provide lists and links for easier content management.
Each node in the tree has its own endpoint with a unique URL slug (API-Id) for HTTP calls. However, nesting does not affect the endpoint URL.
The following types of tree nodes are available:
Collectionsare aggregated lists of
documentsthat match a certain definition. For more info, see the collections page.
Document Linksare single
documentslinked in the tree. They may represent a unique or important document, for example a landingpage or an important document that will be constantly changed by editors.
Folderscan be used to group collections or document links. By now this is their only function and they have no endpoint, but there are some features planned for the future.
To add a node, simply click or drag the corresponding icon above the tree and enter a name and
API-Id. For Document Links you can select the document to be linked from the list on the bottom.
Folders and Document Links can be edited by right-clicking a node and selecting 'Edit'. This will bring up a dialog in which you can change the name, API-Id or the linked document.
Collections have their own configuration page. Right-click a node and select 'Edit' or enter the collection view by left-click and find the 'Configuration'-Button on the top right.
You can either right-click a node an select 'Delete', or switch into edit mode to delete a node.
Be careful when deleting a node, this will also delete the URL endpoint!
On the bottom of the Content Tree you will find the
Document Archive. It collects all archived
documents. In the archive you select documents to delete them permanently.