Multi-site Laravel CMS

Start with one site, then add pressure when it is real

This page helps you separate one-site setup from the extra decisions that arrive with domains, languages, and site-specific package configuration.

Capell can begin as one Laravel CMS project. When the work expands, it can add languages, editors, domains, packages, and site-specific output without splitting into unrelated systems.

The point is not to carry enterprise process from day one. It is to keep a path open before the first site outgrows itself.

A multi-site Capell project should make shared and local decisions obvious. Shared concerns might include package availability, common section types, media rules, redirect policy, and deployment flow. Local concerns might include domain, language, navigation, theme defaults, legal pages, and package settings.

Start by proving one site. Add the second site only when the model is clear enough to explain which records are global, which records are site-scoped, and how editors know where their change will appear.

Next steps

• Review operations before adding more sites.
• Read governance when roles and approvals matter.
• Review deploy options when each site needs a clear runtime path.