🏗️ Architecture Overview static reference Last reviewed 2026-05-19
Five-layer model showing how the public site, hub, sections, roles, and data fit together. This part doesn't change often. Companion: system-overview.md · dedicated diagram page .
Same Solutions architecture: domains, projects, sections, access roles, data layer
Multi-layer architecture diagram showing how samesolutionsllc.com, hub.samesolutionsllc.com, and party.samesolutionsllc.com route to website and substrate projects, organized by sections with role-based access and data sources
Layer 1 — Domains (what users type)
samesolutionsllc.com
Public business site
hub.samesolutionsllc.com
Personal/family hub
party.samesolutionsllc.com
301 → fireworks page
Layer 2 — Cloudflare projects (where files live)
samesolutionsllc-website
Pages · static · public deploy
samesolutions-equipment-service
Pages · substrate · noindex
Layer 3 — Sections (organized content)
/ landing
/manage app
/our/
/cece/
/jon/ /win/
/personal/ + /customer-jobs/ + /handoff-blocks/
Layer 4 — Access roles (who sees what)
owner
Sam · CeCe in own area
member
CeCe in /our/ · future stylists
viewer
Sam in CeCe's salon
Layer 5 — Data (where state lives)
KV namespace · events
/data/*.json · projects
_data/*.json · schedules