I was looking into how Caddy serves pre-compressed files (html/css/js), it’s pretty straightforward, I just need to generate the compressed files after Hugo builds the site. However, that is small fraction of the total payload since a lot of my posts have images. So I’m tackling that first. ...
I didn’t have a good process to add film photos to my Hugo static site with consistent tags to serve as metadata for camera, film, developer, format, etc. so I cobbled together a small Bash script to collect some input and create a folder as a Hugo `page bundle` but it was a very manual process still and the tag template soon became tedious to maintain. I discovered Gum and decided to play with it to see if it would improve my post creation experience and it has been pretty good during my brief testing....
This blog post can also be found at 1ba87346. This short URL is designed to make sharing online more compact without having to use an external URL shortening service. The permalink for this post is 62 characters (plus base URL, everything following discounts the base URL), while the short URL is 11 characters. Every post will predictably be 11 characters since I’m using CRC32 hash of the permalink to generate the short link....
I have been wanting to transition my photography site to Hugo as well but have not investigated how to utilize Hugo’s image processing capabilities. Yesterday I came across Wivik’s helpful shortcodes that display EXIF information and presents the photo with a frame and a caption. I’m experimenting with it now and might modify it and eventually migrate my photography content. I ran into nil pointer evaluating resource.Resource.Resize error when running the shortcode and tried out the built-in figure shortcode with the same path to verify that it wasn’t an actual path issue....