Multi-tenancy and multi-team development in AEM

Unfortunately, one solution very rarely fits the needs of all tenants. This talk elaborates on necessary namespacing rules to isolate individual AEM tenants with their own code running on the same AEM server/in the same AEMaaCS program as well as some tooling to enforce that isolation (aem-content-package-namespace-validators).

In addition, it outlines some means on how multiple teams can develop on the same AEMaaCS program along with advantages/disadvantages. The shared resources which require some governance/alignment will be clarified. One side aspect is how to establish common code among multiple tenants (possibly even managed by different implementation teams).