Build a common component library for multiple tenants

[manasabojja7]

Hi,

Our team is new to AEM development and we are in our initial phases of building a new application using AEM. The idea here is to build a common library of AEM components to be used across multiple tenants hosted in an instance. What are the best options for us to build a common library and use it in different tenant apps? Do we have any recommendations as to how and what needs to be considered while working on this common library? Do we also have any referenced documentation as to how the commons library is built and can be imported to tenant apps? What should be the strategies for maintaining the versioning for these common components?

Your help is much appreciated. Thanks in advance.

-Manasa

[Saravanan_Dharmaraj · Accepted solution]

Couple of blogs talks about Multi Tenancy and components

https://levelup.gitconnected.com/aem-multitenancy-running-multiple-websites-on-a-single-aem-environm...

https://www.netcentric.biz/insights/2021/12/component-library-aem.html - Using versioning to your advantage

https://www.bounteous.com/insights/2016/06/22/managing-multi-tenant-component-styles - how to manage your style.

https://dev.to/anfibiacreativa/integrating-a-modern-frontend-in-a-multi-tenant-aem-project-2l20 - Specific about setting Front end development