AEM CMS Plugin Technical Details

Modified on: Thu, 5 Nov, 2026 at 8:58 PM

Summary

The Siteimprove AEM CMS plugin uses the repository paths and clientlib categories listed below. Its overlay is rendered only in /editor.html and /cf# when a cloud configuration is assigned to the current path or the current path matches the configured active paths; integration with editor.html uses an addition to the headerbar to avoid conflicts with the AEM edit-mode overlay.

Affected repository paths

/apps/siteimprove-packages
/apps/siteimprove/plugin
/apps/granite/ui/content/globalhead/siteimprove
/apps/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/toggleContentCheck
/apps/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/siteimprovePlugin
/apps/wcm/core/content/editor/jcr:content/content/items/content/content/items/siteimprovecontentcheckresult
/etc/cloudservices/siteimprove
/conf/global/settings/siteimprove
/conf/global/settings/workflow/models/siteimprove
/var/workflow/models/siteimprove
/home/users/system/siteimprove
/home/groups/s/siteimprove
/rep:policy

Removing old sample workflow locations, have been relocated

/conf/global/settings/workflow/models/si-test
/var/workflow/models/si-test
/conf/global/settings/workflow/models/si-unpublishcheck
/var/workflow/models/si-unpublishcheck

Limitations

The plugin overlay is only rendered in /editor.html and /cf# if there is a cloud configuration assigned to the current path or the current path matches the configured active paths.

Clientlib categories used

siteimprove.aem
cq.wcm.edit
cq.authoring.editor.sites.page.hook

Inclusion in editor.html

For making the plugin available in editor.html, an addition to the headerbar has been created, as including the overlay within the page will lead to issues with the AEM overlay used in edit mode.

Did you find it helpful? Yes No