The design principle
Every technology choice in this stack follows one rule: it must be operable via text files and terminal commands. That’s not a developer fetish — it’s what makes the stack readable, writable, and deployable by AI agents as well as humans.
Layer 1 — Hugo (the builder)
This page started as a Markdown file called stack.md. Hugo compiled it into the HTML your browser loaded. The entire site builds in under 100ms.
There is no server processing your request. No PHP, no Node.js, no Python runtime. Hugo runs once at build time, produces static files, and its job is done.
Why this matters for agents: An AI agent creates a page by writing a .md file. It changes config by editing hugo.toml. It builds the site by running hugo. Every operation is a file write or a CLI command — the native interface for coding agents like Claude Code and Codex.
What Hugo replaces: WordPress, Wix, Squarespace — or hand-coded HTML without the pain of maintaining every page manually.
Layer 2 — GitHub (the system of record)
Every file powering this site lives in a Git repository. Push a commit to main and the site rebuilds and deploys automatically.
- Every change is tracked with a timestamp and author
- Any change can be rolled back in seconds
- Multiple people (or agents) can work simultaneously via branches
- There is no admin panel — the repo is the CMS
Why this matters for agents: Git is already the version control system every coding agent understands natively. git add, git commit, git push — an agent deploys to production the same way a developer does. Pull requests provide a natural human-review checkpoint.
What GitHub replaces: WordPress admin, FTP uploads, emailing files around, “which version is live?”
Layer 3 — Cloudflare Pages (the delivery network)
Cloudflare Pages is connected to the GitHub repo. On every push, it clones the repo, runs hugo, and distributes the output to over 300 edge locations worldwide.
The page you’re reading was served from the Cloudflare node closest to you. Automatic HTTPS. Unlimited bandwidth. No configuration.
Why this matters for agents: The agent doesn’t interact with Cloudflare at all for normal operations — pushing to GitHub is deploying. For advanced operations (domains, redirects, environment variables), Cloudflare’s API and CLI (wrangler) are fully programmable.
What Cloudflare Pages replaces: Web hosting, SSL certificates, CDN setup, deployment scripts.
What this costs: R0.00/month on the free tier.
Layer 4 — Google Workspace (the dynamic layer)
A static site can still collect data and manage bookings. The Forms Demo embeds a live Google Form — submissions land in a Google Sheet. The Calendar Demo embeds a Google Calendar for scheduling.
Why this matters for agents: The embedded forms and calendar work without any agent involvement. But the Google Workspace APIs open up further automation — an agent can read form submissions from Sheets, create calendar events, or trigger workflows via Apps Script. The dynamic layer is as programmable as the static one.
The full picture
You / Agent → write Markdown → git push → Cloudflare builds → CDN serves
↕
Google Workspace APIs
(forms, calendar, sheets)
Total monthly cost: zero. Total infrastructure to manage: zero. Time for an agent to deploy a content change: seconds.
For a deeper look at why agent-operability matters, see Agent-Ready Architecture.