
Starting a Site with Hugo: Own the Place You Write
Part one of building a site you actually own. Why static, why this stack, and getting Hugo running on your machine in ten minutes.
security · azure · data · the practical side
This series builds the site you’re reading, from an empty folder on a laptop to a site on its own domain that deploys every time I push. Three pieces, each doing one thing: Hugo turns a folder of Markdown into a website, GitHub holds the source and its history, and Cloudflare Pages builds it and serves it. At this scale it costs nothing to run, and there’s no database or admin login sitting on the internet waiting to be brute-forced. I’d pick the same stack again.
It’s written in the order I’d do it if I were starting over, with the mistakes left in. Most parts include the setting or habit that cost me an afternoon, so it doesn’t cost you one. By the end you have a site that looks like yours, holds up to a security scanner and releases future-dated posts on its own while you get on with something else.
Parts appear below as they go live, newest at the top. If you’re starting from nothing, begin at the bottom and work up.

Part one of building a site you actually own. Why static, why this stack, and getting Hugo running on your machine in ten minutes.