<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mental-Model on /var/log/janio</title><link>https://devops.sarmento.org/en/tags/mental-model/</link><description>Recent content in Mental-Model on /var/log/janio</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 11 Apr 2026 11:31:45 +0000</lastBuildDate><atom:link href="https://devops.sarmento.org/en/tags/mental-model/index.xml" rel="self" type="application/rss+xml"/><item><title>From WordPress to Hugo: Theming Is Not What You Think</title><link>https://devops.sarmento.org/en/posts/from-wordpress-to-hugo-theming-is-not-what-you-think/</link><pubDate>Sat, 04 Apr 2026 15:20:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/from-wordpress-to-hugo-theming-is-not-what-you-think/</guid><description>&lt;p&gt;Anyone who has worked with WordPress long enough develops a strong intuition for what a theme is and what it does. That intuition serves you well within the ecosystem: it guides decisions about file structure, where to put logic, and how to extend functionality. The trouble starts when you move to Hugo and try to apply the same mental model. The vocabulary overlaps — templates, layouts, partials — but what those words mean in practice is radically different.&lt;/p&gt;</description></item></channel></rss>