Hi, Experience League Community --
We are looking to leverage AEM as a "platform" to power multiple business units, each with their own set of unique websites; and I wanted to ask if anyone had any advice on how we might use AEM most effectively, or feedback if you are potentially using AEM in a similar environment.
We have two major business units (BU's) -- BU #1 and BU #2. These business units have very different brands and serve a different set of customers. And, each BU has various websites, in the neighborhood of a few hundred pages each.
We are currently using AEM to power all of the websites across these two business units, but each business unit is using AEM in a slightly different way. For example, BU #1 has developed their own unique set of components for each of their websites (that cannot be shared or utilized by BU #2) and vice versa. Furthermore, over the course of the last few years, each BU has developed duplicative components that differ slightly -- for example, we have multiple "Accordion" components that differ only slightly in their visual presentation.
We are looking to re-imagine our site infrastructure, and leverage one instance of AEM with a common, well-documented set of universal components that can be used by both of our brands and multiple websites. In other words, we want to build an "Accordion" component once and make it flexible enough to enable both of our brands to style the visual presentation of this Accordion however they please for each of their sites.
Is anyone using AEM in this way (as a "platform") to power multiple business units, and multiple properties? Any best practices, or lessons learned, around using core components and guidelines for when to develop a custom component?
Thanks!
