I Rebuilt My Developer Portfolio with Nuxt 4 + Strapi and Made It Open Source
If you've been putting off rebuilding your portfolio because it feels like a weekend project that always gets pushed to the following month, I understand. Mine sat on Vue 2 and CosmicJS for years. ...

Source: DEV Community
If you've been putting off rebuilding your portfolio because it feels like a weekend project that always gets pushed to the following month, I understand. Mine sat on Vue 2 and CosmicJS for years. It still worked, but it carried the kind of technical debt that makes you hesitate every time someone asks for the repository. This is the story of how I finally rebuilt it from scratch, why I made certain architectural decisions, and why I ended up open-sourcing it as a reusable Nuxt 4 + Strapi portfolio starter. The Problem With Most Developer Portfolios Here's a pattern I've noticed: developers spend a lot of energy on the initial build, then abandon the thing entirely. The portfolio accumulates outdated tech, unmaintained dependencies, and content that no longer reflects who they are. The reasons are usually the same: No CMS — updating content requires a code change, a commit, a deploy. That friction kills momentum. Outdated stack — Vue 2, Create React App, Gatsby v2, Jekyll. Not inherent