Anyone used Experience Fragments with EDS & Universal Editor? | Community
Skip to main content
daniel-strmecki
Community Advisor and Adobe Champion
daniel-strmeckiCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 28, 2025
Solved

Anyone used Experience Fragments with EDS & Universal Editor?

  • May 28, 2025
  • 1 reply
  • 616 views

Hello,

Universal Editor supports Experience Fragments (XF) [1], but does this work in combination with Edge Delivery Services (EDS)? There is an EDS block called Fragment [2], but the sample is built only for document-based editing, and I am not sure if it works with AEM.

Has anyone tried it? Does it work? Which resource type should be used for the XF page and components?

[1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types#experience-fragment

[2] https://sidekick-library--aem-block-collection--adobe.aem.page/tools/sidekick/library.html?plugin=blocks&path=/block-collection/fragment&index=0

 

I appreciate any advice you can provide,

Daniel

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by daniel-strmecki

The answer is: Experience Fragments (XF) cannot be assembled server-side in EDS like we are used to with classic AEM.

Possible alternatives are:

  • Expose XFs via API and load them client-side in EDS
  • Switch to EDS fragments, which are again client-side rendered

Therefore, this might be challenging for clients who are used to using many XFs. Moving to EDS requires redefining and simplifying how content is stored and authored.

 

Hope it helps someone,

Daniel

1 reply

daniel-strmecki
Community Advisor and Adobe Champion
daniel-strmeckiCommunity Advisor and Adobe ChampionAuthorAccepted solution
Community Advisor and Adobe Champion
May 29, 2025

The answer is: Experience Fragments (XF) cannot be assembled server-side in EDS like we are used to with classic AEM.

Possible alternatives are:

  • Expose XFs via API and load them client-side in EDS
  • Switch to EDS fragments, which are again client-side rendered

Therefore, this might be challenging for clients who are used to using many XFs. Moving to EDS requires redefining and simplifying how content is stored and authored.

 

Hope it helps someone,

Daniel

    Terms & ConditionsAccessibility statement

    Loading footer...