All writing

From WordPress to Hugo to Next.js and Sanity: Rebuilding This Site a Third Time

By Bronson Dunbar ·

In December 2022 I wrote Goodbye WordPress!, about moving this site to Hugo and Netlify. My hosting bill dropped to zero, my Lighthouse scores jumped, and I could write in Markdown.

Since then the site has been rebuilt twice more. This post covers all three moves, and why the latest one isn't really a blog at all.

Rebuild one: WordPress to Hugo (2022)

The reasons are all in the original post: the cost of WordPress hosting, slow pages, tedious theme updates and backup plugins. Hugo with Forestry.io as the CMS and Netlify for hosting fixed all of that. Everything lived in GitHub, builds were nearly instant, and hosting was free.

Then Forestry.io shut down in 2023, which left the Hugo site without its CMS. That was part of the reason to move on. The other part was Sanity itself, which felt a lot more modern.

Rebuild two: Next.js and Sanity (2025)

In February 2025 I rebuilt the site on Next.js with Sanity as the CMS. By then it was much more than a blog: posts and tutorials, an apps section, a course, open-source projects, a resource library, videos, Algolia search and a contact form.

Sanity gave me structured content with a proper editor, and an embedded Studio at /studio, so the CMS shipped with the site. I kept writing in Markdown, stored in a plain text field, which kept the posts portable.

Overall, though, it didn't work well as a portfolio. I wanted a site that showcased my projects properly, while keeping the blog posts for SEO, and that version did the opposite: the projects were buried among everything else.

Rebuild three: a portfolio (2026)

By 2026 my work had changed. Alongside my day job, I now build and run three products and four games, and the old site led with blog posts. Someone visiting couldn't see what I actually make.

So the new site starts from a different brief: the work leads, and the text is kept to a name, a category and one line per project. The home page is a grid of everything I've built, filterable into software and games. The writing is still here, but it's one section among several.

What changed technically:

  • Next.js 16 with the App Router, React 19 and its View Transitions. Opening a project morphs its tile into the project page's hero image.
  • Same Sanity project. The new site points at the same dataset as the old one, so all 43 posts came along with no migration, and their old /post/<slug> URLs still work.
  • Projects in Sanity too. They started as a local TypeScript file, and a seed script copies them into Sanity with their images, so the Studio can manage everything.
  • Live data from each project. Tiles show each project's live link-preview image, and game pages show their latest devlog entries, both read from the live sites (how that works).
  • Redirects for the old structure. /blog, /tutorials, /portfolio and /apps all point somewhere useful, and so do the /blog/<slug> URLs from before the Hugo move.

The design

The brand is a keycap with a custom "bd" legend. Keyboards drive both my software and my games, so it's the key you press to start anything. In the hero you can press it: click it or press any key on your keyboard, and it presses down, the matching key lights up on a faint keyboard behind it, and a small keycap with the letter you pressed flies off.

Everything else stays out of the way: a near-black canvas, off-white text and one accent colour, violet. The projects supply the rest of the colour through their own images.

Moving the old content safely

Moving 43 posts across rebuilds always leaves things behind. While preparing this launch I found:

  • About 80 screenshots that only existed on the old site and would have broken. They're now part of this site.
  • Links that had rotted. One old CMS domain now redirects to a spam site.
  • Tutorials that no longer worked. Several AI tutorials used packages and models that don't exist any more. They've been rewritten and tested.

If you're rebuilding your own site, check links and images in the old content before launch, not after.

What three rebuilds taught me

Two things I'd pass on:

  • A rebuild is worth it when your direction changes. If what you do has moved on, your site should move with it. A rebuild is also a good excuse to try newer technologies on a project you control.
  • Choose a CMS for your needs. Sanity works well for me, but it depends on what you need. For something simple, it could be too much, given the initial setup it requires.

The short version: your site should show what you're doing now. For me in 2022 that was writing, and in 2026 it's building. This version is the first that shows it.