Helloblog

Configuration Guide

Sat, 07 Nov 2026 00:00:00 +0800

Configuration guide#

This page explains how to configure the theme: what ships with the theme, what must live in your own site, what each parameter does, and the mistakes that are easy to make. Work through it in order and you have a running blog.

Three layers of configuration#

File	Purpose	Do you edit it?
Theme `hugo.toml`	Built-in defaults, merged into your site by Hugo	No, override only what you need
Your site `hugo.toml`	Your site configuration	Yes, required
`exampleSite/hugo.toml`	Demo site config, including self-test mounts	Reference only

Warning

Do not copy exampleSite/hugo.toml wholesale. Its [module] section mounts ../layouts and ../assets from the parent directory, which only works when the repository root is the theme itself. Once installed under themes/helloblog those paths do not exist and the build fails.

Writing Components and Typography on a Static Blog

Fri, 23 Oct 2026 00:00:00 +0800

After writing for a while you notice that reading experience is shaped less by the words than by typography: whether code is highlighted, whether warnings get noticed, whether a long post can be skimmed. This sample article explains how the writing components in this theme are designed and used, and doubles as a template for new posts.

Why render at build time#

The most common misconception about static sites is that “static” means “no interaction”. Interaction stays; only its execution point moves.

About Me

Mon, 01 Jan 0001 00:00:00 +0000

About Me#

Profile#

I study at Northeast Electric Power University, majoring in Electrical Engineering and Automation.

I am interested in programming and have taught myself a fair amount of it.

Tech Stack#

Frontend: HTML5, CSS3, TypeScript (JavaScript), Vue3, SSG (Hexo, Hugo, VitePress)
Backend: Python, TypeScript
Hardware: Arduino (Cpp), STM32 (C)
Tools: Vite, Git, npm

Contact#

Email: 3253884026@qq.com
GitHub: https://github.com/Cnkrru

On AI-assisted Programming#

I do not dislike AI-assisted programming, but I am not a fan of going all in on AI
From my own experience, how much AI can help depends on your own knowledge and coding skills
Whether it is frontend, backend or hardware, AI does make things much easier, but the code it writes still feels like a mess
Enough said: AI is a good thing, but the result still depends on the person using it

Every article and sample snippet on this blog is written by hand
I am not saying this to show off. If you have questions about anything covered here, just ask. I may not remember the exact solution, but I do remember what I have written myself

It is best to review code written by AI yourself. After human review, some modules shrink by 50%: some become leaner with the same behavior, and some turn out to be dead code