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
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!
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.
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.
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.