My Frontend Stack in 2026

People ask what I use to build sites like this one. The honest answer is that the stack is fairly boring — and that is intentional. I would rather ship with tools I know well than chase whatever is trending this month.

Here is what I am using in 2026 and why each piece is still on my list.

The core

Next.js handles routing, server components, and deployment without much ceremony. For a personal site with a blog, games, and a few static pages, it covers most of what I need out of the box.

TypeScript is non-negotiable for me now. The small upfront cost pays back quickly when refactoring or coming back to a project after a few weeks.

Tailwind CSS keeps styling colocated and predictable. I pair it with shadcn/ui for accessible primitives I can customise instead of fighting a heavy component library.

Content and motion

MDX lets me write blog posts in Markdown with React components where it helps — callouts, custom layouts, that kind of thing.

Motion (formerly Framer Motion) is there when I want subtle animation. I try not to overuse it; a little movement goes a long way.

What I am not optimising for

I am not trying to adopt every new framework or rebuild the site every six months. The goal is to build quickly, keep complexity low, and spend most of my time on content and features people actually see.

If your stack looks different, that is fine. The best tools are the ones that get out of your way and let you finish things.