Skip to main content
FreeAn audit of your Drupal siteA written audit of your Drupal site, within three business days
All articles

Frontend & SDXNov 16, 20264 min read

One platform, many sites: brand families and multisite done well

Valentin ZsigmondFounder & Lead Engineer

Businesses grow into more than one website. A second brand, a new country, a product line that deserves its own presence, a campaign site, an events site, a foundation. Each starts as a reasonable decision and each adds a site to maintain, and by the fifth or sixth the organization discovers it is running a small portfolio of websites, each slightly different, each on its own schedule, none of them quite sharing anything. This article is about the alternative: one platform that runs many sites, sharing what should be shared and separating what should be separate, so that the portfolio costs about as much to run as one site did.

What should be shared, and what should not

The question that shapes a multi-site setup is which parts are common. Usually the answer follows a pattern.

Shared: the platform itself, the security updates, the component library, the editorial tooling, the hosting, the monitoring, the integrations with central systems such as the CRM or the invoicing package, and the team that looks after all of it. These are the parts that are expensive to duplicate and gain nothing from being different.

Separate: the content, the domain, the brand expression within the shared design system, the editors and their permissions, the languages, and sometimes the analytics and the legal pages. These are the parts that make each site itself, and they need to be controllable by the people responsible for that site without affecting the others.

A good architecture makes the first list genuinely shared, so a fix or an improvement lands everywhere at once, and the second list genuinely separate, so a mistake on one site stays on that site.

The ways Drupal can do it

Drupal offers several models, and the right one depends on how much the sites have in common.

One site, many domains. When the sites are really one body of content presented under different brands or for different regions, a single Drupal installation can serve several domains, each with its own theme settings, menus and front page, drawing on shared or separate sections of the same content. Editors work in one place; visitors see distinct sites. This is the simplest model to run and suits brand families and country sites with overlapping content.

One codebase, many installations. When the sites need fully separate content and configuration but should share code, Drupal's multisite capability runs several independent sites from one codebase. Each has its own database and its own configuration; all receive the same code update at the same time. This suits organizations with distinct units that want autonomy over content and structure but one platform team.

A shared distribution. When the sites are numerous and should start from the same template, we package the shared parts, the component library, the content types, the editorial workflow, the default configuration, as an installable profile. Each new site is created from it in minutes, inherits every improvement to the shared parts, and diverges only where it needs to. This is the model behind the site factories that large organizations run, and it scales down well to a company with a handful of sites.

These can also be combined. A distribution can define the template, multisite can run the installations, and any installation can serve several domains.

The component library is the key

Whichever model, what makes it work in practice is a shared component library. Each site is assembled from the same set of building blocks, hero, card, form, navigation, footer, and each block accepts the brand's colors, typography and spacing as settings rather than hard-coding them. A new brand is a new set of settings, not a new theme. A fix to the accessibility of a form field lands on every site the next time it deploys. And the visual identity of each site stays consistent with itself because it can only be built from pieces that already follow the rules.

This is also what keeps the sites from drifting apart over time. Without a shared library, each site accumulates its own small variations until they are effectively different products. With one, variation is deliberate and expressed in settings, and the underlying structure stays common.

Operating a portfolio

Running several sites as one platform changes the maintenance picture entirely. Security updates are applied once and tested once. Monitoring covers all sites from one dashboard. Backups follow one policy. A new integration, with a central CRM for instance, is built once and configured per site. When a major upgrade comes due, it is one project rather than six. On our platform, each site still runs in its own isolated containers with its own resources, so the sharing is of code and process, never of failure.

Editors and governance

Multi-site brings a governance question: who decides what is shared? We recommend a small group that owns the shared parts, the component library and the platform configuration, and a clear path for a site team to request a change or a new component. Site teams own their content and their brand settings fully. Roles and permissions reflect this: a site editor sees their site, a platform owner sees the shared configuration, and neither is confused by the other's tools.

When to move to one platform

The signs are familiar: the same fix being made three times, a security update that reaches some sites and not others, brand guidelines that each site interprets slightly differently, and a budget that grows with the number of sites rather than with their value. Consolidating is a project, usually done one site at a time onto the shared platform as each comes due for a refresh, so the portfolio is never disrupted all at once. If you are running several sites and any of those signs sound familiar, we would be glad to map out what a shared platform would look like for you.

Written by

Valentin Zsigmond

Founder & Lead Engineer

Full-stack Drupal architect with almost two decades of experience leading large teams in enterprise environments. Founded Tilizy Digital to bring senior-level expertise directly to the organizations that need it. Mentor to dozens of Drupal developers and creator of SDX — a Drupal extension for building modern frontends with React and Vue.

Enjoyed this article?

If this resonated, imagine what we could do working together on your Drupal site.