Running multiple sites from a single Drupal codebase is powerful—and tricky—when it comes to configuration. One site needs a feature, another must not have that feature; environment overrides creep in; and “just export and import” stops being simple. This session presents a clear, repeatable approach built around distinct Config Split types and shows how to templatize and automate them so adding a new site is a 5‑minute task, not a much longer ordeal.

What we’ll be covering:
- Site-level splits (per-domain overrides), feature-level splits (toggleable features any site can opt into), and environment-level splits (dev/stage/prod tooling).
- Setting split precedence using Config Split
- Opinionated directory structure and naming conventions that prevent overlap and drift.
- Reusable site-level split templates
- A lightweight automation command that scaffolds a new site-level split from the template and runs a quick validation so you know it’s sound.

We’ll walk through creating a feature split, generating a new site split from a template, opting the site into the feature, and importing config across two sites locally. You’ll leave with an understanding of patterns, templates, and a simple automation you can adopt immediately.