Content section consists of 9% of total score in the Salesforce Community Cloud Consultant certification exam, covering topics such as CMS Connect, content, Chatter questions and Chatter group, Communities Search and translating a Community. Without further ado, lets get started!

Guideline for Content

  • Explain the capabilities of CMS Connect.
  • Identify the methods to personalize content for users.
  • Explain the capabilities of Chatter questions and Chatter groups.
  • Describe the capabilities of Communities Search.
  • Describe the process for translating a Community.

CMS Connect


  • CMS stands for Content Management System.
  • CMS Connect can be used to connect a third party CMS to community.
  • CMS Connect supports connecting CMS components such as HTML, CSS, Javascript, JSON and personalized content from Adobe Experience Manager (AEM), Drupal, Wordpress and etc.
  • Create a new CMS Connection:
    • Name
    • CMS Source
      • AEM
      • Drupal
      • Wordpress
      • SDL
      • Sitecore
      • Other
    • Connection Type
      • Public
        • Server URL
      • Authenticated
        • Named Credentials
    • Root Path
    • Use Personalization
      • Connector Page Path
      • Script Path
    • Add CSS (up to 10 CSS URLs)
      • Scope
      • CSS URL
    • Add Scripts (up to 10 Javascript URLs)
      • Script URL
    • Add JSON (up to 5 JSON connections to retrieve content from CMS)
      • Content Type Name
        • Add Content Item
          • Name
          • Path - relative path to the content
          • ID Path - field name or path to use as the unique identifier for this Content Item
          • Title Path - field name or path to display as the title for this Content Item
        • Add Content List (multiple)
          • Name
          • Path - relative path to the content
          • Node Path - start Node path to the content
    • Enable language mapping
    • Add Language
      • Salesforce Language
      • CMS Language
  • Set CMS Connect Header and Footer in Experience Builder > Settings > CMS Connect:
  • Add the CMS Connect component on the page:
  • The content for this part is not complete. Just briefly know what it is should be fine.

Content Personalization

  • Audience Targeting can be used on:
    • Page Variations
      • Priority can be set if the page contains more than 1 target audiences:
      • The page will display a banner on top of the page indicates that the page is for targeting audience only:
      • Learn more about Page Variations
    • Components
      • When a component has set target audience, the page will display a banner on top of the page indicates that the page contains components specific for targeting audience.
    • Branding Sets

Salesforce CMS

-Salesforce CMS is a hybrid content management system, where you can curate and share content, manage multiple language versions of your content, and control who creates what.

  • Use Salesforce CMS to create, manage, and deliver content from a central location, and then share that content across multiple channels.

  • Salesforce CMS Pricing:

  • Get Started with Salesforce CMS:

  • Create CMS Workspace steps:

    1. Set Name and Description
    2. Add Channels:
    3. Add Contributors:
    4. Assign Roles (Content Admin or Content Manager) to Contributors:
    5. Add Languages:
    6. Review and finish!
  • Add Channels can be used to add additional channels:

    • NOTE: once Channel is added, it cannot be removed.
  • Likewise, Add Contributors can be used to add additional contributors with roles:

    • NOTE: once Contributor is added, it cannot be removed.
  • Likewise, Add Languages can be used to add additional languages:

  • Create Content as Draft:

  • Ready for Translation can be used to update the status of your draft to Ready for Translation.This version will no longer be editable.

  • All of your contents can be viewed in your CMS Workspace:

  • Export for Translation can be used to export the contents for translation:

    • You will receive an email with the link to the file:
  • The output file is a zip file with .xlf extension. Feel free to use any tool or editor to modify the files.

  • Example of .xlf file:

