Ditching SSGs for a hand-crafted Website
The author has transitioned from using Hugo as a static site generator to creating a more personalized hand-crafted website. This change has allowed for greater control over the HTML and CSS, enhancing the author's learning experience. The process involves using server-side includes to manage repetitive elements efficiently.
- ▪The author used Hugo for a long time but found it limiting in terms of personal creativity.
- ▪They simplified the HTML and CSS code by using various online validation tools.
- ▪Server-side includes were implemented to avoid repetitive coding for common elements like headers.
Opening excerpt (first ~120 words) tap to expand
Ditching SSGs for a hand-crafted Website Posted on 2026-05-29 Introduction Ok, this is not really a 100% hand-crafted website but new articles and some other parts are now. Here’s the story: I used Hugo as a static site generator (SSG) for a long time and started to get bored. With Hugo, I was also much closer to the final product than, say, with WordPress, but it didn’t feel like I was personally creating the website. So I simply took the HTML code generated by Hugo as a basis, copied it to a new directory, and moved it to a new Git repository. Then I started simplifying the HTML code and the CSS file and adapting them to my needs. For this, I used the following online tools: W3C Markup Validation Service - The classic that pretty much everyone knows.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Rz01.