Unusionable is a podcast I do with Hannah. The name is a made-up word, which is sort of the point. We needed a website for it, and I didn't want to use a podcast hosting platform's built-in site because those are all templated and covered in someone else's branding. So I built a static page on GitHub Pages with a custom domain.
.svg){kind=link}
The site
The repository contains two files: an index.html and a CNAME file. The CNAME points the custom domain unusionable.com to the GitHub Pages deployment. When someone visits the domain, GitHub's servers route the request to the repository's published content.
This is about as minimal as a website gets. There's no CSS framework, no JavaScript, no build process. The HTML handles its own styling inline. The reason for keeping it this simple is that the site's only job is to exist at a URL that we can put in podcast directories and share with people. It doesn't need to do anything else.
Custom domains on GitHub Pages
Custom domain configuration for GitHub Pages is one of those things that's easy once you've done it but confusing the first time. The CNAME file in the repo tells GitHub which domain to expect. On the DNS side, you add either an A record pointing to GitHub's IP addresses or a CNAME record pointing to username.github.io. GitHub handles HTTPS automatically through Let's Encrypt. The whole setup costs nothing beyond the domain registration.
I've used this pattern for a few projects now. For something that's just a landing page or a redirect target, a single HTML file in a GitHub repo with a CNAME is hard to beat. No hosting fees, no server maintenance, no deployment pipeline. You push to the repo and the site updates.