Why I rebuilt my portfolio (again)

Losing my old source code forced a full reset. Instead of restoring from a backup, I used it as a chance to rethink the whole site — starting with why a portfolio needs a blog at all.

The old site

The previous version was a straightforward Next.js + Chakra UI portfolio. It worked, but it was purely a showcase — no writing, no way to talk through the why behind a project, just a list of finished things.

What changed

This version treats the blog as a first-class citizen instead of an afterthought. Every project gets a project card, but the actual depth — the debugging stories, the decisions, the dead ends — lives in posts.