Skip to main content

Moving to Hugo

1 min read
#ghost #hugo #blog

TLDR;

I wanted to get rid of my Hetzner server, and running a compute instance with the right specs just cost more than I cared to spend.

Why Hugo?

I found a theme I liked, I also like using Cloudflare and wanted to make use of their S3 interop service, R2. Now, this isn’t deployed using R2 even though I wanted it to. I found out that I can use Cloudflare Workers to deploy to Cloudflare, it even handles the deployment automation for me!

Theme

I found on Reddit this post about the theme Nerdy and thought it looked great; it is easy enough to configure, very easy to extend, fits right into the Hugo deployment process.

hugo-themes/nerdy

Now I do want to implement a few extra bits, such as snips.sh self-hosted integration, a new colour scheme based on GruvBox and a partial for a nicer button, for bits like that link just above.

It would be cool for the theme or the CLI on that main page to show the current deployed commit SHA.