Connect Your Content Management System (CMS) to Your Community (Beta)

Is your company’s website built in Adobe Experience Manager (AEM)? CMS Connect lets you bring your AEM content, such as headers, footers, and banners, into your community. Dynamically render your components, CSS, and JavaScript on community pages for consistent branding, authentication, and ease of maintenance. CMS Connect is available in communities that are based on Customer Service (Napili), Partner Central, and any Lightning Bolt solutions.

A Whole New Workspace

Look no further than your Community Workspaces to get started with CMS Connect. (Not using the new Community Workspaces yet? Just go to your Community Settings in Setup to enable it.)

Serving All Servers

Got multiple AEM servers? You can connect them to your community. Set their load order according to their dependencies on each other. Load order is mostly relevant for CSS and JavaScript.

Streamlined Paths

Component Paths

When setting up a CMS connection, enter the root path for the directory where components are stored on your AEM server. This saves time later when adding components in the Builder. You can include placeholders in your path for language and component.

Header and Footer Paths

Enter paths to your header and footer in Settings in Community Builder so that you don’t need to add them to each page. Add them once and you’re good to go!

Language Support

We provide language mapping for your AEM connections, so you can display your content in multiple languages. Add all your languages when setting up a connection. For each Salesforce language you add, enter the name of the corresponding language directory from AEM.

CSS and JavaScript

You can include CSS and JavaScript from your CMS. Add up to 10 of each per connection. If your CSS is scoped, you can specify that to prevent rule collision with other CSS on your community pages.

If You Build It, They Will Come

After your CMS connection is set up, you’re ready to use it in Community Builder. Drag a CMS Connect component to your page, and add the source and component path in the property editor. Your community will soon be looking consistent with your website, with very little effort after the initial configuration.

Note

CMS Connect requires an HTTP server that can serve HTML fragments. All URLs in HTML fragments must be absolute URLs. All connected CMS servers must be accessible via HTTPS to retrieve HTML and JavaScript. Not all tags are supported. See the product documentation for details.

This release contains a beta version of CMS Connect, which means it’s a high-quality feature with known limitations. CMS Connect isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. We can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.