Most of my blog posts are lessons learned. I’m trying to achieve something, and I document the process I used to do it. This one is one of the few where, in the end, I didn’t achieve what I wanted. In this post, I aim to explain what I learned from trying to migrate from Jekyll to Hugo, and why, in the end, I didn’t take the final step.   Context   I started this blog on WordPress. After several years, I decided to migrate to Jekyll. I have been happy with Jekyll so far. It̵

Frankel's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, Frankel offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

A Java geek

A developer attempted to migrate their blog from Jekyll to Hugo due to Ruby 4 compatibility concerns and Jekyll's declining maintenance. The migration covered 80% of functionality relatively smoothly—content mapping, shortcodes, and build pipeline updates. However, Hugo's external processing of Asciidoc files caused build times to balloon from 2 minutes to over 10 minutes for 800+ posts. The migration was ultimately abandoned, highlighting the importance of performance testing with real-world data volumes before committing to major tooling changes.

Migrating from Jekyll to Hugo... or not