Working with Gatsby and GitHub Pages
Gatsby and GitHub pages can be a quick and effective way of developing a Website integrated with your existing source control, with minimal initial investment.
There are many different choices available for Website hosting, AWS and Google Cloud are cloud platforms I've used in the past for dynamic and static Web hosting but if you're already on GitHub and want to get a site running or have a dedicated page for your repository, GitHub Pages is a viable choice.
GitHub Pages doesn't need a build framework to work, you could run a static site with simple a index.html file and if you want a custom domain a CNAME file with your domain, for instance the CNAME for this site would simple have georgepaterson.com in the file.
GitHub provides some excellent documentation, create your repository if you need to and then set up two branches, main for your Gatsby development and gh-pages that will render the site. Using the gh-pages branch you will need to set it as the publishing source.
With the repository prepared you'll then want to initiate NPM, install Gatsby, and add the gh-page package to support deployment. You'll then need to add a deploy script to package.json.
"deploy": "gatsby build --prefix-paths && gh-pages -d public"
This will allow you to write code in the main branch and when you're ready you can deploy to gh-pages. Gatsby have full documentation at How Gatsby Works with GitHub Pages.
The CNAME that I mentioned earlier, put that file in your static folder and it will deploy to the root of the gh-pages branch.
This should give you a quick site to work with, there's more to explore with Gatsby and as the site gets more complex you could choose to move from GitHub pages and deploy to another host with minimal changes.