<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Css on robyn.digital</title>
    <link>/tags/css/</link>
    <description>Recent content in Css on robyn.digital</description>
    <generator>Hugo</generator>
    <language>en-CA</language>
    <managingEditor>hello [at] robyn.digital (robyn)</managingEditor>
    <webMaster>hello [at] robyn.digital (robyn)</webMaster>
    <lastBuildDate>Wed, 06 Aug 2025 08:43:00 -0600</lastBuildDate>
    <atom:link href="/tags/css/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating my Site Theme from `XMin`</title>
      <link>/2025/08/creating-my-site-theme-from-xmin/</link>
      <pubDate>Wed, 06 Aug 2025 08:43:00 -0600</pubDate><author>hello [at] robyn.digital (robyn)</author>
      <guid>/2025/08/creating-my-site-theme-from-xmin/</guid>
      <description>&lt;h1 id=&#34;why-my-own-theme&#34;&gt;Why my Own Theme?&lt;/h1&gt;&#xA;&lt;p&gt;When I settled on &lt;a href=&#34;https://gohugo.io/&#34;&gt;HUGO&lt;/a&gt; as the static generator for my first stab at a 2025-era small/indie web site, I was slowly but surely reminded of how &lt;em&gt;no&lt;/em&gt;, you &lt;em&gt;can&amp;rsquo;t&lt;/em&gt; in fact just build a HUGO site without a theme.&lt;/p&gt;&#xA;&lt;p&gt;Whether or not that is the way to go (I would argue that it is not; see also Bruce Wray&amp;rsquo;s excellent article on &lt;a href=&#34;https://www.brycewray.com/posts/2022/07/really-getting-started-hugo/&#34;&gt;Really getting started with Hugo&lt;/a&gt;), that&amp;rsquo;s where we are. I would prefer if a Hugo site worked without a theme - if it spit out barebones HTML, basically - and we could just slap on different themes to see what the site looks like with those applied. And then pick the one we like best.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
