https://www.rafaelvzago.com/en/tags/jekyll/Recent content in Jekyll on Rafael ZagoHugoen-US© Rafael ZagoSun, 26 Jul 2026 11:00:02 -0300https://www.rafaelvzago.com/en/posts/migrei-o-blog-de-jekyll-para-hugo-com-desenvolvimento-agentic/Sun, 26 Jul 2026 00:00:00 -0300https://www.rafaelvzago.com/en/posts/migrei-o-blog-de-jekyll-para-hugo-com-desenvolvimento-agentic/<p><a href="https://www.rafaelvzago.com/assets/img/headers/migrei-o-blog-de-jekyll-para-hugo-com-desenvolvimento-agentic.png" class="img-lightbox" data-lightbox> <img src="https://www.rafaelvzago.com/assets/img/headers/migrei-o-blog-de-jekyll-para-hugo-com-desenvolvimento-agentic.png" alt="Illustration of migrating from Jekyll to Hugo" loading="lazy" decoding="async"> </a></p> <p>On 24 July 2026 this blog stopped being Jekyll + Chirpy and became Hugo + Archie. I could have treated that as &ldquo;swap the theme and hope.&rdquo; I did not. It was a cutover with a PRD, vertical tickets, a mandatory local preview, and an immutable rollback tag.</p> <p>I already wrote about <a href="https://www.rafaelvzago.com/en/posts/como-eu-uso-ia-no-desenvolvimento/">how I organize skills and agents</a> and about a <a href="https://www.rafaelvzago.com/en/posts/claude-code-automatizando-workflow-prd-pr/">generic PRD-to-PR workflow</a>. This post is the case study: the same playbook on a real migration in this repository. Process as the spine, reproducible steps in the middle. Full multilingual is the next chapter. Here the subject is the Jekyll → Hugo toolchain cutover.</p>