Personal site + MDX blog. Next.js 16 · React 19 · TypeScript 5 · Tailwind CSS 4 · velite · Shiki. Deployed on Vercel.

bun install
bun run velite       # build content once so types resolve
bun dev              # http://localhost:3000

Content changes during dev:

bun run velite:watch # in a second terminal

See CLAUDE.md for full conventions. Short version:

• content/blog/<slug>.mdx — frontmatter (title, description, date, category, tags, cover) + MDX body. Supports <Note> and <Warn> shortcodes.
• content/projects/<slug>.mdx — frontmatter (title, summary, category, stack, repo, url, images, highlights) + MDX body.
• content/site.json — single source of truth for hero / nav / metadata.
• content/experiences/*.json, content/education/*.json, content/data/{skills,stacks,socials}.json — typed arrays.

All content is Zod-validated at build time by velite.config.ts. A broken schema fails the build with a precise error.

Images live at /public/images/<area>/<slug>/<file>.webp. Drop them in and reference from frontmatter or MDX.

• Terminal-aesthetic (Warp / Ghostty flavor). Geist Mono everywhere. OKLCH tokens in src/styles/tokens.css.
• Dark default, .light override. Toggle via ThemeProvider.
• Motion: CSS-only transitions. No JS animation libraries.
• prefers-reduced-motion: reduce zeros the duration tokens globally — single source of truth.

1. Push to GitHub.
2. Import the repo in Vercel.
3. Framework: Next.js (auto-detected). Build command: default (next build; velite is invoked via the build script).
4. Set env var NEXT_PUBLIC_SITE_URL if you want to override the URL coded into content/site.json (optional — the canonical is read from content/site.json.url).

bun run build
bun start   # or any Node-compatible runtime that serves Next output

All routes prerender statically at build time, plus one RSS route (/feed.xml).

See CLAUDE.md for conventions, content schema, and contributor rules.