April 13, 20261 min read
Orchestrating Multi-Site Architecture in Drupal 11
Strategies for managing shared configuration and distinct content across global enterprise instances, without the operational drag of a 2015-era multisite.
Why multi-site still matters
For many global enterprises, a fleet of country sites is a non-negotiable requirement. What has changed is the tolerable operational overhead.
The shared-config pattern
Instead of one codebase with N settings files, I prefer a shared install profile that exports a baseline content model, then selectively overrides per-site via configuration splits.
Where it breaks
Translation workflows, media library reuse, and editorial access control are the three places where the pattern pays for itself or collapses under its own weight.