After a few hours of work, I was able to get the bare minimum of this site rewritten for hugo. I’ll work on finalizing the /home and /about pages slowly but surely; for now though, I am more than satisfied with just having the blog up and running.

While I was working on the migration, I read up on some things I would like to incorporate some day:

• Hugo has support for Emacs users to write the pages in Org mode. That’s exciting to even just try out for an article or two; especially considering that at some point I was trying to write a Python script to change an org file to markdown for Jekyll.

• A goal I’ve had in the start is to write the site from scractch, and that goal has been reinvigorated with this migration.

Some hiccups I encountered along the way:

• I glossed over the one line in the Hugo Documentation that was like “User pages have to have the files for the site on the master branch”. I read that after I learned about setting up multiple working trees and put all of my files in a gh-pages branch.

  • No worries, I just swapped the two branches essentially. So master holds the Hugo generated website files, and my dev branch holds the files that generate the files that need to sit in master.

• There was a path issue in linking the CSS files. In the config you can set the baseURL of the site, and in the theme I am using, the author references that variable directly, like so: {Site.baseURL}css/nameOfStylesheet.css. You get the point. Naturally, you would think to set the baseURL= https://luandy64.github.io/. That way when it is referenced later, I get a properly formed url to the CSS file.

  • Right now, the ‘baseURL’ lacks a trailing /, and I edited the theme to include the / between {Site.baseURL} and the rest of the path to the stylesheet. I plan to look into what is considered the better practice, but for now, it works as is.