Blog

Building this portfolio

Why I moved from static content to a small CMS—and what I learned shipping the backroom panel.

1 min read

Why a CMS at all

I wanted the public site to stay fast and polished, but I also needed a place to update projects, experience, and writing without redeploying. A lightweight backroom admin on the same Laravel app felt like the right balance.

Stack choices

  • Laravel + Inertia + Vue for one codebase and SSR-friendly pages
  • Markdown for posts so drafts stay readable in git and in the editor
  • MySQL for structured portfolio content

What’s next

More posts on implementation details, performance tweaks, and design decisions. If something here resonates, get in touch—I’m open to interesting work.