Designing a Content Fragment Model for Multi-Brand Sites

By Alberto Zarza Martín · · 7 min read

Serving multiple brands from a single AEM instance is a common enterprise requirement, and the Content Fragment Model design decisions made early on determine whether that setup stays maintainable or turns into a maze of brand-specific exceptions.

Shared core, brand-specific extension

The pattern that scales best is a shared base model covering fields common to every brand (headline, body, primary image, SEO metadata), with brand-specific variations handled through either separate extended models or a well-scoped set of optional fields — not by adding every brand's unique fields to one universal model.

Folder and permission structure

Structure the DAM and Content Fragment folder hierarchy by brand at the top level, with shared/reusable content in a clearly separated common folder. This makes permission scoping straightforward later — brand marketing teams get write access to their own tree and read access to shared assets, without needing per-fragment permission rules.

Avoiding model sprawl

Rendering considerations

Whether delivery happens through classic AEM components or EDS blocks, keep brand-specific presentation logic in the rendering layer, not in the Content Fragment Model itself. The model should describe what the content is, not how a particular brand chooses to display it — mixing the two is the most common reason multi-brand Content Fragment Models become hard to evolve.

Governance

Assign a model owner responsible for approving changes to shared base models. Without this, individual brand teams tend to request one-off field additions that quietly turn a clean shared model into a union of every brand's edge cases.