Portfolio Website v2 was the previous version of my personal website, built with Gatsby and Strapi CMS. It connected a fast static frontend with editable CMS content, giving me a portfolio that was easy to publish, quick to load, and simple to update without changing code for every project.

Gatsby and static performance

Gatsby was a good fit for this version because it generated static pages ahead of time. That meant fast page loads, good SEO foundations, optimized assets, and a reliable deployment flow for a content-heavy personal site.

Strapi-powered content

Strapi handled the project data, images, links, and descriptions. This gave the site a cleaner separation between content and frontend code, and made it easier to keep the portfolio updated as I added new work.

Why I moved on

I really loved working with Gatsby ❤️, but over time it stopped feeling actively maintained and the ecosystem became harder to rely on. This version still represents an important step in my portfolio, but it also made the later move to Next.js feel like the right direction.