<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Html on c2thulhu.sh</title><link>https://c2thulhu.sh/tags/html/</link><description>Recent content in Html on c2thulhu.sh</description><generator>Hugo -- 0.146.0</generator><language>en-us</language><lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://c2thulhu.sh/tags/html/index.xml" rel="self" type="application/rss+xml"/><item><title>Adding My Own Theme To This Blog!</title><link>https://c2thulhu.sh/posts/adding-some-theming-and-aesthetics-to-this-blog-with-a-custom-theme/</link><pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate><guid>https://c2thulhu.sh/posts/adding-some-theming-and-aesthetics-to-this-blog-with-a-custom-theme/</guid><description>&lt;p>Most Hugo theming guides will tell you to fork the theme and modify it
directly. I am here to tell you that is not necessary and the solution I propose
and utilize here in this blog is much simpler and more maintainable. First I
will talk about why forking a theme and using that is not what I see as the
ideal solution for this use-case:&lt;/p>
&lt;ol>
&lt;li>It&amp;rsquo;s boring!&lt;/li>
&lt;li>Making your own theme is fun and will give your blog more personality.&lt;/li>
&lt;li>Having to cater your blog posts to upstream changes in the theme is a
shortcut to becoming frustrated with maintaining your blog; it adds
unnecessary friction to your life and workflow for blogging.&lt;/li>
&lt;/ol>
&lt;p>So, for a site running PaperMod as a git submodule, that approach is a
maintenance problem waiting to happen and most importantly, isn&amp;rsquo;t fun. The
cleaner solution is to use Hugo&amp;rsquo;s override system to inject custom styles
without touching the theme directory at all. This gives us full control over the
theme and even allows for future post-specific customization.&lt;/p></description></item></channel></rss>