// Colophon
This site is exhibit A.
A portfolio should demonstrate the work, not just describe it. This page documents the architecture decisions behind the site itself — the same reasoning I bring to systems that are considerably larger.
01Fully static, no moving parts
Every page is generated at build time. No server, no database, no cookies, no cross-site tracking — the only measurement is anonymous, cookieless page counts (Vercel Web Analytics). There is nothing to patch at 3 a.m. and nothing to leak.
02Diagrams are the imagery
A solutions architect's work product is the system diagram, so the site's visuals are hand-coded, animated SVG architecture diagrams — each case study rendered in the same visual language, a few kilobytes each, no stock photography.
03One content model
All content lives in a single typed TypeScript file. Pages, structured data and the AI-crawler summary derive from it — change a fact once and every representation updates.
04Built to be read by machines too
Person, FAQ, Article and ItemList structured data (JSON-LD), per-page canonicals, a sitemap, and an llms.txt summary for AI crawlers. Search and AI visibility treated as an architecture concern, not an afterthought — the same approach that put a client's site at №1 on Google in a day.
05Pinned, verified versions
Next.js 16.2.10 · React 19.2.7 · Tailwind CSS 4.3.2 · TypeScript 5.9.3 — exact versions, checked against the registry at build day, no ranges.
06Costs about a domain name
Static output on Vercel's free tier plus the domain: roughly $12 a year, total. Architecture is also knowing when the right amount of infrastructure is almost none.