Rebuilding my Portfolio Site with Next.js

January 29, 2026 (1d ago)

0 views

After 2 years of mostly no progress, I've "completed" the next iteration of my portfolio site. This one is a rebuild using Next.js with TypeScript.

Before

I redo my portfolio from the ground up every so often to have fun and learn something new. Plus a refresh is always nice.

In order the iterations have been:

  1. A flat html file with no scripts that I made when I was 11 (sadly this has been lost)
  2. A Grav site I made in college (no longer hosted publicly)
  3. A Gatsby site (demo and source)
  4. This site here! (demo and source)

Dependency hell

I use GitHub's Dependabot to keep my dependencies up to date especially when their are security issues (which Next.js has had multiple critical CVEs during development of this site). Because this took 2 years, Dependabot opened a lot of pull requests. I'm in awe at how the javascript world is built on dependencies on dependencies on dependencies. It's dependencies all the way down.

The difficulty of upgrading to secure versions of dependencies with Gatsby was one of the original pushes for moving to a new framework. I fear that I've fallen into the same trap. This is one of the many reasons I almost abandoned this effort and went for Go or Rust for generating and building the site rather than a javascript framework. That's probably what I'll try for my next re-write.

Deployment

Deployments with Vercel are a breaze. It's very simple to connect to GitHub. It was easier than my old site which used Firebase.

Vercel has definitely been successfuly in building Vercel and Next.js together in such a way that they are the clear hosting option for personal projects like this.

What's next?

I still have more to do for implenting blog article views with a real database. I'm planning to try using Vercel's hosted database option first, but I will abstract the backend so it is easy to swap data stores.

I also want to include more content, so writing is in my future.