Every spoke. One template.
The canonical marketing template every NOWAITN app forks from. Editorial hero with an animated pipeline, a one-viewport capability section, and a FAQ closer — wired into shared Blade components so the look stays consistent.
Mobile-first · Blue/white/black · Component-driven
Same shell. Same identity. Less friction.
Every NOWAITN app starts from this scaffold so the platform looks and feels like one product, not seventeen.
Canonical marketing components
A shared hero, capability section, and FAQ mean every app reads as part of the same platform — no per-spoke divergence in layout or palette.
Mobile-first by construction
Every section sized to fit one viewport on a portrait phone. Typography, spacing, and ambient chrome all scale up cleanly to desktop.
Sync-driven mesh consistency
The shared header, footer, app chooser, chat widget, and component set live in one source of truth and fan out to every spoke via sync-app-registry.sh.
What forking the scaffold means.
No — the canonical hero, unlocks, and FAQ cover the standard welcome shape. If your spoke needs a different shape, drop in a per-spoke partial. The shared header, footer, and chat widget should always render so cross-app navigation stays consistent.
Marketing surfaces (welcome page chrome, hero, unlocks) stay on the platform palette: blue / white / black. Per-app accent colors are reserved for the in-app surface (sidebar, app icon tile, dashboard chrome) where color is a navigation aid.
The scaffold is the source of truth. Run bin/sync-app-registry.sh from the monorepo root and the change fans out to every spoke. The script is idempotent and detects drift; --check mode is suitable for CI.
The scaffold ships /sso/* routes that talk to the Hub at nowaitn.com. As long as the spoke is registered in config/apps.php and HUB_SSO_SECRET is set on the .env, sign-in is automatic — your spoke does not host its own login form.