Lightning Communities Developer Guide

Get Up to Speed with Lightning Communities
Develop Lightning Communities: The Basics
Customize the Look and Feel of a Lightning Template
Example: Build a Condensed Theme Layout Component
Develop Secure Code: Locker Service and Stricter CSP
Analyze and Improve Community Performance
Connect Your Community to Your Content Management System
Before Using CMS Connect
Create a CMS Connection
Edit a CMS Connection
Manage CMS Connections
Add CMS Content to Your Community Pages
Personalize Your CMS Content
CMS Connector Page Code
CMS Connect Recommendations for Optimal Usage
CMS Connect Examples
Report on Deflections: The Deflection Signals Framework
Deploy a Community from Sandbox to Production
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Personalize Your CMS Content

CMS Connect supports content from Adobe Experience Manager (AEM) that is personalized using Client Context. If you have content in AEM that is personalized using Client Context, you can enable personalization in your community so you decide who sees what. Personalization in CMS Connect lets you keep the branding and other personalized content consistent between your community and your website. Render content according to different segments of users, based on criteria such as geolocation or language.

Some upfront effort is required to get personalization working in your community. You need to create and install a connector JSP page and expose it through an HTML page in AEM. The connector page contains the JSP with your website's personalization mapping logic. We provide the code for it in CMS Connector Page Code. You might need to add some code, depending on how you want to run scripts. Then provide the path to this connector page in AEM when you’re setting up the CMS connection in your community. In your CMS connection, you can also add a path to your JavaScript file if you want to run scripts dynamically inside the JSP file.

Ready to get started? Let’s dig in. (Take a power nap first, if you need to.)

Set Up Personalization and the Connector Page in AEM

  1. If you haven’t done so already, set up personalization using Client Context in AEM.
    • Create personalization rules based on your segments and what you want them each to see. Create an experience for each segment.
    • Determine which personalized content you want to host in your community. Each component in AEM has a default URL. Make a list of these URLs, along with the components they’re for. You’ll need these when you set up your CMS connection.
  2. Use the CMS connector page code to create a connector JSP page and expose it through an HTML page in AEM.

Enable Personalization in Your CMS Connection

  1. Create a CMS connection (or edit an existing one) where you want to host your personalized content.Personalize CMS Connection
  2. Enable Use Personalization.
  3. In Connector Page Path, enter the path to the connector JSP page you installed in AEM.
  4. If you want your personalized content to run scripts dynamically, enter the path to your JavaScript file in Script Path.
  5. Click Save.

Enable Personalization in Your Page Components

  1. Navigate to Community Builder.
  2. To personalize a header or footer, click Builder Settings and select Settings. Select CMS Connect. (Skip this and the next step if you don’t want to use a personalized header or footer.)CMS Connect Builder Settings
  3. In Header Source and Footer Source, choose the name of the connection that contains the personalized content. In Header Path and Footer Path, enter the Default Experience URL from AEM for the header and footer components. Append .html to default URLs copied from AEM. Enable Use Personalization for the header and footer.
  4. To personalize content on a community page, drag a CMS Connect (HTML) component to your page (or edit an existing one). In the component’s property editor, choose the connection name in CMS Source. In Component Path, paste the Default Experience URL for the component from AEM. Append .html to the component path since it’s not included in the path in AEM.Personalization in Builder
  5. Voilà! Repeat these steps for any additional components you want to personalize.