Silktide's integration with Adobe Experience Manager (AEM) helps you to streamline your website management process.
Here's a simple guide on how to get set up:
Supported versions
The Silktide AEM integration is currently available for:
AEM 6.4
AEM 6.5 (SP2+)
Installing the Silktide package
To connect AEM to Silktide, you'll need to install the Silktide package.
Download package
Obtain the relevant AEM package from Silktide, for your AEM version
Login to your AEM author instance
Make sure that your AEM account has permission to upload and install packages
Navigate to CRX Package Manager by clicking on Tools (the hammer icon on the far-left) > Deployment > Packages
Click on Upload Package and select the AEM package provided earlier
Click OK
Click on Install to open the installation modal
Click on the Install button
Check the log shows the installation was successful
Connect AEM to Silktide
Log into Silktide as an account administrator
Click on the user menu (top-right) and select Settings
Click on Integrations
Click New CMS
Select Adobe Experience Manager from the list provided and press Add
Make a note of the API key and Endpoint URL provided on the next screen. You will need to copy these into AEM
Login to AEM author instance with admin user account
Click on the Silktide icon from the Start page:
Enter your Endpoint URL and API key provided by Silktide:
Click Save
Silktide can now be used for all pages by default (you can override this below)
URL mappings
Two optional Silktide features require an additional configuration step. These are:
Deep link from Silktide directly into AEM to edit a specific page with an issue
Automatic re-testing of AEM pages when they are published
To configure this, please provide your Silktide Customer Success Manager with an example of the same page being edited and then being viewed on the public site.
Silktide needs to know how to translate between the private and the public URLs used by AEM.
For example, this editor URL:
http://localhost:4502/editor.html/content/we-retail.html
Maps to this public URL:
http://localhost:4502/content/we-retail.html
In this case, the transformation is very simple – Silktide simply removes or adds /editor.html from the path of the URL.
Advanced configuration
Enable/disable Silktide for specific pages
By default, the Silktide integration is enabled for all pages. You can change this as needed.
If you're ever unsure of the status of the Silktide integration, hovering over the Silktide icon while editing any page will show whether it is enabled or disabled.
To disable Silktide for a page or hierarchy of pages:
Login to the AEM author instance
Under Sites, find the page you want to modify
Select the page you want (click the thumbnail) and select Properties from the top navigation bar
Select the Silktide Integration tab
Select Disable from the dropdown option and leave the Override Parent Page Configuration unchecked
Save your settings
Silktide is now disabled for the current page and its child pages
To enable Silktide for a child page when it is disabled on its parent page:
Login to the AEM author instance
Under Sites, find the page you want to modify
Select the page you want (click the thumbnail) and select Properties from the top navigation bar
Select the Silktide Integration tab
Select Enable from the dropdown option and select Override Parent Page Configuration
Save your settings
Now, Silktide is enabled for the child page
Configure Silktide integration permissions
Silktide adds a new silktide-admin user group to AEM.
Users within the group have the ability to:
set the Silktide API key
configure which webpages the Silktide plugin applies to
In most cases, you can leave these settings alone, as AEM administrators will already have access.
If you need to grant a user permission to access these settings:
Login to AEM author instance with an admin user account
Navigate to Tools > Security > Groups
Search for the silktide-admin group
Select silktide-admin group from the results
Add any necessary users to this group