Colophon
How this document is built.
- Concept
- The portfolio is a draft red herring prospectus for one engineer. It reads as a document, so the plain-text version and the designed version are the same content.
- Framework
- Next.js App Router with Cache Components. Every page is prerendered; the listing chart's data revalidates every 6 hours.
- The document
- three.js, one mesh per sheet. Pages bend in a vertex shader (φ = θ + k·x, integrated in closed form) and spring toward their targets. Page textures are drawn at runtime from the site's own section text. The chunk loads during idle time after first paint, over an SVG drawing of the same cover.
- Scroll
- No smooth-scroll library. Sticky sections plus one passive, rAF-throttled scroll reader per scene. Bidirectional by construction.
- Register
- Filters animate with the View Transitions API, not a motion library. The force-directed map loads only when you open it.
- Content
- One MDX file per project, validated by a strict Zod schema. Every metric must name its source or the build fails. Tickers, listing markers, risk factors, the register, sitemap, JSON-LD and social images all come from that file.
- The gift
- Allotment letters are signed tokens (HMAC-SHA256) carried in the URL. Nothing is stored, so there's no database to leak.
- Honesty
- Exhibits replay real system shapes with synthetic data and say so. Client and employer names are left out. Numbers come from git history, test runs, the résumé, or my own confirmation.
Open the console and try aman.help(). Back to the prospectus