This website, built in public
ProblemThe portfolio itself — spec, decisions, and what broke — kept as a build doc.
StackNext.js 16 · React 19 · Tailwind v4 · TypeScript
StatusActive · started Jun 2026
The portfolio itself — spec, decisions, and what broke — kept as a build doc.
The problem
A portfolio that claims "demo vs. deployment honesty" has to model it. So this site keeps its own build log, including the parts that didn't go to plan.
The build
Next.js 16 App Router, Tailwind v4 with the brand palette as theme tokens, and
the engineering title block as the signature element. Content is MDX in the
repo — the repo is the CMS. The running log lives in docs/build-log.md.
What broke
×01The hero engraving asset wasn't ready, so a broken <Image> shipped on first
paint. Swapped in a cross-hatch placeholder that reads as intentional until
the real art lands.
Results
Foundation, landing, the content system, and the blog + projects pages are live. Search and the about page are next.
Next rev
⌘K command-palette search over a build-time index; RSS; OG image generation with the title-block footer.