Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

recommended way to built site using AEM headless or hybrid?

Avatar

Level 3

Hi Everyone ,

 

The client plans to build a static site (header , footer, banner, cards and integrations) using Headless CMS, exposing content to client-side applications through HTTP REST APIs and GraphQL APIs. They are seeking advice on the best AEM hybrid or headless approach. i would like understand what is headless approach? Can some one please assist me

 

Thanks,

Durga Kavali.

3 Replies

Avatar

Community Advisor

Hi, 

A pure headless approach means that you have a source system(AEM) where data (content, in the case of AEM) is exposed to different "heads" or applications, generally React or Angular applications. By definition, the headless approach means you don't have the ability to provide any WYSIWYG editor but solely rely on how the data is presented. In this case, you would rely on Content Fragment Editors.

 

The hybrid approach, introduced by Adobe, is not a widely used term in the industry. It combines the best of both worlds: maintaining the headless functionality of exposing data while incorporating the ability to use a WYSIWYG editor. This hybrid approach can be implemented through the SPA Editor and, more recently, through the Universal Editor. The choice of approach depends on the capabilities you need, as each has its own advantages and disadvantages. I have provided a brief overview of these approaches. For a more in-depth reference, you can read these:

 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev...

https://medium.com/@prajwaljainkmt/aem-architecture-headful-vs-headless-vs-hybrid-cb7a757b398f 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev... 

 

Hope this helps



Esteban Bustamante

Hi Everyone,

 

The client wants to use a headless strategy, which means that via GraphQL APIs.AEM exposes content, which frontend frameworks (like React) can use. And the client wants to integrate AEM forms with Marketo from the AEM side, which means building adaptive forms and storing the data in Marketo upon form submission. How can these integrations be handled most effectively without using any AEM services(client only wants headless way)?

 

Please assist.

 

Thanks,

Durga Kavali.

 

 

 

 

 

 

Avatar

Administrator

@kavalidurga Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni