Headless AEM

Avatar

Avatar

AEM_Forum

Avatar

AEM_Forum

AEM_Forum

12-03-2021

Hi all,

 

If I am implementing Headless AEM

1. What is the relevance of AEM Templates, given that pages will not be built in AEM and AEM supplies only data to te front end?

2. How content could be created?

3. How could the front end consumes AEM Experience Fragments?

 

Appreciate your support.

 

Thanks,

Rama.

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Veena_Vikram

MVP

Avatar

Veena_Vikram

MVP

Veena_Vikram
MVP

13-03-2021

@AEM_Forum The link @jbrar gave you will tell you the complete picture of Headless AEM . May be you have to start from her https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/c... . Let me try answer your below questions as much as I can

 

1. What is the relevance of AEM Templates, given that pages will not be built in AEM and AEM supplies only data to te front end?

 

   The templates are created so that we can generate an endpoint API for your services to consume the content from AEM. It is clearly explained in the video in the above link and more clear explanation is https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/c... 

 

2. How content could be created?

   Content can be created as Content Fragments and Editable Templates to create the Content Service API

"

The key concept with Content Fragments, is the authored content is presentation-agnostic, meaning its intended for multi-channel use where the consuming application, be that AEM, a single page application, or a Mobile app, controls how the content is displayed to the user.

The primary concern of the Content Fragment is to ensure:

  1. The correct content is collected from the author
  2. The content can be exposed in a structured, well-understood format to consuming applications.

This chapter covers enabling and defining Content Fragment Models used to define a normalized data structure and authoring interface for modeling and creating “Events”.

"

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/c...

 

 

"In AEM Content Services, editable templates are used to define how the JSON data is exposed." - https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/c...

 

3. How could the front end consumes AEM Experience Fragments?

     Any content can be consumed in JSON format by any other service once they are exposed as CaaS.

 

Update : I will try to answer below question asked in the comment of this Reply

Everything looks similar between regular AEM and Headless AEM implementations. Then What is the difference in efforts estimation/implementation between regular AEM and Headless AEM? 

 I agree that to some extend but the fact is the effort is much lesser compared to the Regular AEM project , where you need to estimate for the UI effort , design the components and all the thinks included in deploying it as the final AEM website/portal . But in Headless AEM , you create the content in AEM either using CF or a Template to expose the content as an API. You really don't invest much in the FE design in AEM , as the content is delivered only as JSON to be consumed by your services. The only focus is in the structure of the JSON to be delivered. Does that help to understand ? 

 

Thanks

Veena

Answers (1)

Answers (1)

Avatar

Avatar

jbrar

Employee

Avatar

jbrar

Employee

jbrar
Employee

12-03-2021

You can find detailed docs related to headless AEM and templates at [1]

 

[1] https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/c...