Deep dives into the Next.js ecosystem: App Router, server components, rendering strategies, and production architecture.
11 posts in this category.
Generating social card images on demand from a serverless function feels modern. It's also slow, expensive, and fragile. Static sites can pre-render every OG image at build time, cache it forever, and never pay for it again.
For a decade, smooth page transitions meant shipping a SPA router and giving up the simplicity of multi-page architecture. The View Transitions API ends that tradeoff — and it's finally supported everywhere that matters.
Structured data, Open Graph, sitemaps, and RSS — all generated at build time, all under your control, and none of them require a plugin that phones home.
Sharp at build time, next/image in static export, WebP/AVIF variants, blur placeholders, responsive srcset — image optimization used to be a manual chore. Now it's a build step.
You've decided WordPress isn't worth the maintenance anymore. Here's the full migration playbook — content extraction, markdown conversion, image handling, redirects, and deployment.
tRPC is excellent. It's also overkill for most projects. Here's how to get type-safe API routes in Next.js using route handlers, Zod, and shared types — no extra dependencies required.
The App Router shipped with promises of simpler data fetching, better performance, and a cleaner mental model. Two years of production projects later — here's the honest verdict.
No database. No admin panel. No plugin updates at 2am. Just files.
Vercel is the obvious choice. Here's why you might not want it — and how to get the same result on Render with full control.
A real look at the pipeline I built to take a client intake form and turn it into a deployed website — with minimal human involvement.
From a Facebook experiment to the backbone of the internet — the story of two frameworks that rewired how developers think about building for the browser.