<?xml version="1.0"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en-US" trgLang="zh-CN" xmlns:fs="urn:oasis:names:tc:xliff:fs:2.0">
 <file id="0cw3s0000004C93">
  <unit id="00000013">
    <source>First Content</source>
  <unit id="00000014">
    <source>First Content</source>
  <unit id="00000015">
    <source><pc id="0" fs:fs="p">First Content is created!</pc></source>
  • Once you have done editing the xlf files, archive them into a zip file.
  • Import Translated Content can then be used to import the translated content zip file back to workspace.
  • You can find the translated contents in Translation tab:
  • As for the final step, click Publish the content:
  • Edit as Draft can be used if you need to edit the content. Bear in mind that it will create a copy of currently published item to work with as a draft.
  • Content Types:
    • News - add news article with rich text and image support
    • Image - add media files, such as PNG or JPEG, or link to a URL
    • Document - add content using any file type or an external URL
    • Custom Content Types - create using Metadata API
  • CMS Collection can be created to group CMS Contents:
  • You can add CMS Collection component or CMS Single Item component into the community page.

Chatter Questions and Chatter Groups

  • Chatter Questions:
    • Chatter Questions can be used to promote engagement with members in the community.
    • Users can ask questions in:
      • Chatter Feeds
      • Groups
      • Users
      • Records
      • Searches
    • Question-to-Case can be enabled in Setup > Support Settings (classic only).
    • Answer can be selected as Best from the question by moderators or the person who asked the question.
    • Best answer will have a Green check mark with "Selected as Best" next to it.
    • Similar questions and knowledge articles can be displayed when the user types a question.
  • Chatter Groups:
    • Chatter Groups can be created to allow collaboration with community members.
    • The option to Allow Customer does not need to be selected when creating the group.
    • Navigation Menu can add Group as a menu item for customers to access the groups easily.
    • Groups can be Public, Unlisted or Private.

Communities Search

  • Communities Search is a very powerful search tool to search for related contents, such as Discussions, Cases, Knowledge, Accounts, and etc.
  • Search and Global Search for Peer-to-Peer Communities component allows autocompleting search and suggest matching Articles, Discussions, Cases and etc.
  • Global Search Results component can be used to display the search results:
  • Some search features:
    • Understand different forms of search terms, ex: hello <-> hi, howdy <-> how are you, etc.
    • Spelling auto-correction, ex: 'afiliate' -> 'affiliate', 'seach' -> 'search', etc.
    • Search on metadata, ex: search for the content of PDF files
    • Search with defined synonym group, ex: 'computer' = 'pc'

Translation a Community

  • Multiple languages can be set in community.
  • URL Parameter ?language={language_code} can be used to set the default language for the community.
    • Example: ?language=zh_CN to change the language into Chinese
  • Language Selector component can be used to witch the community language
  • Google Cloud Translation can be used to translate on all feed items in community, such as posts, questions, comments, replies and etc.
  • Some components are not translatable, hence requires manual work by switching the language and retype the translated content in the selected language.
  • Import Translation and Export Content from Experience Builder > Settings > Languages can be used to send a language content file to a translation service.
  • Export Content in .xml file:
  • Modify the .xml file to include the translation:
<?xml version="1.0" encoding="utf-8"?>
<languagedata exporttimestamp="1592189504547" version="1.0">
	<component context="Seo Assistant (Aura)" id="2351251b-3416-40c8-9eb1-325b204c6664">
		<field name="AuraAttributes" language="zh_CN" exportcrc="4146036844">
			<property name="metaTags"><![CDATA[]]></property>
			<property name="description"><![CDATA[]]></property>
			<property name="title"><![CDATA[测试页面]]></property>

NOTE: You need to replace the text to be replaced part in <![CDATA[Text to be replaced]]>, if it is empty <![CDATA[]]> like this, you don't need to add translated text because it probably will not display on the screen either.

  • Import Translation by drag and drop the translated .xml file:
  • Translation Workbench can also be used to translate components such as navigation menu items, reputation levels, managed topics and etc.
  • Enable Translation Workbench in Setup > Translation Language Settings:
  • Add the language that needs to be translated:
    • NOTE: the user must have 'View Setup and Configuration' permission to translate.
  • Navigate to Setup > Translation Workbench > Translate, select the setup component to begin translation:
  • Check out the translated topics in Chinese language:
    • NOTE: for those fields that are not translated, you can translate them by the component properties (mostly):

That's all about it, we are almost there! See you in next post!

Post was published on , last updated on .

Like the content? Support the author by!