<?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 Christian Spoo</title><link>https://www.christian-spoo.de/tags/hugo/</link><description>Recent content in Hugo on Christian Spoo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 06 Feb 2026 11:33:18 +0100</lastBuildDate><atom:link href="https://www.christian-spoo.de/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I chose Hugo over WordPress for this blog</title><link>https://www.christian-spoo.de/posts/2026/01/why-i-chose-hugo-over-wordpress-for-this-blog/</link><pubDate>Fri, 23 Jan 2026 14:30:00 +0100</pubDate><guid>https://www.christian-spoo.de/posts/2026/01/why-i-chose-hugo-over-wordpress-for-this-blog/</guid><description>&lt;p&gt;When I decided to start this blog, one of the first questions I had to answer was: which platform should I use?
For many people, WordPress is the obvious choice—it powers over 40% of all websites on the internet, after all.
Unlike many others, however, I&amp;rsquo;ve never really liked WordPress.
Part of this stems from its terribly grown, unstructured codebase that has accumulated technical debt over nearly two decades.
More recently, political turmoil within the WordPress project around the behavior of Matt Mullenweg and the company Automattic has further soured my view of the platform.
After working with Hugo for a while now, I&amp;rsquo;ve found it suits my needs much better—particularly for static content like a personal blog.&lt;/p&gt;</description></item></channel></rss>