<?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 Leyline — Demo</title><link>https://jordinebot.github.io/hugo-leyline/tags/hugo/</link><description>Recent content in Hugo on Leyline — Demo</description><generator>Hugo 0.161.1</generator><language>en</language><atom:link href="https://jordinebot.github.io/hugo-leyline/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugo Modules: composable themes</title><link>https://jordinebot.github.io/hugo-leyline/posts/hugo-modules-composable-themes/</link><pubDate>Tue, 28 Apr 2026 18:00:00 +0200</pubDate><guid>https://jordinebot.github.io/hugo-leyline/posts/hugo-modules-composable-themes/</guid><description>&lt;p&gt;Themes used to be monoliths. You picked one, you got everything it shipped, and any deviation meant forking. Hugo Modules change that: a theme is a Go module, and you can compose modules together the same way you compose Go packages.&lt;/p&gt;
&lt;p&gt;Leyline leans on that. The MTG shortcodes — &lt;code&gt;card&lt;/code&gt;, &lt;code&gt;cardname&lt;/code&gt;, &lt;code&gt;combo&lt;/code&gt;, &lt;code&gt;mana&lt;/code&gt;, &lt;code&gt;match&lt;/code&gt;, &lt;code&gt;draft&lt;/code&gt; — don&amp;rsquo;t live inside the theme. They sit in a separate Hugo Module, &lt;a href="https://github.com/jordinebot/hugo-mtg-shortcodes"&gt;&lt;code&gt;hugo-mtg-shortcodes&lt;/code&gt;&lt;/a&gt;. Sites that want them add the import; sites that don&amp;rsquo;t, don&amp;rsquo;t. The module ships its own SCSS, partials, JS, and the mana icon font — Hugo merges it all into the consuming site at build time.&lt;/p&gt;</description></item></channel></rss>