Scaling Drupal across 100+ independent sites brings technical chaos: config overrides, rogue modules, forked repos. In this session, we’ll explore real-world solutions — and the scars — from managing it.

Prerequisite
The talk will be developer-focused, and include code solutions - however, as a use case, it might also be interesting to sitebuilders.

Outline
I work for Reload, a Danish digital agency. We recently built a Drupal platform that is used as the public facing website for 100+ libraries across 3 countries.

Some of these libraries are very small, with very few editorial resources, where things just need to work out of the box.

Others have many editors and technical ambitions, such as having their own modules developed, uploaded and managed, without Reload getting involved.

On-top of all that, the platform is also open-source, meaning that there are some libraries that are completely out of Reload’s control - managed by other digital agencies.

All of this results in a situation where we need to both have a site that can be strictly controlled for some, and very open for others.

A platform, where we need to be able to force through our updates, without overwriting the webmasters work.

Learning Objectives
- Learn practical techniques for managing shared configuration across large numbers of Drupal sites.

- Understand how to structure deployments when allowing different degrees of editorial and technical freedom.

- Identify governance models that reduce platform instability without over-restricting innovation.

- Recognize early warning signs of dangerous forks, rogue modules, or config drift in a platform ecosystem.

Experience level
Intermediate