Visual Freedom And Shared Core

Visual Freedom & Battle-Hardened Shared Core

1. Executive Summary

Traditional multi-site platforms share rigid UI component templates across tenants, causing every client site to look like a slightly re-skinned clone.

SiteSwarm inverts this boundary:

1. Battle-Hardened Shared Functionality: Domain validation, state machines, security verification, and storage/service connectors live in shared capability packages (CAPABILITY_MANAGEMENT.md) where they are tested once and hardened across the fleet.
2. Unconstrained Storefront Visuals Guarded by Strict Linting: Client storefronts (apps/<client>/) author bespoke markup, layout composition, and styling per client without shared view templates. Quality, accessibility, and performance on the storefront are enforced through automated architectural, WCAG 2.1 AA accessibility, and mobile performance linters rather than restrictive visual templates.

flowchart LR
    Core["Shared Headless Capabilities\n(Validation, State, Edge Connectors)"] --> App["Bespoke Client Storefront (apps/<client>)\n(Custom Markup, Typography & Layout)"]
    App --> Gates["Automated Quality Gates\n(Accessibility, Perf & Edge Safety)"]

---

2. Separation of Headless Mechanics from Storefront Presentation

Layer	Ownership & Location	Architectural Rule
Functional Mechanics & Contracts	Shared platform packages (packages/*)	Tested once; exposes headless schemas (./schemas), browser state controllers (./client), and edge route handlers (./server).
Storefront Presentation & Brand Identity	Individual client workspace (apps/<client>/)	100% bespoke Astro/HTML markup, typography, and CSS authored per client; never constrained by a global visual theme or shared UI template.
Quality & Safety Verification	Automated CI & Governance Gates	Enforces WCAG 2.1 AA contrast/semantics, zero-CLS responsive layout discipline, and strict bundle size budgets on every bespoke storefront.