Please enable JavaScript.
Coggle requires JavaScript to display documents.
Salesforce CMS in Experience Cloud - Coggle Diagram
Salesforce CMS in Experience Cloud
Salesforce CMS App: Is available in Lightning experience called "Salesforce CMS".
Visibility: To allow users to view this app, it must be set to "visible" in USER PROFILE.
Tabs can be made available by setting the tabs to "Default ON" in the TAB SETTINGS section.
To user SF CMS with Experience Builder Site, LIBRARIES in SALESFORCE FILES must be enabled in SETUP.
CMS Home: Can be used to access CMS Channels, workspaces, and experiences.
CMS Workspaces: Must be created first to create content, define content, access and define channels.
Folders: Can be created to organize content in CMS Workspaces.
Collections and Topics: Can be used to group and organize content in Experience Cloud site. This can be managed in Workspaces.
Adding Content: Once content is created, it can be added on Experience Cloud site by adding one the CMS components to a page.
Multiple languages can be added to a CMS Workspace and content can be translated using a localization partner.
Standard Content Types: Document, Images, News.
Custom Content Types: Can be created using MANAGED CONTENT TYPE in METADATA API. CMS CONTENT TYPE CREATOR can also be used. Ex: FAQ
Lifecycle of Content: Content can be SAVED AS DRAFT. It can be PUBLISHED. It can be EDITED as a new copy once published.
Storage Limits: Images and Documents count towards the org's storage limit but not the content record limits.
Domains used for URL links should be ALLOWLISTED to ensure that users can access the content.
Access Roles: can be assigned to all contributors to control access.
Chatter Rest API: To share content in SF Tabs + VF site, we have to use Chatter Rest API.
Experience Cloud CONTENT DELIVERY NETWORK (CDN) can be used to deliver CMS content to an Experience Site.
Roles
Salesforce Admin: has access to fill SF CMS App.
Content Admin (per workspace): Has access to all the content in the CMS workspace to which they have been added. They can also manage contributors and content sharing.
Content Manager: Has full access to all the content in a CMS Workspace.
CMS Channels: Can be created to share content in CMS Workspaces with other end points such as B2C commerce, B2B commerce, Heroku etc.
Schedules: CMS Content schedules can be created to publish and unpublish at required dates and times.
Adding Content on Site
CMS Content Page: Add it as a new page in Experience Builder by selecting CMS Content as the page type.
Single Item or Collection can be added to a page by selecting CMS Single Item Component or Collection Component.
Audience targeting can be done by setting page variations for content pages.
Translation: Content to be translated need to be translated by a localization partner and then it can be imported and published.
Content Export/Import: Content can can be transferred from one org to another using import and export features. Upto 5000 items can be imported at the same time. It is exported in .zip archives of JSON files.
CMS Connect
CMS Connect: A CMS Connection needs to be created in WORKSPACES to connect a CMS with Experience Cloud site.
Personalized content from Adobe Experience Manager (AEM) can be connected to an Experience Cloud site using CMS Connect. It can also connect with Drupal, Sitecore, Wordpress.
This is a tab in EXPERIENCE BUILDER SETTINGS where you can setup CMS Connection. Also available in WORKSPACES --> CONTENT MANAGEMENT --> CMS CONNECT.
CMS SOURCE and CONNECTION TYPE needs to be specified while creating a CMS connection.
Personalization
Criteria based display: Can be done by using criteria like geolocation.
Personalization can be enabled when creating or editing CMS Connection by selecting "USE PERSONALIZATION". It requires CONNECTOR PAGE PATH which is the path to the JSP file in AEM.
Headers and Footers can be personalized from EXPERIENCE BUILDER Settings.
CMS Component can be personalized by accessing the properties in EXPERIENCE BUILDER.