Universal Editor with existing AEMaaCS Project

Question

I have reviewed the following query and noticed that I have a similar use case, but it require only the Universal Editor feature. So, whenever the client opens a page created using an editable template in AEM, it will automatically open in the Universal Editor, allowing them to make any modifications.

However, my questions are different:

1. Will the Universal Editor feature be available for AEM Site Template pages in the future? As far as I know, it’s currently only available for Editable Dynamic Sites (EDS). Is that correct?

2. If I want to move my AEM site to the Universal Editor, do I need to enable instrumentation for all core components as well as custom components?

3. Is instrumentation also required for Experience Fragments?

4. How will template policies and the style system be handled in this case?

5. What about Page Properties?

I referred to the documentation and successfully edited a text component using the Universal Editor

However, I will need to enable this for each component individually and manually open the page through the Universal Editor, as it is not directly linked to AEM.

daniel-strmecki · Accepted Answer

Hi @sapnatanwar,here are my thoughts:1. Officially, Adobe supports Universal Editor only with EDS or Headless setups. However, personally, I don't see any reason for it. The official statement is "Since the Universal Editor follows a more streamlined, modern approach that does not support these legacy features, migrating such sites would require significant refactoring. For this reason, migrating Page Editor sites to the Universal Editor is only recommended for projects transitioning to Edge Delivery Services."2. Yes, you need to instrument all core components as well as custom components.3. Yes, you need instrumentation also for components within XFs.4. Style system is not supported AFAIK, but you can add a style property to components as a workaround. Template policies are defined with JSON files in Universal Editor.5. Page properties can still be edited in AEM. I am curious if you tried the migration of classic AEM components/pages to Universal Editor, and which challenges did you face? BR,Daniel

AmitVishwakarma · Answer

Hi @sapnatanwar ,1. Will the Universal Editor support AEM Site Template pages in the future?      - Universal Editor only supports Editable Dynamic Sites (EDS).      - AEM Site Templates (static HTML/CSS/JS with no Sling models) are not yet supported.      - Future roadmap may include this, but today it’s EDS only.2. Do I need to instrument core and custom components for UE to work?     - Yes. Every component (core or custom) needs to be instrumented using the @UniversalEditorEditable annotation or with instrumentation metadata.     - This allows the Universal Editor to map and update content dynamically.3. Is instrumentation required for Experience Fragments (XF)?     - Yes, if you want to edit content inside an Experience Fragment via Universal Editor.     - Instrument each XF component just like page components.4. How are template policies and style systems handled?     - Template policies (design dialog settings) and style system features are not editable via Universal Editor.     - They must be configured in the Editable Template UI in AEM — not from Universal Editor.     - UE is content-focused, not structure-focused.5. What about Page Properties?     - Not supported yet.     - You cannot edit page properties (title, description, etc.) via Universal Editor as of early 2025.     - Must use the classic Page Properties dialog in AEM Touch UI.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded