Write the HTML.
Drop the file.

You can host a page for nothing, and it takes about a minute

Cloudflare Drop does one thing: it takes a folder of static files and puts them on Cloudflare's global network. Its own description is "deploy static sites to Cloudflare's global network instantly, with no account required to start." That last clause is the interesting bit — you can ship something before you've decided whether you care about it.

There are two ways in. Drag a folder or a .zip onto the page, or run one command:

copynpm exec --yes wrangler@latest -- deploy ./dist \
  --name my-static-site \
  --temporary \
  --compatibility-date 2026-07-30

Either way you get a live workers.dev URL. The folder has to contain an index.html — which, if you have been writing single-file HTML, you already do.

What "free" actually means

Drop deploys to workers.dev, so it inherits the Workers free plan. The published limits:

Custom domains

This part holds up. A custom domain can be attached from the dashboard, from wrangler with custom_domain = true, or over the API — and the domain has to be on an active Cloudflare zone that you own. That is precisely why it feels instant when the domain is already on the same account: Cloudflare creates the DNS record and issues an Advanced Certificate for you, so there is nothing to copy-paste between dashboards.

Markdown is where documents go to not be read

The argument in The unreasonable effectiveness of HTML is narrower than "HTML is good". It's that for anything a human is meant to read, HTML should be the default output and Markdown the exception. The honesty that makes it land:

I tend to not actually read more than a 100-line Markdown file.

Using Claude Code — the unreasonable effectiveness of HTML

Which is true of most people, and quietly damning if your work habitually arrives as a 400-line .md. The post's case breaks into four claims.

There's a fifth point that's easy to skim past and is arguably the most useful: the same document can synthesise sources that don't otherwise meet — the filesystem, connected tools like Slack or Linear, git history, browser history — into one report. That isn't a formatting upgrade. It's a different kind of artifact.

Where it earns its keep

• Specs and exploration — several design directions side by side rather than described in sequence.
• Code review — annotated diffs with the reasoning next to the change.
• Design prototypes — parameters the reader can actually move.
• Reports — several data sources joined into one page.
• Custom editing interfaces — where the reader's edits export back out as instructions.

The default aesthetic is the problem

The companion piece, prompting for frontend aesthetics, starts from an uncomfortable premise: left alone, a model converges on whatever is most "on distribution". In frontend work that produces a recognisable house style people have started calling AI slop — and recognising it is most of the fix.

The remedy is three strategies: direct each design dimension deliberately, reference a specific existing aesthetic rather than asking for "nice", and name the defaults you don't want out loud.

What this page is doing, so you can judge whether it worked

A page arguing for handmade HTML should show its own workings. Here is every choice it committed to.

Put this page on the internet

Drop this file into a folder as index.html and run:

copy# from the folder containing index.html
npm exec --yes wrangler@latest -- deploy . \
  --name html-field-notes \
  --temporary \
  --compatibility-date 2026-07-30

# then claim it within 60 minutes, or it's gone

Everything this page was built from

Two skills shaped it, two blog posts are summarised in it, and three Cloudflare pages supplied every number in tab 01. All of it is public.

The skills that built this page

Neighbours in the same repos, not used here

The two posts summarised in tabs 02 and 03

Where every number in tab 01 came from