# Frontend Oolong's frontend is Solid + Vite under `web/`. The Go server serves the embedded shell, the shared CSS, OAuth routes, and the JSON API. User records still live on the user's PDS. No lexicon or record migration is needed. ## Development ```sh pnpm install just run-oolong pnpm run check:web pnpm run test:web pnpm run build:web just e2e ``` `pnpm run build:web` builds `web/dist` and copies it to `internal/web/spa/build` for Go embedding. Build before compiling or running Go. With `OOLONG_DEV=1`, the server reads `web/dist` on each request, so a rebuild does not need a Go restart. `pnpm --dir web run dev` starts Vite with API/auth/static proxies; set `SOLID_DEV_BACKEND` to override `http://localhost:18920`. Production assets use `/web-assets/` with content hashes. Shared CSS uses Go's content-hashed URL. The shell carries the request's CSP nonce, safe display-only session attributes, and app-owned public-page metadata. OAuth tokens never reach the browser bundle or bootstrap attributes. The attributes avoid an authentication flash while the client refreshes `/api/session`. ## Pages Solid owns the homepage, My Tea, onboarding, all record forms and detail pages, backlinks, profiles, settings, notifications, signup, moderation, About, Terms, and AT Protocol information. Vendor, vessel, and infuser forms have full-page `/new` and `/{id}/edit` routes. `AppLink` intercepts only application page URLs. OAuth, login/logout, scope upgrades, downloads/exports, image URLs, and external links use full navigation. Clients read data from `/api/*`; see `docs/api/`. Known HTML routes with trailing slashes redirect to their canonical path. The shared Oolong CSS remains the styling baseline. Forms and page sections keep their existing fields and structure. Copy identifies records and actions, explains requirements, or reports state; decorative text is omitted. ## Tests `pnpm run check:web` checks the app, Playwright config, and E2E specs. Unit tests live in `web/src/test/`. Playwright configuration is in `web/playwright.config.ts` and browser tests live in `web/e2e/`. `just e2e` builds the frontend and runs the suite against `tests/e2e/server`, an isolated loopback fixture using the real Go routes and an in-memory record store. The browser suite intentionally starts small: navigation/auth smoke coverage and record create/edit/delete lifecycles. It does not pin form layout, exercise real OAuth, or write to a live PDS. Test authentication and synthetic records exist only in the fixture binary, never in the production server. Set `CHROMIUM_PATH` to use a system Chromium, or install Playwright's browser with `pnpm --dir web exec playwright install chromium`. Failures retain screenshots and traces under ignored `web/test-results/`.