A while back I started consolidating all my release scripts and ran into an issue, that on the second look is quite obvious to solve, but I still wanted to share it with you. You might run into situations, where you have scripts that are only relevant for certain builds or environments.

The download attribute for anchor (<a>) tags is a nifty feature that often flies under the radar but can significantly enhance the user experience on a website. This attribute, when added to an <a> tag, instructs the browser to download the resource linked by the anchor tag instead of navigating to it.

Today, I reworked my theme changer script from vanilla JavaScript to an Alpine.js-based component. This change cut down the code lines by 50%. However, initially, it didn’t work. The console error messages indicated that my theme switcher function was unrecognized. Intrigued, I decided to investigate.

Visual Studio Code (VSCode) is a powerful code editor, but occasionally, it may provide different functionality than you need out of the box. Just have a look at the open feature requests on Github, and you’ll see that many users have encountered situations where VSCode doesn’t deliver as expected.

In my projects, I often encounter situations where I need to update the version number of the project before making a release. I follow the Semantic Versioning (Semver) standard for versioning. In this blog post, I’ll demonstrate how to retrieve the next Semver version number using a Bash script.

A while back (pre-COVID-19 era), I had the idea to create a GoHugo module that would allow me to create forms via configuration files. I also wanted to easily translate the form into different languages. I sketched out a solution but never got around to implementing it.