<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo on Kaisekukun</title><link>https://netguide.jp/en/tags/hugo/</link><description>Recent content in Hugo on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Kaisekukun</copyright><lastBuildDate>Fri, 12 Jun 2026 12:00:00 +0900</lastBuildDate><atom:link href="https://netguide.jp/en/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Goodbye WordPress: Why and How We Migrated to Hugo Static Site Generator</title><link>https://netguide.jp/en/web/wordpress-to-hugo-migration-story/</link><pubDate>Fri, 12 Jun 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/en/web/wordpress-to-hugo-migration-story/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/wordpress-to-hugo-migration-story-en.png" alt="Featured image of post Goodbye WordPress: Why and How We Migrated to Hugo Static Site Generator" /&gt;&lt;p&gt;We have officially completed the transition of &lt;strong&gt;netguide.jp&lt;/strong&gt; from WordPress to &lt;strong&gt;Hugo&lt;/strong&gt;, a modern static site generator (SSG).&lt;/p&gt;
&lt;p&gt;Operating a dynamic CMS like WordPress had become increasingly bottlenecked by page load delays, security updates, and hosting costs. Migrating to a static workflow resolved all of these issues. In this case study, we share our motivation, migration strategy, and the post-migration performance gains.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="1-three-reasons-we-left-wordpress"&gt;1. Three Reasons We Left WordPress
&lt;/h3&gt;&lt;p&gt;While WordPress remains a highly versatile CMS, its dynamic, database-driven architecture presented critical challenges as our content grew:&lt;/p&gt;</description></item></channel></rss>