Registering content types
Content types are registered from content type schemas that are either created using the schema editor and stored internally, or externally on a web based services such as AWS. Registering a content type and associating it with one or more content repositories makes it available for a user to use to create content.
The Dynamic Content app provides a user interface to make it easier to register and configure content types, including providing support for out of the box icons and content library cards.
In this section
The Register content type window
To register a content type, select "content types" from the development tab at the top of the Dynamic Content window. A list of content types registered to this hub will be displayed, with their label and their URL. To register a new content type click the "Register content type button".
To register a content type you need to provide the URL of a content type schema. Schemas can be created with the schema editor and stored with your Dynamic Content hub, or hosted externally on a service such as AWS or GitHub.
In this example the content type schema is hosted externally so we will select "external" and enter the external URL. If you click "internal" you will be able to choose from content type schemas created with the schema editor and stored with the hub.
See the schema editor section for more examples of creating and registering internal schemas.
Maximum length of URI
The maximum length of the content type URI is 950 characters.
Choosing an icon
You can add an icon to a content type by providing the URL to a 256x256 pixel image or choosing one of the standard icons. In this case we'll choose a simple picture icon.
Configuring a card
A card provides a graphical representation of a piece of content in the Content Library. This makes it easier for users to quickly identify a piece of content when viewing items of this content type in the Content Library.
You can provide the URL to your own custom card or choose from one of our out of the box cards, each providing a different way of representing your content. For this example we'll use the summary photo card. This will display an image with some text underneath.
Each card includes a number of configurable fields that determine how the card content should be displayed. You will map the chosen properties in your content type to the fields displayed on the content card.
For example, the banner type includes properties named "headline" and "background". We want the value of the headline property to be displayed on the card, so we enter "/headline" in the headline field and "/background" for the image.
When content of this type is shown in the content library, the background image will be displayed with the headline text underneath.
When your chosen card is configured, click the "Choose content type card" button to return to the main screen.
For more information about content cards, creating your own cards and mapping fields from linked content see the Cards page.
Enabling the content type on a repository
Before a content type can be used to create content, it must be enabled on at least one content repository. Choose the repositories on which you want to enable the content type from the list of available repositories in the "Associated repositories" section.
In this example there are just two repositories, one for content and one for slots, but each repository within the hub will be displayed. Once a content type has been enabled for a repository, it will be available to use to create content.
Registering slot types
Setting up visualizations
If you want to provide a visualization for the content type, click the "Add a visualization button" and enter the templated visualization URI in the field provided. Note that you must provide the complete URI, including all the templated variables. Give the visualization a label.
For more information about developing visualizations see the Visualizations page.
Completing the content type registration
Click Save to register the content type with the hub. If the content type is valid, then a message appears indicating that the content type has been registered. Note that an error message will also be displayed if the content type URL is the same as another content type already registered on this hub.
In the production view, the tutorial banner is now available from the content types window and can be used to create content.