In Adobe EDS Universal Editor, is it possible to create custom ResourceTypes for new blocks?

[Wilnaweb1]

I’m working with the Universal Editor in Adobe Edge Delivery Services (EDS) and need to create new blocks/components for a project.

My question is: in addition to implementing the new blocks, is it also possible to create custom ResourceTypes for them, similar to what we do in traditional AEM Sites?

If so, is there any official documentation or practical example showing how to register and associate these ResourceTypes in the context of Universal Editor/EDS?

[Saravanan_Dharmaraj]

@Wilnaweb1 Please have a look at this documentation

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/bu...

[Wilnaweb1]

Thank you, my friend.

I’d like to confirm if it’s possible to create custom ResourceTypes or extend existing ones, as described in the documentation:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/bu...

[Wilnaweb1]

Thank you, my friend.

I’d like to confirm if it’s possible to create custom ResourceTypes or extend existing ones, as described in the documentation:
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/bu...

[Shiv_Prakash_Patel · Accepted solution]

Hi @Wilnaweb1 ,

In Universal Editor (UE) with Edge Delivery Services (EDS), you cannot create and register custom sling:resourceType for blocks like in traditional AEM Sites.

All UE blocks use the generic Franklin resource types:

• Blocks: core/franklin/components/block/v1/block
• Sections: core/franklin/components/section/v1/section

Instead, you “register” new blocks for authoring by adding them to:

• component-definitions.json – declares the block name and options
• component-models.json – defines editable fields in the Properties panel

Official docs & examples:

Create a Block with Universal Editor

Component Definitions

Component Models (Field Types)

Note: For EDS + UE, stick to Franklin’s resource types and register blocks via JSON models/definitions — custom sling:resourceType is not the supported approach.