addison, cyan and dallas-images) and the private studio behind them. It covers the front end and back end, how each deployment knows which site it is, how the databases are split, and where things live in the repository.
Architecture
The project has three layers, and every site runs the same code in each of them.
Code that both the browser and the server need, such as site configuration, node types, the review model and theme rules, lives in
config/. Server-side relative imports use .js extensions because the serverless functions run as real ESM; pnpm check:esm enforces this for api/ and db/.
There is no app-wide state library. Services in src/services/* call /api with a bearer token, and components use React state, context, small module-level stores and SWR. Board runs are driven from the browser, one request per variation, so a long run never sits inside a single function call. The review UX audit runs on the server, where one whole-review Claude call and one call per screen start together.
One codebase, three sites
Each site is its own Vercel project with its own Neon database. Nothing is shared between sites at runtime. Only thesite_settings table is keyed by site; photos, users and categories have no site column.
A deployment learns which site it is from two environment variables:
VITE_SITEis read by the browser bundle and inlined at build time, so each Vercel project ships a bundle for exactly one site.SITEis read at runtime by the serverless functions and by scripts.
resolveSite() in config/sites.ts, which looks the key up in the SITES table. The match is exact after trimming whitespace.
On the server, getSite() in api/_lib/site.ts layers SITE_* environment variables over the resolved site with applySiteOverrides(). This is how a site created from the admin, which has no entry in config/sites.ts, gets its own name, domain, origins and email sender. Unset variables keep the compiled value.
There are two layers of site identity:
- Identity and security (
siteConfiginsrc/site.ts): canonical domain, CORS origins and the email From address. It is fixed at build time and not editable at runtime. - Content and theme (
useSiteSettings()): name, tagline, colours, fonts and the shader background, loaded from/api/site-settingsand edited by an admin in Settings. See Site settings.
Locally,
scripts/dev-stack.mjs copies VITE_SITE into SITE, so pnpm dev, pnpm dev:addison and pnpm dev:cyan set both from one value.Repository map
src/App.tsx, and admin sections in src/pages/AdminPage.tsx. The database schema is db/schema.sql plus the patches in db/patches/; db/schema.ts is generated from a site’s database with pnpm db:pull, and the patches remain the only thing that creates or alters a table.
Developer guides
Local setup
Install, pull environment variables and run the dev stack for one site.
Databases
The per-site Neon databases, migrations, Drizzle, and why local dev uses live data.
Deploying
Vercel projects, the production build, and migrating before you ship.
Testing
Vitest in real Chromium, the node project, and the lint gates.
API
Every route under
api/, the auth model, and the generated OpenAPI docs.MCP server
Connect Claude or another MCP client to read and update the studio.