Hi everyone, I’m looking for some guidance on an architectural decision for a multi-site setup on AEM as a Cloud Service. I need to create additional websites on the same AEM Cloud program. Some of these new sites will share part of the existing platform (authoring model, utilities, or components), while others may require different structures, custom components, or even different frontend approaches. In short, it’s a mix of shared and site‑specific functionality. On AEM on‑prem, my usual approach would have been: - One **common multi‑module project** containing shared utilities, services, and reusable components.- One **separate multi‑module project per site**, each deployable independently (its own pipeline, its own release cycle).- The shared project consumed as a dependency by each site. ### With AEM as a Cloud Service, I’m trying to understand the best practice for this scenario. From what I know, AACS encourages a **single Git repository** and a **single pipeline** per program, b
