Headful or Headless AEM? Why not both with Hybrid? | AEM Community Blog Seeding

[#1]

Headful or Headless AEM? Why not both with Hybrid? by Paul Goodrich

Abstract

It’s not uncommon when facing a new problem, to fall back on a tried-and-true solution. Then, suddenly remember why the team moved off of that solution in the first place. Recently, I’ve seen this trend with engineering teams and a desire for multichannel content.

A Common Case for Headless Content on AEM
Let’s set the stage with an example. A digital marketing team has licensed Adobe Experience Manger 6.5 with the hope of using the WYSIWYG content editing to quickly produce and release content decoupled from code deployments. They also see that AEM has the capacity to produce reusable multichannel content via Content Fragments. Marketers plan on using those fragments within a marketing website, a companion mobile app, and voice assistance devices. Finally, it would be great if the site had the option for highly interactive pages that didn’t require a refresh. They ask the engineering team to implement the solution.

The engineering team is full of talented backend developers who have years of experience serving up web content. The engineers dig into the platform, and while some are able to learn AEM component development, it’s slow going.

Read Full Blog

Headful or Headless AEM? Why not both with Hybrid?

Q&A

Please use this thread to ask the related questions.