From Svelte to Nuxt: Rebuilding my portfolio in 2025
It's 2025, and I've just rolled out a complete rebuild of my personal website. I've migrated from a Svelte and Sapper stack to Nuxt, Tailwind CSS and a Turborepo monorepo. It wasn't a cosmetic update but a full rewrite, driven by five years of changes in the frontend landscape and by the wish to use the same tools at home as at work.
The 2020 decision: Why Svelte?
Back in 2020, when I built the first version of this site, the Vue ecosystem was in the middle of a big transition. Vue 3 was in beta, and it was released right after I had finished my website. The first two years of Vue 3 were painful, and Nuxt 3 wasn't stable until November 2022. The migration path from Vue 2 was uncertain, and frankly, the future felt a bit shaky.
At that time, Svelte and its companion framework, Sapper, were a compelling alternative: fast, simple and stable. It was the right choice for its time.
The tipping point: Ecosystem vs. DIY
Five years later, the tables have turned. Svelte is still a great framework, but the Nuxt ecosystem has grown to cover almost everything a site like this needs.
With my old Sapper site, I had to build many features from scratch: SEO meta tags, content management for the blog and image optimization. I learned a lot, but maintaining that custom code became a chore. On top of that, the migration from Sapper to SvelteKit was a big project that I simply didn't have the time for.
Nuxt, on the other hand, has modules that handle these concerns out of the box:
- @nuxt/content for file-based content management.
- @nuxtjs/seo for SEO and metadata, with defaults that work without any configuration.
- @nuxt/image for image optimization.
- @nuxt/icon for using any icon set without shipping the whole set.
With that covered, I can focus on writing.
Aligning with my daily workflow
The frontend side of my day job is Vue 3 with the Composition API, TypeScript and Tailwind. It makes sense for my personal site to use the same technologies I use every day. Working with Nuxt feels natural and simple, once you get its philosophy.
A quick look at the new stack
Nuxt is the core of the application. Tailwind CSS handles the styling, and daisyUI adds components and the light and dark themes. Turborepo manages the monorepo, which keeps the main app, the shared configurations and the internal tools in one place.
From Bulma to Tailwind CSS & daisyUI
In the previous version of my site, I used Bulma, and it's a great CSS library. However, my day-to-day work is rooted in Tailwind CSS. Switching between the template and a separate CSS file now feels like double the work, since you rarely reuse classes across .vue or .svelte components.
Because I use Tailwind every day, I've started to "think" in Tailwind when it comes to styling, and once you think that way, it's hard to go back. For this rebuild, I've paired it with daisyUI. It lets me opt in to pre-styled components when I don't want to overcomplicate things, and opt out to build something fully custom without losing any of Tailwind's benefits. It also comes with a theme system designed for Tailwind.
The role of AI in development
This rebuild was also a chance to try the latest generation of AI coding assistants. I've tried (too many) tools, like the Gemini CLI, Aider and GitHub Copilot. Some days they felt like superpowers, and others like the flu. If I stick to my goal of writing more, I'll tell you more about each of them soon.
What's next?
I want to write more, share some ideas I've been thinking about for a long time, and maybe start contributing to an open source project.
Thanks for reading. See you around.