Static Site Generators and Github Pages

I told you a while ago about my experience building a static site with Hugo.  I was updating the page to show a few changes (notably to my book group website, but also to update the year in the footer).  I stumbled upon a small bug in Hugo’s date reporting, but the real issue that caused me to waste a ton of time was that in my aggravation, I wound up deleting the public folder to ensure a clean start.  But in a Github Pages based site, the public folder should really be a separate Github repo pointing to your target site!

So now I do a quick check in my deployment script to make sure I haven’t accidentally done this again.  Be sure you do something similar!

Note: If you are using Jekyll instead of Hugo, the same advice applies, but you’ll want to check _site instead of public.

Updating my book group website COMPLETE!

So I decided to go with Jekyll, a Ruby based static site generator. I created a new website for my book group, using a gem that makes it easy to autogenerate Amazon affiliate URLs with the Product Advertising API.

I open sourced the project in case anyone else wants to build a book club website, or any other type of website that uses Amazon affiliate links.

Updating my book group website

My beloved book group website is getting the dreaded “not mobile-friendly” warning from Google.  That’s because the site was built when “RWD” meant  “rear-wheel drive,” not “responsive web design!”  But challenge accepted – I will rework the site, and its 17 years of book choices – to be compatible with the modern web.  And you, dear reader, will be lucky enough to follow my adventure!