> For the complete documentation index, see [llms.txt](https://docs.uniqpath.com/dmt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uniqpath.com/dmt/configuring-devices/device-definition-files/content.def.md).

# content.def

\[ in progress ]

{% hint style="info" %}
This file is used to specify the **sets of paths** on the file system for sharing with your network.
{% endhint %}

### Example:

```bash
content:
  path: ~/Files
  path: ~/Desktop
```

### Advanced example:

This is an example with multiple root keys (notice they are all the same - `content: ...`)

{% hint style="warning" %}
It is invalid to have different root keys. It is a) **one** or **b)** multiple exact repetitions.

Each key can have completely different subkeys. We don't yet have `defsyntax` checker.

We also don't have `deflense` yet to map between different versions of **.def** files.
{% endhint %}

```bash
content:
  path: ~/Files
  
content: music
  path: ~/Music
```

{% hint style="info" %}
Unnamed **content** is *the default content*.
{% endhint %}

{% hint style="success" %}
Default content **is always public** and accessible to anyone with access of your node.
{% endhint %}

{% hint style="success" %}
Other types of content are more protected but this warrants a special section \[soon].
{% endhint %}

{% hint style="success" %}
If a folder is not listed in your **content.def** file it is not part of dmt data sharing logic.
{% endhint %}