Properties make up the structure of a content type. They define what kind of information each entity of that type can hold. A property has a name, an icon, a type and a type.
There are three groups of properties: default properties, normal properties, and type-specific properties.
Default properties are properties that every content type has, no matter what. Under the hood, they will always be there, even if they are not shown in the list of properties for a content type. For your custom content types you can have them displayed by adding them as a property from the property dropdown.
This is the list of all default properties.
- Title The title of an entity. It is a plain text property. The title is quite important for search, so giving your content a meaningful title can help you to access it more quickly.
- Created at
These properties can be used by the user and are also used to construct some properties of the basic content types as well.
A plain text property without any formating.
A simple number property (no currency or unit formating supported yet).
A simple checkbox property that can either be checked or unchecked.
A blocks property that can hold any kind of blocks-based content.
A date property that can be extended to include a time.
🚧 Work in progress
Single select: Allows linking to one entity of a specified type as the content of this property (Capacities will display all options for other types directly in the dropdown with the label
Multiple select: Allows linking several entities of a specified type as the content of this property (Capacities will display all options for other types directly in the dropdown with the label
We use these specific properties to add specific data or functionality to our basic content types. The file resource property of an image (or other media types) that holds the reference to the actual file and shows a download button in table view is an example for that.
🤔 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!