zeekay
4c0d15fb5e
Fork of hanzo-apps/hanzo-starter: identical stack, providers, vite.config, auth (PKCE @ hanzo.id) and deploy contract. Two views in @hanzo/gui — a typographic Resume and an Editor — over profile + entries Base collections (schema.sql, org-scoped). Light theme, ATS-clean, prints as one clean page.
5.0 KiB
Curriculum — Resume
A polished, print-friendly online resume you fork on hanzo.app and deploy live on Hanzo Cloud. Write your experience, projects and skills once; Curriculum renders one clean, typographic page — and prints it just as clean.
- UI —
@hanzo/gui(the Hanzo design system) under Vite + React 19. Light theme, generous whitespace, an ATS-clean single column. - Auth —
@hanzo/iam, OAuth2 PKCE against hanzo.id. No local passwords — IAM owns every credential interaction. - Data —
@hanzo/base, the IAM-native, org-scoped data plane. Your resume is two real Base collections.
Two views
- Resume — the read surface. Your header (name, title, summary) followed by every entry grouped into sections. Hit Print and the app hides its toolbar so a single clean page prints.
- Editor — the write surface. Upsert your header and add or remove line items under Experience · Projects · Skills · Education. Every write is scoped to your org.
Stack (pinned)
| Package | Version |
|---|---|
react / react-dom |
^19.2.4 |
@hanzo/gui + @hanzogui/config |
7.3.0 |
@hanzo/iam |
^0.13.1 |
@hanzo/base |
^0.2.1 |
vite |
^6 (@vitejs/plugin-react) |
react-native-web |
^0.21.0 |
typescript |
5.9.3 |
Run it
npm install
npm run dev # http://localhost:5173
npm run build # tsc --noEmit && vite build -> dist/
npm run preview # serve the production build (SPA fallback on)
Out of the box it runs against live Hanzo (hanzo.id + api.hanzo.ai) — no
config needed to see the sign-in flow. Copy .env.example to .env to point at
a different environment.
Environment contract
Only VITE_-prefixed vars reach the browser (this is a static SPA — there is no
server). Defaults in parentheses.
| Var | Purpose |
|---|---|
VITE_HANZO_IAM_URL (https://hanzo.id) |
OIDC issuer. |
VITE_HANZO_CLIENT_ID (hanzo-app) |
IAM application (<org>-<app>). Its redirect-URI list must allow this deploy's /auth/callback. |
VITE_HANZO_REDIRECT_URI (${origin}/auth/callback) |
PKCE redirect. |
VITE_HANZO_BASE_URL (https://api.hanzo.ai) |
Browser-reachable Hanzo Base data plane. Deploy injects the provisioned URL. |
How auth works — ambient IAM
login() starts an OAuth2 PKCE S256 redirect to hanzo.id; hanzo.id returns
to /auth/callback, where handleCallback() exchanges the code for tokens
(stored in localStorage, refresh-aware via offline_access). Every deployed
app is a static site at <slug>.hanzo.app; there is no server token — the
SPA authenticates the user in the browser and carries the resulting IAM JWT to
Base.
The one deploy requirement: the IAM client (VITE_HANZO_CLIENT_ID) must list
this origin's /auth/callback as an allowed redirect URI. Register a
https://*.hanzo.app/auth/callback wildcard on the shared client, or a dedicated
hanzo-<app> client per fork.
How data works — Base from schema.sql
schema.sql is the app's databaseSchema (SQL DDL). On publish,
Hanzo Cloud translates each CREATE TABLE into a Hanzo Base collection
(provisionBaseFromDDL, additive + idempotent):
profile—name,title,summary. One live row per org (the editor upserts the newest).entries—section,title,detail,when. Every line item, grouped bysection.
Base manages id/created/updated/owner/org, stamps owner+org from
the verified IAM principal, and scopes every row to the caller's org
(@request.auth.org_id = org) — a teammate in your org sees the row; other orgs
cannot. At runtime src/views/resume.tsx reads and src/views/editor.tsx writes
those collections through @hanzo/base/react carrying the IAM token.
Deploy — Hanzo Cloud
hanzo.yml declares a static build (npm run build → dist/,
served at <slug>.hanzo.app) plus the Base schema to provision and the env to
inject. Do not build a container image locally — Hanzo Cloud owns builds and
deploys. CI here only proves the template compiles green.
Layout
src/
main.tsx entry
providers.tsx GuiProvider(light) -> IamProvider -> BaseProvider(client=IAM-token)
app.tsx route (/auth/callback) + auth gate
gui.config.ts createGui(defaultConfig from @hanzogui/config/v5)
iam.config.ts IAM PKCE config
env.ts the VITE_ env contract, one place
lib/base.ts BaseClient carrying the IAM bearer token
lib/models.ts Profile + Entry row types
lib/sections.ts canonical sections + ordering
auth/callback.tsx PKCE return leg
views/ signed-out (landing) · home (shell) · resume · editor
schema.sql databaseSchema -> profile + entries collections on publish
hanzo.yml Hanzo Cloud build/deploy manifest