How to leverage Content Fragment in Adobe Edge Delivery with x-walk approach?

[rituraj_singh]

HI all,

Using the X-Walk approach have a question regarding EDS. I learned that whenever we add content to Universal Editor it goes directly to EDS. However, I am unsure how to send content authored in an AEM content fragment to EDS, rather than accessing it through AEM Publish. Could you please let me know if it is possible to send content fragments to EDS  ? My goal is to send all the CFs to EDS and fetch it directly via Frontend.

Thanks.

[arunpatidar · Accepted solution]

Hi @rituraj_singh 
When delivering content fragments using Adobe Edge Delivery Service with GraphQL, you can create a model field [1] that allows you to browse and select a specific Content Fragment. Once the Content Fragment is selected, you can use GraphQL queries [2] to fetch and deliver the content dynamically.

References:

1. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev... 
2. https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headles... 

[RiturajSi]

@arunpatidar  Sorry to follow up late on this

Thanks for the reply, i followed the document  you mentioned , yes it solves the content fragment selection process in the EDS page.
So for EDS approach using AEM we will generally don't require AEM Publish server, so who will serve the graphQl request , will it be author or i have to keep Publish server up and running with the the published content fragment to serve the graphQL query.

Also in that case will it impact the performance as request will be served from the AEM server rather than the edge servers.

Have you seen these use cases implemented in some other way or this is the only way to go ?

Also there is already one block component called fragments, it works fine if we reference any HTML fragments but not with content fragments as it shows only a button link. Any idea in future it will also support the CF directly ?

[arunpatidar]

Hi @RiturajSi 
You need publisher to use GraphQL endpoints. However you leverage persistent query & CDN cache for performance optimisation.

Fragment component, can load any page with plain selector, it is similar to experience fragment in AEM.