Editorial networks, franchise brands, and multi-venue cultural organisations often face the same problem: they need to run many separate websites that share a common technical foundation but present distinct identities. Building and maintaining each one as a wholly independent project is expensive. Every time the core platform improves, the change has to be applied across every site individually. The overhead compounds with scale.
This platform solves that by turning one codebase into an unlimited number of live, branded websites, each on its own domain, each with its own look and feel, each independently managed.
How it works for the organisation
An editor manages content through a cloud-based system. When a build is triggered, the platform fetches the latest content, compiles it into fast static web pages, and pushes it live. A new tenant site such as a new branch venue, a partner organisation, an exhibition microsite can be brought online by setting two configuration values and running a single command.
Each site lives on its own domain. SSL certificates are issued and renewed automatically; there is nothing to configure manually. The sites are served from Cloudflare’s global network, so pages load quickly for visitors anywhere in the world without requiring a dedicated server entirely free of infrastructure.
Theme inheritance without forking
The design system works like a child-theme model. A set of shared default components (header, footer, navigation, typography) forms the base. A client-specific theme folder holds only the overrides: a different logo, a different colour scheme, different fonts. Everything else inherits from the shared defaults automatically.
The result is that a rebranded tenant site requires only the files that are genuinely different. There is no copy of the whole codebase to maintain per client, and a fix or improvement made to the core platform reaches every tenant the next time their site is built.
Reliability built in
The platform validates every image URL before it is compiled into a page and broken or expired links are removed automatically rather than appearing as missing images in production. Content fetched from the database is cached between builds, so incremental rebuilds are fast even when the content library is large.
The outcome
The architecture makes a direct case for organisations thinking about digital scale. Whether the goal is to bring partner institutions onto a shared platform, run regional microsites for a distributed membership body, or give exhibition sponsors a branded web presence without spinning up separate infrastructure, the model is the same: one maintained codebase, many independently operating sites, with each tenant unaware of and unaffected by the others.
Here I reduced creating new site to an automated operational task, rather then a development project.