<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Theme on Werk Space</title>
    <link>/tags/theme/</link>
    <description>Recent content in Theme on Werk Space</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 06 Aug 2026 17:39:13 +0000</lastBuildDate>
    <atom:link href="/tags/theme/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Theme Overrides</title>
      <link>/docs/document-system/theme-overrides/</link>
      <pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
      <guid>/docs/document-system/theme-overrides/</guid>
      <description>&lt;h2 id=&#34;the-principle&#34;&gt;The principle&lt;/h2&gt;&#xA;&lt;p&gt;The vendored theme in &lt;code&gt;_vendor/&lt;/code&gt; is never edited. Hugo resolves templates by looking in the site&amp;rsquo;s own &lt;code&gt;layouts/&lt;/code&gt; before the theme&amp;rsquo;s, so a file at the same relative path shadows its theme counterpart. Customization happens by shadowing; the vendored copy stays pristine, and &lt;code&gt;hugo mod vendor&lt;/code&gt; can regenerate it at any time without losing anything.&lt;/p&gt;&#xA;&lt;p&gt;The cost of a shadow is that it copies theme markup at a point in time. When the theme upgrades, the shadow silently keeps the old markup until it is reconciled by hand, which is why the &lt;a href=&#34;/docs/document-system/#install-docsy&#34;&gt;upgrade steps&lt;/a&gt; include a re-diff of every override.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
