Hugo

The answer first: structure is a promise to the reader Good structure reduces the amount of reconstruction a reader must do. A useful technical section makes its conclusion, evidence, limits, and next action easy to find. That also gives search and answer systems cleaner material to process, but no heading pattern, paragraph length, summary block, or schema type guarantees an AI citation. That distinction matters. It is tempting to turn GEO into a writing ritual: put the answer first, keep the paragraph within a magic range, add FAQ schema, and wait for citations. Google explicitly says its AI search features use the same foundational SEO requirements as ordinary Search and require no special AI markup or content format. The safer order is: ...

136: Hugo Advanced Coming to the advanced part, you need to learn some advanced Hugo techniques in depth. Module Hugo modules are the core building blocks of Hugo. A module can be your main project or a smaller module that provides one or more of the 7* component types defined in Hugo: static, content, layouts, data, assets, i18n and archetypes. You can combine modules in any combination you like, and you can even mount directories from non-Hugo projects to form a large virtual union file system. ...

📌 Update (July 2026): This post, written in 2023, covers how the third generation of this blog was built from scratch on Hugo — the setup tutorial still holds up. Three years later I reassembled the entire blog again, and this time it wasn’t the theme that changed but the whole production line: an AI writing pipeline, a two-stage cover factory, an AI duty officer living in GitHub Actions, and GEO infrastructure. The full retrospective is in this new article (in Chinese) — read the two together: this one is the foundation, that one is how the house grew into a system. ...