--- schema_version: "1" id: dc0537cc6e3be6203d9d796a4351f985d4c9dc051436bf03503ff3c41e476b2d title: ManagedContentType collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_managedcontenttype.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_managedcontenttype.htm source_site: developer.salesforce.com content_type: documentation content_hash: d58c3c42ee20ce5773c09ab3693459c1bb78b742e6411d511f0a1c4be84ada5a description: Represents the definition of custom content types for use with Salesforce CMS. Custom content types are displayed as forms with defined fields. --- # ManagedContentType Represents the definition of custom content types for use with Salesforce CMS. Custom content types are displayed as forms with defined fields. This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") metadata type and inherits its fullName field. ![Important](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note_important.png) #### Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations. ## File Suffix and Directory Location ManagedContentType components have the suffix managedContentType and are stored in the managedContentTypes folder. ## Version ManagedContentType components are available in API version 47.0 and later. ## Special Access Rules ManagedContentType is only available if Salesforce CMS and digital experiences are enabled for your org. ## Fields | Field Name | Field Type | Description | | --- | --- | --- | | description | string | Describes the custom content type defined in this ManagedContentType declaration. | | developerName | string | Required. Unique name for the custom content type. For example: OurSpecialContent\_c | | isMetadataContent | boolean | When true, any content created from this content type is converted to metadata. Default value is false. Availabe in API version 63.0 and later. | | managedContentNodeTypes | [ManagedContentNodeType](#managedContentNodeType)\[\] | Nodes included as part of this custom content type. When rendered as a form in the Digital Experiences app, each node is represented as an individual field. | | masterLabel | string | Required. Declares the name of the content type as it appears in the UI. | ## ManagedContentNodeType Represents the structure of individual nodes within the custom content type.
Field Name Field Type Description
helpText string Provides assistive text in the UI, displayed as an info bubble for the field. If this field is empty, no info bubble icon or text is displayed.

For example: <IMG?>
isLocalizable boolean Declares a field as localizable and consumable by <loc MDAPI reference> (true) or not (false). Default is false.
Note

Note

NodeTypes IMG, URL, DATE, and DATETIME can’t be localized.

isRequired boolean Declares a field as required (true) or not (false). Fields declared as required are indicated by a red asterisk. If a value isn’t added to the field in the custom content type, the form can’t be saved and a standard error is displayed. Default is false.
Note

Note

When nodeType is set to NAMEFIELD on a field, isRequired must also be set to True for that field.

nodeLabel string Required. Declares the label for the field as it appears in the UI.

In enhanced workspaces, the system generates a Title field by default. To prevent having multiple Title fields on the UI when you create a custom content type for use in an enhanced workspace, don't use Title as the label for nodeLabel.

nodeName string Required. Unique name of the nodeType within the content type. nodeName is a simple text field that allows up to 100 alphanumeric characters and underscores. The name must begin with a letter, not include spaces, can’t have two consecutive underscores, and can’t end with an underscore.

In enhanced workspaces, the system generates a Title field by default. To prevent having multiple Title fields on the UI when you create a custom content type for use in an enhanced workspace, don't use Title as the label for nodeName.
nodeType MCNodeType (enumeration of type string) Required. Identifies the supported type of content in the node. Passed as a string. There’s a maximum of 15 node types per content type. Values are case insensitive but are returned in all capital letters as shown. Valid values are:
  • TEXT

    Simple text node (max length=255 characters)

  • MTEXT

    Multi-line text node (max length=2000 characters)

  • RTE

    Rich text node (max length=65536 characters)

  • IMG

    Image node

    Note

    Note

    IMG node types can’t be localized. Set isLocalizable to false for images.

  • URL
    URL node (max length=255 characters)
    Note

    Note

    URL accepts protocol string values starting with http://, https://, mailto:, tel:, and /.

    Note

    Note

    URL node types can’t be localized. Set isLocalizable to false for URLs.

  • DATE

    Date node

    Note

    Note

    DATE accepts dates only in the format yyyy-MM-dd.

    Note

    Note

    DATE node types can’t be localized. Set isLocalizable to false for dates.

  • DATETIME

    Datetime node

    Note

    Note

    DATETIME accepts date and time in the format: yyyy-MM-dd'T'HH:mm:ss.SSS'Z' (UTC datetime in ISO 8601 format).

    Note

    Note

    DATETIME node types can’t be localized. Set isLocalizable to false for datetime notes.

  • NAMEFIELD
    Note

    Note

    NAMEFIELD declares the field as the name that represents the content when referenced in the UI. For example, text entered in this field displays as a list of available content in the Digital Experiences app or as a piece of content available for inclusion in a collection in an Experience Cloud site.

    One, and only one, nodeType in your managed content type must be declared as NAMEFIELD. NAMEFIELD is a string of 200 characters or fewer.

    In enhanced workspaces, the system generates a Title field by default. To prevent having multiple Title fields on the UI when you create a custom content type for use in an enhanced workspace, don't use Title as the label for nodeName or nodeLabel for the NAMEFIELD node. If you've already named nodeName Title, choose a different label for nodeLabel to prevent confusion on the content creation page.

    When NAMEFIELD is used, isRequired must also be set to true for the field.

placeholderText string Provides assistive text in the UI, displayed as placeholder, or ghost text, in a field before any entry is made. For example, Enter a title for your article...
## Declarative Metadata Sample Definition The following is an example of a ManagedContentType component. myContentType My Content Type This is the description for my content type title Content Title NAMEFIELD Placeholder Text for title Help Text for title true true textnode Content Text TEXT Placeholder Text for Content Text Help Text for Content Text true false richtextnode Content RichText RTE multilinetextnode Content MultilineText MTEXT imagenode Content Image IMG ## Usage For each custom content type you create, there must also be a CMS Content page created in any Experience Cloud site that displays the content. Each Content page serves as the detail page for all content of a single content type. See [Create Custom Pages with Experience Builder](https://help.salesforce.com/articleView?id=community_builder_create_page.htm&type=0&language=en_US). ## Wildcard Support in the Manifest File This metadata type supports the wildcard character \* (asterisk) in the package.xml manifest file. For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).