Migrating to Hugo

published on | edited on

This is not the first kind blog post you will see in the web. I was huge fan of Jekyll, but after migrating from GitHub Pages, I found no advantages other than it’s being database-less writing platform.

I still recommend people who have less experience in writing online in Git because it requires less learning curves. I also saw people recommending me to use JavaScript frameworks such as Webpack to create static pages when hearing the word Static Site Generator. SSG is not the same as a bundler because this website consists of redirect pages, sitemaps, generated robots.txt or RSS feeds. There are efforts where generating each of these is possible but I will state again: use the tool that is build for the wanted purpose.

Another reason I picked Hugo because Debian have a package in Buster distribution. I really don’t care about which version they are distributing. I can easily switch the Debian image to Bullseye or Sid to generate the content. This is done because I take advantage of Vagrant on KVM.

So far, I am happy with Hugo 0.54.0. I created my own default theme. I did because I can control the theme. I could go on GitHub and submodule a theme.

I had previous effort to migrate to Hugo but the content was not ready. Actually, the content is still not ready; therefore, I will just push a few posts at a time.

This time of frame, I am using GitHub Actions to publish content in Netlify. Since I am hosting a few WordPress pages, I have reseller account that I can create no-database package for this website. Yes, I will use FTP to synchronize content. Only the reason I keep on GitHub because of Git LFS support.

I don’t maybe already mentioned I migrate posts one by one. I saw few mistakes in my writings and updating the lastmod instead of creating brand new content which you can see in the post page.