Capacities is a very flexible tool in terms of content organization. But all the options can be a bit confusing in the beginning. Here's an overview:
There is an object database for each type of content. This gives you a base-level organization by content type out of the box.
In the object database, there are two main views: "Dashboard" and "All". While the "All" view simply shows you all objects of this type, the "Dashboard" view provides sections such as Collections of that type, "Inbox" and "Last edited".
You can see all your objects in the left side bar in the "Objects" section.
A collection can be useful to create a curated set of objects of the same type. This, is for example, great for sharing.
Collections can also be fully embedded in other objects (such as pages). Go to the place where you want to embed it and inside of an empty text block simply type @ followed by the exact name of the collection. When embedded, they get a new set of sorts and filters which is only applied locally. This way you can create dashboards of different collections with individual sorts and filters applied.
Read our tutorial about databases and collections to learn how to use those in practice.
A tag is content type with
- a title,
- a color,
- an optional description,
- and an optional icon.
Tags are used to categorize objects. Any object can be tagged. If you visit the tag page, all tagged content will be displayed using one of the data views:
In addition, sorts and filters can be applied. Tags can also be fully embedded in other objects (such as pages). When embedded, they get a new set of sorts and filters which is only applied locally. This way you can create dashboards of different tags with individual sorts and filters applied.
The tag page also shows the most relevant related tags based on common connections with the content. This allows you to quickly navigate to related topics.
Read our tutorial about tags to learn how to use those in practice.
🤔 Do you find this explanation unclear or feel like something is missing in the docs?
With your help we can make the docs better for everyone. So just let us know, and we’ll improve it ASAP!
📨 Did reading the docs make you think of any product improvements?
Please let us know if you have an idea for a feature, think that something is missing or see a conceptual inconsistency that could be fixed. Just post it on our feedback board and discuss it with us and other users!