# Content Tree

The Content Tree helps to navigate a repos content and gives some structure to the backend. It can include [Collections](https://docs.comfortable.io/concepts-1/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.

{% hint style="info" %}
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.
{% endhint %}

## Node Types

The following types of tree nodes are available:

### Collections

`Collections` are aggregated lists of `documents` that match a certain definition. For more info, [see the collections page](https://docs.comfortable.io/concepts-1/collections).

![](https://1465026891-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LADWNm2iPQ4ngpcPfGc%2F-LAJZBXC5bK0UsqS8F20%2F-LAJZfeJ6tnzJMr_6_5k%2FScreen%20Shot%202018-04-17%20at%2019.06.36.png?alt=media\&token=efdda3b8-f143-4235-9d1b-1e23e9338894)

### Document Links

`Document Links` are single `documents` linked 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.

![](https://1465026891-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LADWNm2iPQ4ngpcPfGc%2F-LAJRZaNmTNmajt6baW7%2F-LAJWYKp2iwZci3QnnSR%2FScreen%20Shot%202018-04-17%20at%2018.52.56.png?alt=media\&token=d17b2470-74a7-480c-986d-a9148bfc437d)

### Folders

`Folders` can 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.

![](https://1465026891-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LADWNm2iPQ4ngpcPfGc%2F-LAJZyLZtS9PbKLt1JZr%2F-LAJ_Q4xHyZmwf9Jb-BY%2FScreen%20Shot%202018-04-17%20at%2019.09.50.png?alt=media\&token=5a967bdf-cb93-4cdc-95b7-58760c923d25)

## Nodes

### Adding nodes

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.

### Editing nodes

**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.

### Removing nodes

You can either right-click a node an select 'Delete', or switch into edit mode to delete a node.

{% hint style="warning" %}
Be careful when deleting a node, this will also delete the URL endpoint!
{% endhint %}

## Document Archive

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.

![](https://1465026891-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LADWNm2iPQ4ngpcPfGc%2F-LANiMOcs_lfUxrWrxoe%2F-LANiTjmrILG8pCpRWWh%2Farchive.png?alt=media\&token=d5715849-eb15-4c2c-9fbd-bb9f4f0783be)