Create a Content Type

A content type is a framework used to specify what information is included in a content item. You must be a content administrator to create content types and share them with others.

  1. Sign in as a content administrator in your browser and click Content under Administration in the left navigation menu.
  2. Select Asset Types from the drop-down menu.
  3. To create a new content type, click Create, then select Content Type.
  4. Enter a name for your content type.
  5. Edit the display name as needed. The display name is used in the user interface, for example, on the Assets page.
  6. Optionally, add a description to help users understand what this content type is used for.
  7. Click Create.
  8. Drag a data field into the content type definition.
  9. The settings page for the data field opens:
    • Enter a display name and optional description for your data field.
    • Optionally, edit the field name. This name must be unique.
    • If you selected text, media, or reference, select whether the field allows only a single value or multiple values and the number of values allowed.
    • Select if the field is required before the asset can be used.
    • If you selected text, large text, or embedded content, optionally provide a comment or note that provides additional instructions for the translator.

    If this content type will be used in digital asset repositories, configure these additional settings:

    • If you selected media or reference, select whether the dependent asset is always published with the parent asset or only when the dependent asset isn't already published.
    • Select if the field values should be inherited from the master type. For example, you may want a text field to display the company name or stock symbol as entered when a content item is created using this content type across all languages. Or you may want to prepopulate an image field to always use the approved company logo for all languages.


      When selecting Inherit from master, Do not translate is automatically selected. If editing a content type that has been used to create content items of different languages already, selecting Inherit from master causes the field values in the existing draft items to use the value in the master item. If the languages have already been published, then the preexisting value will remain in use until a new draft item of that language is published.
    • If you selected text, large text, or embedded content, select whether or not to translate the data entered into the fields. For example, a product description may be translated, but the product name or brand name might only be valid in the original language.
  10. On the appearance page for the data field, set what your data field will look like and if you want to apply any kind of validation. Each data field has different appearance values, such as validation, minimum or maximum length, the type of text editor to use (text area, rich-text editor, or markdown editor), or if the data needs to follow a particular pattern, such as a valid email address or zip code. For details on the available out-of-the-box data fields and their options, see Data Fields. You can also develop custom field editors.

    When you add a large text field and set the appearance to rich-text editor or markdown editor, you can select the type of toolbar: standard, basic, or custom. For the custom markdown editor, you select which buttons to include in the toolbar. For custom rich-text editor, see Customize the Rich-Text Editor Toolbar.

  11. You can group related fields to make it easier for contributors to work with content item forms.
    • To create a group, click Add Group, and then name the grouping. Drag data fields to the groups as desired.
    • Select whether you want the group to be expanded by default, collapsed by default, or hidden when viewed in the content item editor. For example, you might have mandatory fields that are in a group that is expanded by default and optional fields that are in a group that are collapsed by default, or you might need to edit a content type at some point to hide a group of fields that have become obsolete.
    • To edit a group name, click Edit group icon.
    • To delete a group, click Remove group icon. Select whether you want to remove the data fields along with the group, or if you want to move the data fields to another group.
  12. On the Friendly URL tab, you can enable a readable URL for content items created using this content type. This readable URL can be used as the slug value in calls to the REST API for Content Delivery.
    1. Select Enable friendly item name for URL to enable friendly URLs.
    2. If you're going to provide a custom prefix for the friendly URL and you want to include forward slashes in the prefix to create virtual path segments in the URL when items are displayed on the Detail page, select Allow forward slash.
    3. If you want to provide a custom prefix for the friendly URL, choose Provide custom prefix for item name from the drop-down list, and then enter your prefix in the text box.

    Content items created from this content type will have a friendly URL in the format <custom-prefix>-<content-item-name>. For example, if you enter marketing/blogs as the prefix and Fall 2023 is the name of the content item, the friendly URL would be


    • The prefix can't contain any of the following characters: " # % & : ; < > = ? @ [ ] \ ^ ` { } | ~ and / (unless you select to allow forward slash)

      If you allow forward slashes in your friendly URL, you must URL-encode the slashes when making an API call or the call will fail.

    • Spaces in the prefix and in the content item name are replaced with hyphens (-) in the friendly URL.
    • The friendly URL will be all lower-case.
    • You don't need to include a forward slash before or after your prefix. The forward slash before your prefix will be included automatically in the friendly URL. A hyphen (-) will be added between your prefix and the content item name.
    • Friendly URLs aren't created for items in business asset repositories, only items in digital asset repositories.
  13. On the Content Layout tab for the content type, select the layouts, editor, and preview formats you want to be available for this content type. When a content item is created using this content type, the person creating the content item will use the form you choose to enter the data for the content item and can preview how the content item will appear using any of the chosen layouts.
    • Site Builder layouts: (for use in digital asset repositories only) Choose desktop and mobile layouts for each layout style used in Site Builder. If the content item created using this type will be used on a website, the layouts should be created and uploaded prior to creating the content type.
    • Custom and precompiled layouts: (for use in digital asset repositories only) Add custom layout styles that can be published through the API and optionally used to publish HTML renditions for the published assets. See Manage Custom Components and Layouts.
      1. Click Add Layout Style.
      2. Enter a style name.
      3. An API name is automatically generated, but you can edit it as desired. The API name must be unique.
      4. Select desktop and mobile layouts.
      5. If you want to publish HTML renditions of the content in this layout when the asset is published, select Publish HTML. When the asset is published an HTML rendition of the asset will be created automatically. Repository administrators can also manually republish HTML renditions for all published assets of this asset type.
    • Default preview layout: Choose the layout to be used by default to view and preview content items of this content type in the web client.

      If you want asset users to preview these content items in a site page layout by default, you must first select the site page as described below and save the asset type. Then you can edit the asset type, return to the Content Layout tab, and the selected site page will appear in the default preview layout drop-down list.

    • Content item editor form: Choose the form to be used as the content item editor when adding or editing data for content items of this content type.
    • In-place and external site previews: (for use in digital asset repositories only) If you want the content item creator to be able to see what the content item will look like on a particular site page, select the Oracle Content Management-created site and page, or enter an external site and page URL. External URLs can include placeholders for id, type, language, and slug. For example,{id}/{type}/{language}/{slug} or{id}&lang={language}&type={type}&slug=(slug).
  14. On the Tile View tab for the content type, you can specify a custom tile view. Custom tile views let you configure how the data fields of content items are displayed on the Assets page, based on content type.
    • Under the Display area, select an option. In the available options, media data fields are represented by gray rectangles, title data fields are shown as thick gray bars, and text data fields are shown as thin gray bars.
    • Under the Configuration area, select the content type fields to be used for each piece of data shown in the tile view (title, text, media).
    • If you selected a tile view that includes a thumbnail, you can select Contain Media Thumbnail to scale the thumbnail so that the entire thumbnail is shown in the media area. Otherwise the thumbnail will be zoomed and cropped to fill the media area.
  15. For content types that will be used in digital asset repositories, control translation of standard data fields on assets of this type. By default, name and description data fields are translatable and will be included in the translation package when the asset is translated. On the General tab for the content type, configure the following settings:
    • If you don't want one of these fields to be translated, enable Do not translate, and the field value won't be sent in the translation package.
    • If you want all languages to use the value that is set in the master language for the asset, enable Inherit from master.

To view the content type's properties, click the additional properties pane.

You must associate the content type with at least one repository and grant users at least the contributor role on the repository so the content type can be used to create content items.