https://samarthya.me/tags/css/Recent content in Css on SamarthyaHugo -- gohugo.ioen© Samarthya 2018-2026. All rights reserved.Sun, 25 Oct 2026 12:20:00 -0400https://samarthya.me/posts/rebuilding-3-a-new-home-on-hugo/Sun, 25 Oct 2026 12:20:00 -0400https://samarthya.me/posts/rebuilding-3-a-new-home-on-hugo/<div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"> The content was safe. Now it needed a home that&rsquo;s easy to keep alive: something I can write in, push, and forget about. </div> <h2 class="relative group">The stack <div id="the-stack" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-stack" aria-label="Anchor">#</a> </span> </h2> <ul> <li><strong><a href="https://gohugo.io/" target="_blank" rel="noreferrer">Hugo</a></strong>, pinned to one exact version with <a href="https://mise.jdx.dev/" target="_blank" rel="noreferrer">mise</a>, so a future release can&rsquo;t silently break the build.</li> <li><strong><a href="https://blowfish.page/" target="_blank" rel="noreferrer">Blowfish</a></strong> as the theme, added as a git submodule and <strong>never edited</strong>. Every change lives in the site&rsquo;s own <code>layouts/</code> and <code>assets/css/</code>, so theme updates stay a one-line operation.</li> <li><strong>GitHub Actions → GitHub Pages.</strong> Push to <code>main</code>, and about a minute later the site is rebuilt and live.</li> </ul> <h2 class="relative group">A portal, not just a blog <div id="a-portal-not-just-a-blog" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#a-portal-not-just-a-blog" aria-label="Anchor">#</a> </span> </h2> <p>The first version looked like what it was: an unmodified theme with 137 blank tiles. Imported posts have no &ldquo;feature image&rdquo;, so every card was empty. Three changes turned it into a place:</p>https://samarthya.me/posts/css-and-html-to-dom/Fri, 08 Mar 2019 12:00:00 +0000https://samarthya.me/posts/css-and-html-to-dom/<figure><img class="my-0 rounded-md" loading="lazy" decoding="async" fetchpriority="auto" alt="Fluttery shy bleeding" width="2029" height="2817" src="https://samarthya.me/posts/css-and-html-to-dom/img_20190815_143219_hu_41c3d363f87f31e9.jpg" srcset="https://samarthya.me/posts/css-and-html-to-dom/img_20190815_143219_hu_41c3d363f87f31e9.jpg 800w, https://samarthya.me/posts/css-and-html-to-dom/img_20190815_143219_hu_e75bbbfb933a9163.jpg 1280w" sizes="(min-width: 768px) 50vw, 65vw" data-zoom-src="https://samarthya.me/posts/css-and-html-to-dom/img_20190815_143219.jpg"></figure> <p>Happiness is not always straight lines.</p> <p>Having worked on different technologies I never took HTML very seriously till a couple of years back. I started programming rather seriously programming when I was about 20 years old for a small startup then – FQSL. In those days, my primary responsibility was more around creating a middle – tier application which had a <em>management interface</em> and had the ability to spawn multiple threads to handle the incoming traffic and the main concern was to handle the load effectively and perform under pressure. This was all to be done in a native platform “Windows” and mostly in VC++ and MFC. Glad we are in <em>serverless</em> days now. 🙂</p>