This document intends to define terms that are used across the project and the contexts in which they might be used in.
The generic implementation of the cotype backend. It's intended to be configured by a CMS.
A generic frontend that uses the admin API of the server.
A piece of software that configures the server for a specific use case.
The example CMS in this repository.
A model describes the shape of a data-set and holds meta information about it.
Models are used to configure the CMS.
The server has internal model types like settings and media but also supports content models that are defined by the CMS.
All custom models used to configure the server are of type "content". But the server also uses other types like "setting" or "media".
Unique name of a model, used to tie a data-set to a specific model.
A model of type "content". Which can be implicit since all custom models defined by the CMS are of type content.
Generic name for any data entity.
Same as model name but in the context of a data-set. A data-set has a type that connects it to a single model.
A content is a specific data-set that is modeled after one of the content models.
Alias for data-set type in the context of a content.
A setting is a specific data-set that is modeled after the servers internal setting model. Or in other words, a data-set with the modelType "setting".
A media entity is a specific data-set that is modeled after the servers internal media model. Or in other words, a data-set with the modelType "media".
Fields are defined by a model. When creating a data-set, the user of a CMS fills this fields with custom data.