Layouts
Shared page shell, SEO handling, and footer/header structure.
Workspace Example
Shared packages, local branding, independent deploys.
This second site proves the monorepo pattern: it reuses the shared layout and UI packages while keeping its own data, colors, copy, and pages.
Start a projectWhat is shared?
Header, footer, base layout, contact form, FAQ accordion, and Tailwind foundation.
Shared system, different expression
UI
Reusable form, review card, FAQ accordion, and slider components.
Theme
One Tailwind foundation, with site-level brand tokens layered on top.
How a new site gets added
Create `sites/new-domain/`, add local `data/` files, import the shared packages, and build that site on its own Cloudflare Pages project.
FAQ
Why keep this site in the workspace?
It shows the pattern for new deployments: local data, shared layout, shared UI, and independent build output.
Can this site diverge from the shared system?
Yes. A site can add custom pages, custom components, or even wrap the shared layout with its own variants.