ue-component-model

To configure AEM Edge Delivery blocks for the Universal Editor, you create or edit three JSON files: component-definition.json, component-models.json, and component-filters.json to register definitions, map model fields, and sync filters so blocks appear in the section catalog and render predictably.

The component-definition.json file maps block definitions to Universal Editor templates and resource types, including container and key-value blocks, ensuring blocks are registered correctly for authoring and rendering within AEM Edge Delivery.

You add a new block to the Universal Editor section catalog by validating and syncing component-filters.json entries with your block definitions and model IDs, ensuring authors can add the new block under the appropriate section.

Universal Editor model fields fail to map correctly when naming conventions do not align with the block's decorate() expectations, requiring you to adjust field selection and mappings in component-models.json to enforce proper IDs and predictable rendering.

Yes, you can use JSON templates to register container and key-value blocks in AEM by mapping block definitions to Universal Editor templates and resource types, ensuring correct field mappings and filter entries are applied across the configuration files.

Manually editing Universal Editor JSON configurations risks breaking proper IDs, resource types, and filter synchronization, making blocks fail to appear in the section catalog or render with incorrect fields and behavior without structured validation.