I’ve been making some efforts to streamline the publishing process for this site. I’ve read about tools like Netlify and Lektor, but I wanted to keep things as close to a basic Hugo site as possible. To that end, I wanted to use git hooks to run hugo whenever I ran git commit. That way to publish a new post I simply had to write it in markdown, save, commit and push.
Using HTTPS for your site has lots of benefits. Chief among them being security. Using HTTPS ensures that no one can intercept and read traffic between you and the site you’re visiting. However, it’s traditionally been somewhat difficult and expensive to provide HTTPS for your sites visitors. Now though, with Let’s Encrypt an SSL certificate is free! And if you’re using GitHub pages with a custom domain for hosting using it couldn’t be easier.
I’ve added my Keybase Proof as a text file at the root of this site. I used to have my site proven via DNS but for whatever reason CloudFlare removed my TXT record breaking the proof. I decided that having the .txt file proof was more resilient because even if I change hosting (Currently on Github Pages) my proof will remain intact. If you aren’t on Keybase check it out. I like to think of it as “crypto-as-a-service”.
Last night I got the wild hare to migrate my personal site from Pelican to Hugo. I’ve been meaning to do it for a while now, so to give myself the push I needed to get it done I deleted my old personal site from Github. Differences Front Matter Honestly the biggest different for content is “front matter”. Both Hugo and Pelican, as static site generators, use front matter to describe pieces of content.
I recently started using Pelican static site generator for this blog. I was drawn to it for a few reasons: It uses Jinja2 for templates, which I love. It written in python It reminds me a lot of Flask (this might be because of using Jinja2…) I’ve done a few interesting things with this site though. I’m hosting the repo that contains the source content, configuration, etc. on Gitlab.