🖥️ portfolio: the personal site

notes + rendered layer docs (through MILL) are all built and served today by server.ts,

and the zero-ops GitHub Pages deploy is live (batch/export via

.github/workflows/pages.yml). The productivity views (Notes,

Calendar, Mail, and About) are all live. New here and want to make a small edit? →

HACKING.md (route → source map + "which file do I open").

Quick start

Needs Bun, pinned to 1.3.14, the same version CI runs. There is no bundler and no build step: Bun runs the TypeScript straight from source, so the dev server is the whole toolchain.

bun install
bun run dev              # http://localhost:3000  (hot reload, no build)

Then visit:

| Route | What | |---|---| | / | the hero desk: watch the AI drive the real surfaces | | /bread | the stack directory: every layer, one card shape | | /notes | the blog and the whitepaper, rendered through MILL | | /catalog | the live GRAIN component catalog |

The checks this repo holds itself to, all runnable locally:

bun test                 # the unit suite
bun run check            # TypeScript, no emit
bun run export           # the static build GitHub Pages publishes

What it is (and isn't)

• It's a consumer of the stack: a bespoke app, re-skinning GRAIN via its public seams.
• It uses MILL only for content

• Organizing concept: a populated productivity app (Notes · Calendar · Mail · About) with the AI

Read next

• PLAN.md, the execution plan: export → Pages, in-browser AI demo, the build pieces.
• FEATURES.md, the feature menu (north star, the desk, anti-features, reuse table).
• CONTENT-BACKLOG.md, the content to author (guardrails: public repo, neutral).
• GRAIN-PAGE.md · BATCH-PAGE.md, the /grain and /batch showcase plans.
• PHILOSOPHY.md, the beliefs the site proves.