Set up headless content delivery and management in AEM

[#1]

Set up headless content delivery and management in AEM 
by Jeremy Lanssiers

Overview

We set up headless content delivery and headless content management by using AEM’s GraphQL to deliver and Assets API to manage content (via Content Fragments). The focus lies on using AEM to deliver and manage (un)structured data. We use the WKND project at https://github.com/adobe/aem-guides-wknd to support this example. 

Read the blogpost at https://medium.com/@jlanssie/setup-headless-content-delivery-and-content-creation-in-aem-cb03e08cc4d... 

Q&A

Please use this thread to ask questions relating to this article

[#2]

@jeremylanssiers 

Thank you for writing such a comprehensive and informative blog post on setting up headless content delivery and content creation in AEM Headless. I especially liked how you broke down the process into step-by-step instructions, with screenshots to illustrate each step. This made it very easy to follow along.

Feedback:

One small piece of feedback I have is that you could add a section at the end of your blog post to discuss the benefits and drawbacks of using headless AEM. This would be helpful for readers who are trying to decide whether or not headless AEM is the right solution for their needs.

For example, you could mention the following benefits:

• Headless AEM allows you to decouple your content from your presentation layer, giving you more flexibility to deliver your content to any device or channel.
• Headless AEM is also more scalable than traditional AEM deployments, making it ideal for large enterprises with complex content needs.

[#3]

You are right. I will add such a section in the upcoming days when I have some time to spare.