Personal platform · 2026
Most developer portfolios are built once, look sharp for a year, and then rot because adding a post means fighting the codebase. I wanted the opposite trade: slightly more structure up front so that publishing a lesson is editing one typed array.
Content lives in typed TypeScript arrays under `src/data`. That sounds primitive next to a headless CMS, and it buys three real things: the compiler catches a malformed lesson before it deploys, content is versioned with the code that renders it, and there is no external service to go down, expire, or start charging.
Bodies are a discriminated union of block types — text, list, code, note, quote — so the renderer is one exhaustive switch. Adding a block type is a compiler error everywhere it needs handling, which is exactly where you want to find out.
The previous version pulled in a full animation runtime to fade sections in on scroll. That is now one IntersectionObserver hook and a CSS transition on a data attribute — about thirty lines, zero dependencies, and it runs on the compositor.
// the whole reveal system
const io = new IntersectionObserver(
(entries) => {
for (const entry of entries) {
if (!entry.isIntersecting) continue;
entry.target.setAttribute('data-shown', 'true');
io.unobserve(entry.target); // reveal once, then stop paying for it
}
},
{ rootMargin: '0px 0px -12% 0px' },
);