Thoughts on content systems, frontend architecture, and the tools we use daily. Occasionally opinionated.
Every enterprise headless build hits the DAM question eventually. What Sanity's Media Library and Mux already cover, what a DAM really costs in 2026, and the one case where a dedicated DAM still earns its keep.
How to render 1200x630, 1080x1080, and 1080x1350 social images from one next/og template in turbo-start-sanity, with real render timings.
The AI shift didn't replace SEO. It raised the bar. Here's what moves the needle across search, AI answers, speed, and accessibility, and what's noise.
Instant navigations explained in plain English, plus our upgrade to 16.3, the cache components PR we parked, and the 341KB we cut instead.
How a Remotion agent skill stops Claude Code hand-rolling scene chrome: the shared kit, motion tokens, and the drift that forced us to build it.
We read every 'top Sanity agencies' listicle, noticed who writes them, and decided to do it properly. Number one may not surprise you.
AEO, GEO, or just SEO: the playbook is the same. Metadata, JSON-LD, sitemaps, and content negotiation, implemented on a production Next.js site.
Content automation earns its bad name when a model makes decisions that should be rules. Here's where we draw the line, built on the Vercel AI SDK.
Five of our internal skills are now open SKILL.md files, discoverable at /.well-known/agent-skills/index.json. What they do and why we gave them away.
