Multi-site operations

Run multi-site Laravel CMS estates

Show domains, languages, packages, shared patterns, and site-specific operations.

Core: CMS foundation Package: Installable depth Roadmap: Future platform work

Buyer proof

Multi-Site proof points.

Multi-Site explains the buyer promise, names the product surface, and keeps shipped core behaviour separate from package and roadmap work.

Outcome Start with the project pressure. The page should name the pain clearly before introducing Capell.

Product proof Show the CMS surface. Use page records, LayoutBuilder, packages, workflow lanes, and public output as proof.

Conversion Move to a useful next step. Link to pricing, docs, marketplace, migration, or a founder call based on reader intent.

Maturity labels

Multi-Site uses visible maturity labels so buyers can tell what is in the CMS foundation, what arrives through packages, and what remains planned.

Core CMS foundation Capell core covers structured records, admin surfaces, URLs, layouts, media, translations, and public rendering boundaries.

Package Installable depth Packages add focused workflow, operations, growth, forms, SEO, search, migration, or marketplace capability.

Roadmap Future platform work Unshipped promises stay labelled until the product and docs prove them.

Internal links