Sign-in steps (password, sign-up, email code, two-step sign-in and its setup with recovery codes, privacy notice, news question), forgot and reset password, the account page, admin (people, deletions, church profile, linked products, settings, notice, licence, audit) and setup. Strict CSP with a nonce per page; church colours from the profile. @crosscode/ui gets its first components (shell, card, fields, buttons). Plan: roles stay in each product (asked 2026-11-18). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
622 B
622 B
@crosscode/ui
Shared UI for the products a church's members see: the branded shell, cards, buttons, form fields and notices. First used by Accounts' sign-in and account pages (phase 3); the Church Website and App build on it (phases 4 and 6).
- Plain React + Tailwind, no runtime dependencies. Apps compile the source
(
transpilePackages: ["@crosscode/ui"]innext.config.ts) and addpackages/ui/src/**/*.{ts,tsx}to their Tailwindcontent. - The church's colour comes from the CSS variables
--brandand--brand-dark(r g b), which each app sets fromcrosscode.church/1(Tailwind colourbrand).