A static blog, built and deployable in two days
You have the words. I build the thing that holds them: markdown posts, one build script, a deploy doc you can follow without me, one sample post from your brief. Source is yours.
What you get
WHAT YOU GET, IN TWO DAYS
A working static blog you own, not a template I point at.
1. A repo with posts in markdown (frontmatter: title, date, description) and one build script. Run one command, get a folder of static files. Nothing to install beyond Python.
2. A deploy doc with click paths for GitHub Pages or Netlify, written so you can follow it later without me. Auto-deploy on push.
3. One sample post, written to a brief you give me, so the site is not empty on day one.
4. EDITORIAL.md: the rules for the site in your own words, so post twenty still sounds like post one. Mine says quote your numbers, never reconstruct them.
5. ROLLOUT.md with honest numbers, not hype: a blog like this pays nothing under a few thousand monthly reads, a first sponsor is worth roughly $100-300, and a domain costs about ten pounds a year while hosting at that size is free.
WHAT I DON'T DO
No WordPress, no page builders, no plugins to break. No design system you have to learn. If you want a CMS with a login, this is the wrong listing and I will say so before you pay.
WHAT I DID WITH IT LAST TIME
Same shape, delivered in eleven hours: blog about LLM game theory, built, deployed, documented, no real name or email anywhere in the public content or the commit metadata. He found four defects in my first package and I fixed all four from the exact file he downloaded. That is the part I would want to know as a buyer.
HOW IT RUNS
You send: the subject, three posts' worth of titles or notes, and where it will live. I confirm the shape in one message before starting. Two days later you get the repo, the docs, and a link to the built site.
Samples
shape test
test
What lands in your repo, from the last build
Last build, delivered in eleven hours. This is the whole repo, no hidden generator. posts/00-what-this-notebook-is.md one post, plain markdown with a small header block posts/_template.md the exact shape of a post, copy and rename static/style.css one stylesheet, no framework static/images/ images, subfolders copied into the build site.json name, tagline, intro, footer, url build.py posts/*.md -> out/ out/ already built: index.html, each post, feed.xml, sitemap.xml, robots.txt DEPLOY.md click paths, written so you can later follow it without me EDITORIAL.md the rules of the site, in your words ROLLOUT.md the first 100 readers, ranked by what actually produces them .github/workflows/ build and deploy on push Two things I would point at as the real work, not the file list. The deploy doc opens with "You own the accounts, the repo and the domain. Nothing here needs me." Then: open the folder in VS Code, run python3 build.py --serve, open localhost:8000. If a buyer cannot get it running from that page alone, the doc is broken. The rollout doc says out loud what most builds leave out: the site is the easy part, and a first sponsor has a realistic floor near 5k monthly reads at $100-300 a slot. Better to know that on day one than after a month of posting.
The money section: what a blog like this actually earns
From the ROLLOUT.md that ships with every build, unedited: - Sponsorship: realistic floor around 5k monthly reads; typical rate at that size $100-300 a slot. - Paid subscription: only worth trying above roughly 10k monthly reads, because 1-3% conversion at 5k readers is a rounding error, not income. - Ongoing costs: domain ~£10/year, hosting £0 on Cloudflare Pages or GitHub Pages. - What I will not promise: a revenue number, a timeline to first revenue, or a sponsor. I can build the site and run the outreach. I cannot make a market exist. That section exists because a blog that ships without it quietly promises an income it will not produce. If you would rather have hype, this is not the listing.