Universal Editor for developers (deprecated)

This reference applies to existing Universal Editor projects that use Document Authoring (DA.live) and already include the block definitions and generation hook described below.

For Adobe Experience Manager Sites projects, see the Universal Editor blocks guide .

Deprecation notice

For new storefronts, use Experience Workspace instead.

Existing customers and those already implementing the Universal Editor keep access to the tool. For support details, see the visual editing overview.

Block definition files

In an existing storefront with Universal Editor instrumentation, each block’s JSON definition is stored at blocks/{block-name}/_{block-name}.json. Replace {block-name} with the block’s name.

If your project includes the pre-commit generation hook, it combines these definitions into the component-*.json files in the project root. The Universal Editor reads these generated files.

aem-boilerplate-commerce/
├── component-definition.json    ← generated
├── component-filters.json       ← generated
├── component-models.json        ← generated
├── models/
│   └── _section.json           ← add new blocks to component list
└── blocks/
  └── accordion/
    └── _accordion.json      ← UE instrumentation

Tip

Open a page in the Universal Editor to check your blocks. In the content tree, blocks without editor definitions have (no definition) appended to their names.

More help on this topic

• Universal Editor developer reference : instrumentation syntax and options