If you want to create a modified version of a content type, open the content type and click Duplicate in the top right. This creates a duplicate of your content type named “Type_name (copy)” in the project.
Set elements as required
By default, each element you add is optional. If you set the element as required, content creators will know which elements they need to fill in when working with content items.
Set default value for elements
By default, all elements are localizable. This means they can have different values in each language.If you want an element to have the same value across all languages, mark the element as non-localizable. If you later change your mind, you can convert the element back into a localizable one.If you mark an element as both non-localizable and required, the element must be published in the default language first.Content creators can edit non-localizable elements only in the default language. In other languages, non-localizable elements take the value from the default language and appear as read-only.
Limitations for non-localizable elements
Only newly added elements can be marked as non-localizable.
Rich text elements cannot be marked as non-localizable.
You can remove any element from a content type at any time, even when a content item uses the content type.
Codenames identify objects, such as content types, in Kontent.ai. A codename is initially generated by the system from the object's name when it is saved for the first time.You can edit codenames in the UI by clicking the button and then the button or via API by, for example, see modifying a content type.
Rules for codenames
Delete content types
If you want to delete a content type that is already used for any components or content items, you need to delete the content items first.To delete a content type:
In Content model, use the checkboxes to select the content types you want to delete.
The content type is now removed and cannot be restored.
Limit role access to elements
When you have multiple contributors accessing your content items, it's best to limit their access to specific elements by using content groups based on their roles. For example, in an article content type, a content creator can access only the content body, while an SEO specialist can access the metadata settings.To set role-based limitations:
When editing codenames, the new codenames must meet the following conditions:
Only lowercase letters, numbers, and underscores are permitted.
Codenames must start with a letter or an underscore and have at least one character.
Codenames are usually limited to 60 characters, but longer codenames are allowed for multiple choice options and taxonomy terms.
Codenames of elements within a snippet must be prefixed with the snippet's codename.
Codenames must be unique per object type. This applies to, for example, every element within a content type, every content type within an environment, every content item within an environment, and so on.
This means the following applies when codenames are generated automatically:
All letters are made lowercase.
All forbidden characters are replaced by _.
For any names that start with a number, the codename will start with n.
Codenames that duplicate another codename will have a random string attached to the end.
Codenames of elements within a snippet will be prefixed with the snippet's codename.
Codenames will be cut off at the character limit.
An example of how the role is configured to access certain content groups of a content type.
Localizable elements can’t be turned into non-localizable ones.Once an element is saved as localizable, the setting becomes irreversible. A localizable element cannot be turned into a non-localizable one. Let us know using the chat button in the bottom left if changing this setting for existing elements is a priority for you.
This action is not reversible. Removing an element from a content type removes the element across all content items with all its data.