The companion episode — Aillex shows you the exact site you’re reading right now, and how it was built.
The website you are reading was designed by an AI, written by an AI, and is maintained by one every day. But none of it built itself: every page was asked for, defined, and signed off by a human. That’s the model this guide teaches — you direct, the AI builds, you own the result — and you can run it yourself this weekend for about the price of one coffee a year.
Rent, or own
Most “build a website with AI” tutorials point you at a builder — Wix, Squarespace, a Framer template. Those work, but you’re renting: stop paying and the site goes dark, and your words live on someone else’s servers under someone else’s rules.
There’s a simpler path: a static site. Every page is built ahead of time into plain, finished HTML — nothing to hack, nothing to crash, and it loads instantly. You can host it free, forever. Static sites used to be tedious to build by hand; that’s exactly the tedium AI erased. So we own, we don’t rent.
The three free pieces
The site is three free tools wired together, and once they’re wired you forget they exist:
- A static site generator — Hugo. You write in plain text (headings, bold, links); Hugo turns a folder of it into a complete, styled website in about a tenth of a second.
- GitHub — the safe home for your files, with a full history of every change.
- Cloudflare — the host that serves your site to the whole world, for free.
The magic is that they’re connected. The moment a change is saved, the live site rebuilds itself. One command — git push — and about 45 seconds later it’s public. No uploading, no deploy button.
Which AI, actually? (name it)
“Just use AI” is a useless answer, so here’s the specific one.
In our case, the AI that laid this foundation was Claude. Given clear, specific instructions, it wrote the structure, the styling, and the first pages — and with instructions that clear, you can get a base site done on Claude’s free plan. No subscription required to start.
But you don’t need any company’s cloud. Local, open-source models are fully capable of this now. With a decent graphics card:
- Models: Qwen3-Coder, Z.ai’s GLM, or DeepSeek — all open-weight and permissively licensed. On a home GPU, a mid-size model like Qwen 3.6 or Devstral will fit and do real work.
- Tools to drive them: Cline (in VS Code), Aider (terminal, git-native), or OpenHands — these let the model actually read your files, edit them, and run commands, instead of just chatting.
The trade-off is honest: a less capable model means you’ll be more hands-on, guiding it to the finish line yourself. But that’s the fun of DIY — and it’s how you actually learn. (New to local models? Start with AI models, explained and run a local brain.)
The words: AI drafts, a human decides
This is where AI does the heavy lifting — and where most people go dangerously wrong.
Every guide here started as a draft written from a real knowledge base — actual build notes, mistakes, and fixes. That’s the trick nobody tells you: AI writing is only as good as what you feed it. Point it at hard-won experience and it writes like an expert; point it at nothing and it writes an empty brochure.
So the non-negotiable rule: the AI drafts, a human decides. Every page passes under a person’s eyes before it goes live — catching what’s subtly wrong, killing the filler. You are never publishing raw AI. You’re publishing work a human defined and stood behind. That difference is the entire ballgame.
A designer, without a designer
You don’t need to be a designer — you just don’t build the design from scratch.
- A theme does the design for you. Ours is PaperMod — clean, fast, free — and there are hundreds. Pick one and every page is instantly styled and readable on a phone.
- The images are AI-generated. Every cover on this site, and the favicon in your browser tab, was made on the same machine that renders our videos. If you’ve followed the Engine Room series, you already know how. Your website becomes one more place to use the AI you’re already building.
The part everyone skips: getting found
A beautiful site nobody can find is a diary. The unglamorous grunt work that makes search engines understand your pages is exactly what AI is better at than a human:
- Structured data — a machine-readable summary of each page (on video pages, including chapter markers so Google can drop a searcher into the exact second).
- Discover eligibility — the tags that make pages eligible for Google’s Discover feed.
- The sitemap every search engine reads, plus telling Search Console the moment a new page exists — minutes, not weeks.
Define the standard once; it’s applied to every page you’ll ever publish, perfectly, forever.
The site that maintains itself
This site grows, mostly on its own. One of our AI agents — the Librarian — has one job: this website. Every time an episode ships, it writes the companion guide, generates the cover, embeds the video, links it to related pages, and pushes it live.
The agents don’t hold meetings; they coordinate through a shared log — each writes down what it did, the next reads it first. Two of them edited this site hours apart one day and never collided. The site grows itself — but a human still holds the final gate. It grows itself; it does not publish itself. On purpose.
What it actually costs
| Item | Cost |
|---|---|
| Hosting (Cloudflare) | $0 |
| Software (Hugo, theme) | $0 |
| The AI models | $0 (local) or a free plan |
| Domain name (the .com) | ~$10 / year |
| Total | ~$10 / year |
Less than a dollar a month for a real, fast, searchable website. And once it exists it can quietly do a job — for us it’s the hub of everything, with affiliate links disclosed at the top of every page, because honest is the only version worth doing. It’s also just yours: a domain that will still be here in ten years, because nobody can switch it off but you.
Your first one, this weekend
Own it, don’t rent it. You direct; the AI builds. If you’re starting from zero, the fastest on-ramp is the Start Here path — then come back here and stand up your own site.
Build it this weekend, then tell us about it over at r/aillex or on YouTube → @AskAillex.
