Here is a list of the components that are included in the Salesforce Experience Bundle as well as a list of components that are NOT included in the bundle. Hopefully, this will give you a sense of what to include in your deployments.
The Salesforce Experience Bundle is a feature that allows you to package and deploy all the metadata related to a Salesforce Experience (formerly known as Salesforce Communities) site as a single bundle. This helps in managing and deploying changes to Experience Cloud sites. Here’s a list of the metadata components that are related to the Salesforce Experience Bundle:
BrandingSet: Represents the branding configuration for a Salesforce Experience.
CustomSite: Defines a custom site, which can include pages and associated resources.
ExperiencePropertyType: Represents different properties that can be customized for an experience.
NavigationMenu: Contains the navigation menus used in an Experience Cloud site.
Network: Represents the Experience Cloud site itself, including settings such as URL, site template, etc.
ObjectSearchSetting: Customizes search settings for objects in the experience.
Recommendation: Manages recommendations for users within the experience.
SiteDotCom: Represents a specific site in the Experience Cloud, containing all the pages and their components.
SiteRedirectMapping: Handles URL redirects within the experience.
Theme: Manages themes applied to the Experience Cloud site, including colors, fonts, and other branding elements.
UserCriteria: Defines criteria used to control user visibility for certain features in the experience.
ExperienceBundle: Contains the actual content of the Experience Cloud site, including pages, branding, and other components.
These components are essential for creating, customizing, and managing Salesforce Experience sites. When using the Experience Bundle, all these components can be included in a single package for easier deployment and version control.
Elements NOT Included In the Experience Cloud Bundle:
There are several Salesforce Experience (Experience Cloud) metadata components that are not included in the Salesforce Experience Bundle. While the Experience Bundle is a powerful way to package and deploy many of the components associated with an Experience Cloud site, some metadata types are managed separately and aren't included in the Experience Bundle. Here’s a list of some key metadata components related to Experience Cloud that are not part of the Experience Bundle:
CustomObject: Represents custom objects used in the Experience Cloud site, including their fields, relationships, and settings.
ApexClass: Contains Apex code, which might be used for custom logic within the Experience.
ApexTrigger: Contains triggers that might interact with objects used in the Experience Cloud site.
SharingRules: Defines sharing rules that determine record visibility within the Experience.
Profile: Manages user permissions and access controls, which are crucial for Experience Cloud users.
PermissionSet: Similar to Profiles, but more granular, allowing specific permissions for Experience Cloud users.
CustomMetadata: Used for managing custom metadata types that might be relevant to the Experience Cloud site.
CustomLabels: Used to store custom text labels that can be displayed in the Experience Cloud site.
WorkflowRule: Contains workflow rules that automate actions within the Experience.
Flow: Represents Lightning Flows that can be used to create guided processes for Experience users.
ApprovalProcess: Manages approval processes that might be invoked within the Experience Cloud site.
ConnectedApp: Represents apps connected to Salesforce, which can include Experience Cloud integrations.
EmailTemplate: Contains email templates used within the Experience Cloud site, often for notifications.
LightningComponentBundle: Contains custom Lightning components that might be used in the Experience Cloud site.
ContentAsset: Represents content assets such as images, documents, or videos that are used in the Experience.
CMSConnectSource: Manages connections to external content management systems (CMS) for content delivery in the Experience.
These components are essential for the full functionality of an Experience Cloud site, but they are not packaged within the Experience Bundle metadata type. They must be managed separately, often through their respective metadata types in Salesforce.