AEM headless architecture

[durga_kavali]

Hi Everyone,

We constructed CF models and CFs using a headless architecture approach, delivering content to FE via GraphQL endpoints. Do we still adhere to the AEM project structure in this case? since we just utilized the dispatcher module.Please recommend recommended practices for maintaining the headless approach's code base.

<!-- <module>all</module>
 <module>core</module>
 <module>ui.frontend</module>
  <module>ui.apps</module>
 <module>ui.apps.structure</module>
 <module>ui.config</module>
 <module>ui.content</module>
 <module>it.tests</module>-->
 <module>dispatcher</module>
 <!--<module>ui.tests</module>-->

Thanks,

Durga Kavali

@ EstebanBustamante 

arunpatidar

daniel-strmecki

[EstebanBustamante]

Hi,

The archetype is just a base template that will be adjusted to your needs, so it is perfectly fine to tweak it to fit your project requirements. In your case, I think you could still consider keeping ui.content for versioning the Content Fragment Models, along with the other modules that enable deployment, which I believe is ui.all.

Hope this helps.

[durga_kavali]

Thank you for the prompt reply.

Can i delete the unused project modules expect ui.content and Dispatcher modules and deploy?

[EstebanBustamante · Accepted solution]

Yes, you can do that; however, it will require more work if you need them back at some point. As long as they don't run as part of the build it should be ok, but it is up to you. 

[daniel-strmecki]

Hi @durga_kavali,

on the initial project setup, I always delete modules I am not using to keep the project as simple as possible. You can always add it later. For example, if your project is headless then you probably don't need the ui.frontend module.

However, sticking to the default AEM project structure still makes sense for any project. In case you have a complex project or multiple teams working in different modules you can even add more.

Good luck,

Daniel