/en/tags/zhi/Recent content in Zhi on Mi&Bee BlogHugo -- gohugo.ioen蓝宝石的傻话Wed, 13 May 2026 00:00:00 +0000/en/posts/aihelper/hugo-theme-zhi-v11-upgrade/Wed, 13 May 2026 00:00:00 +0000/en/posts/aihelper/hugo-theme-zhi-v11-upgrade/<h2 id="one-month-in">One Month In</h2> <p>It&rsquo;s been nearly a month since the previous article <a href="/en/posts/aihelper/hugo-theme-zhi-intro/">Switched My Blog Theme: From Hugo NexT to Self-Written Zhi</a>. During this month, the theme has been running stably without major issues. Replacing the NexT theme was the right decision — although there was some initial adjustment, the experience is now significantly better.</p> <p>After a month of use, the theme&rsquo;s stability has exceeded expectations. My initial concerns — whether pure Hugo Pipes without build tools could support complex requirements — were proven unfounded. Daily maintenance has become very simple; modifying a feature no longer requires digging through deeply nested SCSS files — one CSS file gets the job done.</p>/en/posts/aihelper/hugo-theme-zhi-intro/Thu, 16 Apr 2026 00:00:00 +0000/en/posts/aihelper/hugo-theme-zhi-intro/<h2 id="why-switch">Why Switch</h2> <p>This blog previously used <a href="https://github.com/hugo-next/hugo-theme-next">Hugo NexT</a>, forked for custom modifications. NexT itself is a feature-rich theme, but when it comes to &ldquo;customizing things yourself,&rdquo; the experience wasn&rsquo;t great.</p> <p>The issues boiled down to a few things:</p> <p><strong>SCSS nesting hell</strong>. 101 SCSS files, three levels of directory nesting. <code>_common/components/post</code>, <code>_common/components/third-party</code>, <code>_common/outline/sidebar</code>… To change a style, you first had to figure out which file it was in, where variables were defined, and which scheme was overriding it. Not that it couldn&rsquo;t be done, but each change meant half an hour of hunting.</p>