---
schema_version: "1"
id: 2a5b21414ee5ab41e7c46abf497a535a132674f4d997aa8260d7bf38e2032267
title: ManagedTopics
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_managedtopics.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_managedtopics.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 376ecdd847dabd6b21825aa5bfe4aa4cca1f6d4a787585a1e247fa0c9c4e9910
description: Represents navigational and featured topics managed in an Experience Cloud site.
---
# ManagedTopics

Represents navigational and featured topics managed in an Experience Cloud site.

![Note](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note.png)

#### Note

The related Experience Cloud site must exist before you deploy managed topics. (This occurs automatically when deploying an entire org.)

## File Suffix and Directory Location

Components have the suffix managedTopics and are stored in the managedTopics folder. In that folder, you find separate files for each Experience Cloud site (for example, SiteNameA.managedTopics and SiteNameB.managedTopics).

## Version

ManagedTopics components are available in API version 32.0 and later.

## Fields

| Field Name | Field Type | Description |
| --- | --- | --- |
| ManagedTopic | [ManagedTopic](#ManagedTopic_title) | Represents a specific navigational or featured topic. |

## ManagedTopic

<table class="featureTable sort_table" summary="">



          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d652124e140">Field Name</th>

              <th class="featureTableHeader  " id="d652124e143">Field Type</th>

              <th class="featureTableHeader  " id="d652124e146">Description</th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d652124e140" data-title="Field Name"><span class="keyword parmname">name</span></td>

              <td class="entry" headers="d652124e143" data-title="Field Type">string</td>

              <td class="entry" headers="d652124e146" data-title="Description">The topic name.</td>

            </tr>

            <tr>
              <td class="entry" headers="d652124e140" data-title="Field Name"><span class="keyword parmname">managedTopicType</span></td>

              <td class="entry" headers="d652124e143" data-title="Field Type">string</td>

              <td class="entry" headers="d652124e146" data-title="Description">The topic type: “Navigational” or “Featured”</td>

            </tr>

            <tr>
              <td class="entry" headers="d652124e140" data-title="Field Name"><span class="keyword parmname">topicDescription</span></td>

              <td class="entry" headers="d652124e143" data-title="Field Type">string</td>

              <td class="entry" headers="d652124e146" data-title="Description">An optional description of topic contents. This field is
                accessible only via the API; there is no corollary in the user
                interface. </td>

            </tr>

            <tr>
              <td class="entry" headers="d652124e140" data-title="Field Name"><span class="keyword parmname" id="parentName_field"><a name="parentName_field"><!-- --></a>parentName</span></td>

              <td class="entry" headers="d652124e143" data-title="Field Type">string</td>

              <td class="entry" headers="d652124e146" data-title="Description">
                <span class="ph" id="parentName_desc1"><a name="parentName_desc1"><!-- --></a>The name of a parent topic for which
                  this topic is a child. Child topics are accessible from the
                  subtopics section of the parent topic page and their feeds are
                  added to the parent topic feed.</span>
                <p class="p"><span class="ph" id="parentName_desc2"><a name="parentName_desc2"><!-- --></a>Only navigational topics support parent-child
                    relationships.</span></p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d652124e140" data-title="Field Name"><span class="keyword parmname">position</span></td>

              <td class="entry" headers="d652124e143" data-title="Field Type">int</td>

              <td class="entry" headers="d652124e146" data-title="Description">The placement of this topic relative to others of the same type.
                The results differ depending on topic type:<ul class="ul bulletList">
                  <li class="li">For top-level navigational topics,
                    <span class="keyword parmname">position</span> arranges the Topics menu
                    in the Experience Cloud site.
                  </li>

                  <li class="li">For child navigational topics, it arranges sibling topics in
                    the subtopics section.</li>

                  <li class="li">For featured topics, it arranges topic thumbnail images on
                    the Experience Cloud site home page.</li>

                </ul>
                <p class="p">Enter a number between 0 and 24. (The maximum amount of
                  navigational or featured topics is 25.)</p>
              </td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following example retrieves or deploys managed topics for all sites:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>\*</members\>
        <name\>ManagedTopics</name\>
    </types\>
    <version\>32.0</version\>
</Package\>

The following example shows a package.xml file referencing the ManagedTopics component:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>SiteName</members\>
        <name\>ManagedTopics</name\>
    </types\>
    <version\>32.0</version\>
</Package\>

The following example shows the ManagedTopics component itself:

<?xml version="1.0" encoding="UTF-8"?>
<ManagedTopics\>
    <ManagedTopic\>
        <name\>Running</name\>
        <managedTopicType\>Navigational</managedTopicType\>
        <topicDescription\>Training advice</topicDescription\>
        <parentName\></parentName\>
        <position\>0</position\>
    </ManagedTopic\>
    <ManagedTopic\>
        <name\>Hiking</name\>
        <managedTopicType\>Navigational</managedTopicType\>
        <topicDescription\>Routes and gear</topicDescription\>
        <parentName\></parentName\>
        <position\>1</position\>
    </ManagedTopic\>
        <ManagedTopic\>
            <name\>Trails</name\>
            <managedTopicType\>Navigational</managedTopicType\>
            <topicDescription\>Maps for local favorites</topicDescription\>
            <parentName\>Hiking</parentName\>
            <position\>0</position\>
        </ManagedTopic\>
        <ManagedTopic\>
            <name\>Backpacks</name\>
            <managedTopicType\>Navigational</managedTopicType\>
            <topicDescription\>Recommended models</topicDescription\>
            <parentName\>Hiking</parentName\>
            <position\>1</position\>
        </ManagedTopic\>
    <ManagedTopic\>
        <name\>Footwear</name\>
        <managedTopicType\>Featured</managedTopicType\>
        <topicDescription\>Suggested types for each sport</topicDescription\>
        <parentName\></parentName\>
        <position\>0</position\>
    </ManagedTopic\>
    <ManagedTopic\>
        <name\>Conditioning</name\>
        <managedTopicType\>Featured</managedTopicType\>
        <topicDescription\>How to get fit for any activity</topicDescription\>
        <parentName\></parentName\>
        <position\>1</position\>
    </ManagedTopic\>
</ManagedTopics\>

## Usage

Managed topic images that are uploaded in API version 50.0 and later are stored as asset files. To migrate managed topic images that are uploaded in API version 50.0 and later, use the ContentAsset metadata type. To migrate managed topic images that were uploaded in API version 49.0 and earlier, use the Document metadata type.

## 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).