#hugo

When I built and posted some content on my site today using Hugo v0.53, I found that I had unintentionally broken some permanent links I was proud of. Thankfully, Hugo has a built-in feature - aliases - to address this issue.

The allure of nice syntax highlighting without leaving Markdown was one of the things that drew me to Hugo. In practice, I have found there are a number of challenges in implementation to get it to work as I expect. I was also reminded why I prefer not to spend my time fighting with CSS. ;)

When I started looking into some of the finer points of how my Hugo site looked, I had a few post formatting questions:

• Why does the sub-header look different in the post listing and page view?
• Why do the date posted and tags not appear in the page view but do in the post listing?

As mentioned in my Pip Permissions post, when I upgraded past Hugo v0.28 I noticed that Chroma was now preferred over Pygments. Eventually, I tried tackling the migration.

When exploring why another implementation of the Beautiful Hugo theme had summaries that looked much nicer than what I was seeing on my own site, I found out how Content Summaries are determined.