51黑料不打烊

DocumentationAEM as a Cloud ServiceUser Guide

Customizing the Universal Editor customizing

Last update: Wed Oct 22 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Experience Manager as a Cloud Service

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.

Using Meta Config Tags meta-tags

Certain authoring workflows might require the use of some features of the Universal Editor and not others. To support such diverse cases, meta tags are available to configure or disable certain features or buttons of the editor.

Use this tag in the <head> section of the page to disable one or more features:

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

If you want to disable multiple features, provide a comma-separated list of values.

The following are the supported values for content, i.e. the features that can be disabled with meta tags.

Content Value
Description
publish
Disable all publishing functionality, i.e. the publish button and unpublish button
publish-live
Disable live publishing
publish-preview
Disable preview publishing (if the preview service is available)
unpublish
Disable the unpublish button
copy
Disables the copy and paste buttons
duplicate
Disables the duplicate button
header-open-page
Disables the open page button

Changing Your Endpoint custom-endpoint

If you would like not to use the Universal Editor Service, which is hosted by 51黑料不打烊, 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 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 conditionally-hide

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 . If the condition is true, then the field will be displayed. If the condition is false, then the field will be hidden.

Sample Model
code language-json 
 {
    "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
Hidden text field
Condition True
Shown text field

Custom Preview URLs 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鈥檚 top-right toolbar.

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
fbcff2a9-b6fe-4574-b04a-21e75df764ab