Documentation AEM as a Cloud Service User Guide

Customizing the Universal Editor

Last update: June 11, 2025

Applies to:
Experience Manager as a Cloud Service

Topics:
Developing

CREATED FOR:

Admin
Developer

Learn about the different options to customize the Universal Editor to support the needs of your content authors.

TIP

The Universal Editor also offers many extension points, allowing you to expand its functionality to meet your project needs.

Disabling Publishing

Certain authoring workflows require content to be reviewed before it is published. In such situations, the option to publish should not be available to any authors.

The Publish button can therefore be suppressed entirely in an app by adding the following metadata.

<meta name="urn:adobe:aue:config:disable" content="publish"/>

Disabling Publishing to Preview

Certain authoring workflows might preclude the publication to the preview service (if available).

The Preview option in the publish window can therefore be suppressed entirely in an app by adding the following metadata.

<meta name="urn:adobe:aue:config:disable" content="publish-preview"/>

Disabling Open Page

The Open Page button can be suppressed entirely in an app by adding the following metadata.

<meta name="urn:adobe:aue:config:disable" content="header-open-page" />

Disabling Duplicate Button

Certain authoring workflow might need to limit the ability of the content author to duplicate components. You can disable the duplicate icon by adding the following metadata.

<meta name="urn:adobe:aue:config:disable" content="duplicate"/>

Changing Your Endpoint

If you would like not to use the Universal Editor Service, which is hosted by Adobe, but your own hosted version, you can set this in a meta tag. Please see the document Getting Started with the Universal Editor in AEM for details.

Filtering Components

You can restrict the allowed components per container in the Universal Editor using component filters. Please see the document Filtering Components for more information.

Conditionally Show and Hide Components in Properties Panel

Although a component or components may generally be available to your authors, there may be certain situations where it does not make sense. In such cases, you can hide components in the properties panel by adding a condition attribute to the fields of the component model.

Conditions can be defined using JsonLogic schema. If the condition is true, then the field will be displayed. If the condition is false, then the field will be hidden.

Sample Model

 {
    "id": "conditionally-revealed-component",
    "fields": [
      {
        "component": "boolean",
        "label": "Shall the text field be revealed?",
        "name": "reveal",
        "valueType": "boolean"
      },
      {
        "component": "text-input",
        "label": "Hidden text field",
        "name": "hidden-text",
        "valueType": "string",
        "condition": { "===": [{"var" : "reveal"}, true] }
      }
    ]
 }

Condition False

Condition True

Custom Preview URLs

You can specify a custom preview URL via a urn:adobe:aue:config:preview meta configuration, which will open when clicking the Open page button in the editor’s top-right toolbar.

This is particularly useful for applications with specific preview requirements, such as those using Edge Delivery Services with WYSIWYG authoring.

To do so, simply include the desired preview URL in a meta tag of the instrumented app like the following example.

<meta name="urn:adobe:aue:config:preview" content="https://wknd.site"/>

recommendation-more-help