<?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 Pocket Dev</title><link>/tags/hugo/</link><description>Recent content in Hugo on Pocket Dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Apr 2026 10:00:00 -0400</lastBuildDate><atom:link href="/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>From Template to Custom in Under 20 Minutes: Claude Code, Plan Mode, and the Impeccable Skill</title><link>/posts/rebuilding-pocket-dev-claude-code-plan-mode/</link><pubDate>Sun, 26 Apr 2026 10:00:00 -0400</pubDate><guid>/posts/rebuilding-pocket-dev-claude-code-plan-mode/</guid><description>&lt;p&gt;I rebuilt the entire frontend of this site in a single short session. New design system, new build pipeline, new color tokens, new typography, no theme dependency. The old Hugo template, the 36 Go modules, the 800-line custom SCSS — all gone. Replaced with Tailwind v4, ten hand-picked SVG icons, and a single &lt;code&gt;main.css&lt;/code&gt; I actually own.&lt;/p&gt;</description></item><item><title>From Next.js to Hugo: Why I Ditched the CMS for Markdown Bliss</title><link>/posts/nextjs-to-hugo-migration/</link><pubDate>Mon, 27 Jan 2025 10:00:00 -0400</pubDate><guid>/posts/nextjs-to-hugo-migration/</guid><description>&lt;h2 id="the-problem-when-your-cms-becomes-your-biggest-frustration"&gt;The Problem: When Your CMS Becomes Your Biggest Frustration&lt;/h2&gt;
&lt;p&gt;I started my blog with Next.js and Sanity CMS because I thought I&amp;rsquo;d be using the CMS extensively. The promise was simple: write content in a user-friendly interface, and let the system handle the rest. But reality hit hard.&lt;/p&gt;</description></item></channel></rss>