Multi-Site Platform

Multi-Site Platform is the container layer of the CMS. Every CmsSite document is bound to exactly one OrgNode in a tenant — FIPJP, a continental confederation, a national federation, a district, or a club — and inherits scope rules from the existing tenant model. A site-creation wizard walks an admin through three decisions: site archetype (federation-formal, events-heavy, shop-first, community-minimal), branding (logo, primary/accent color, sender-name) and the URL strategy.

Every site is immediately reachable on a generated platform subdomain such as norrbotten-bk.petanque-life.com via wildcard DNS, so editors can start working before any external DNS is configured. When the tenant is ready to go public on its own brand, the Custom Domains module (F18.14) hooks into Cloudflare for SaaS to issue certificates and route traffic. Sites can be activated, deactivated or hidden from the public directory without losing pages or media — deactivation flips an is_published flag that the Next.js renderer respects on every ISR build.

Tenant-scoped management means a federation admin sees and can manage every club site under the federation in a single list view, while a club editor only sees their own site. Cross-tenant management is impossible — a Swedish federation admin never lists French clubs. A platform-wide site directory (opt-in per site) lets players and visitors browse all federation and club websites by country, region, or activity, surfacing the full ecosystem in one place.

The directory is fed by the same CmsSite collection, filtered by visibility and indexed for fast lookup.