Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Adobe Summit 2021, AEM Session | TW122 - Deliver Headless Experiences with Adobe Experience Manager




Session Details

With Adobe Experience Manager, you have a modern unified solution for all your content needs to support web and modern JavaScript front-end apps. Learn from Adobe Consulting Services expert instructors about headless experience management using the latest Experience Manager Content Fragment enhancements and the new GraphQL API for headless content delivery.

Session Recording

Session Schedule

Wednesday, Apr 28 3:00 AM - 4:00 AM IST


Sean Steimer, Technical Architect, Adobe Professional Services, Adobe

Session FAQs

Q. When should you use GraphQL vs QueryBuilder? 

A. As long as you are using content fragments, you should use GraphQL. 

GraphQL is the newer and modern way for delivery of structured AEM content in headless scenarios. Query Builder is great but older, and more specific to AEM and other types of content. 

Q. Is GraphQL available with AEM6.5? 

A. GraphQl is available only for AEM as a Cloud Service currently. It will be available for AEM 6.5 in a service pack due to be released later this year. 

Q. There are some good arguments for using headless if you're starting from scratch - any thoughts on moving from head-on to headless? Is it worth the effort? 

A. AEM lets you choose your preferred implementation model - coupled, decoupled, hybrid - and mix and match those models based on your business requirements. If you already have a head-on experience, you can begin to introduce headless and hybrid elements on a case by case basis, rather than going for a full-on re-write to headless. 

Q. Is there support for custom GraphQL Schema resolvers?  

A. Currently AEM GraphQL is tied to schemas from content fragment models, and endpoints in an instance/service. General schemas across data types and sources are being discussed and investigated for potential future inclusion.  

Q. Can these data types and properties be customized and to what extent? And are there restrictions around adding more validations? 

A. Best way to approach custom structures is with the new capability to nest models and fragments. I.e. break the structure into smaller, standard elements which can form a hierarchy to represent the larger custom structure.  

We've added more validations in the data types. They are product code and not really extensible or customizable.  

Q. Do the Content Fragment Models allow for all of the coral3 form types, such as color picker, file upload, and nested mutlifields? 

A. Content fragment models are independent of the presentation layer and Coral library in particular. Color picker specifically was actually added as an enhancement in the Content Fragment editor, for rich text multiline fields.  

Q. Can we access static & scene7-renditions from the image ref in a GraphQL query? 

A. Only image references as asset references per se for now. We are discussing and investigating if/how to add Dynamic Media support to GraphQL 

Q. I noticed a couple of the fields in the Content Fragment Models I don't see in our AEM instance (Fragment Reference, Unique checkbox, etc). Are those tied to the AEM version or to another area? 

A. There are new data types in content fragments supported on cloud service as part of the graphQL feature set. All of that will be available on AEM 6.5 in the future 

Q. Is graphql limited to content fragments? 

A. For now yes, based on schemas tied to fragment models.  

Full Schedule

Check Here


Please use this thread to ask the question related to this Session.

Don't forget to register yourself for this session @ Adobe Summit 2021

Kautuk Sahni
0 Replies