Hugo Themes on Chrizzle23.net

Hugo Themes Part 4

Tue, 17 Sep 2024 18:47:19 -0400

Just like the last post, here is the TL;DR

Without git, you should use 7zip or tar to make backups of your working site on your workstation.
There is a very specific order you should use to create new content.
Some of this mystery behavior is me not understanding what I am doing when creating “new” posts that are actually old.
IDK why, but I get better results with the Hugo test server by using the –disableFastRender flag.

When we last saw our heroes…

I had decided to remove git from my workflow. It has definitely solved the disappearing template problem. Of course, if I need to regenerate my work directory for the site, I am out of luck. So I have taken to making compressed snapshots of the directory in case I have to delete the directory and start from my last checkpoint.

Hugo Themes Part 3

Wed, 11 Sep 2024 16:13:15 -0400

Just like the last post, here is the TL;DR

Using git to store your entire Hugo file structure is probably a bad idea.
Using git as cloud storage for markup files is probably also a bad idea, so I’m going to stop doing that too.
Dude, you gotta run the hugo command all by itself before you copy files up to the webserver.

When we last saw our heroes…

I was complaining about the theme files randomly disappearing. I think it comes down to git doing what it’s told to do, and me simply not understanding what I am telling it to do. That’s really the only thing that I know about computers: they do what they are told to do, not what they’re supposed to do, not what you want them to do. If a computer isn’t doing what you want, you should probably take a close look at what you are telling it to do.

Hugo Themes Part 1

Thu, 05 Sep 2024 09:49:45 -0400

If you are experiencing frustration with Hugo templates, here’s what I know so far

Unlike a recipe blog that tells you a long story about studying abroad in Europe before giving you the recipe, here is the TL;DR up front:

Running the Hugo test server doesn’t actually do anything. Yes, it runs a test server and serves pages on your workstation. But it doesn’t actually make the site. Once the test site looks good, terminate the server and run the Hugo command with no options. Then deploy the public folder.
Hugo doesn’t like when you add multiple MarkDown files to the site. Work on one at a time. Also, keep a backup copy of your content files outside of your main branch in git. I have broken things so badly that it’s easier to just start over from scratch with a new git repo.

If you are interested in the tale of this quest for this knowledge, please read on: