Why every authoring tool becomes a walled garden.
Three primitives that make HTML a complete authoring system.
From markdown to live URL in five moves, zero build config.
What 30 years of HTML's durability actually looks like.
Authoring, publishing, and generating HTML in 2026.
Three things to ship before the next standup.
We keep building new layers on top of the web while the web's own native language — the most durable, portable, view-source-able format ever shipped — sits underused directly beneath us.
Leverage what modern browsers already do. No framework, no polyfill, no ceremony. The platform ships features faster than any library.
The simplest API ever designed for behavior. One attribute adds interaction. No component model, no build step, no mental overhead.
The most democratic debugging tool in software. Inspect any page. Learn from it. Adapt it. HTML is the only authoring format that teaches itself.
Author in plain text. Any editor works. No account required. File lives on your machine.
One command. Clean, semantic HTML out. Works offline. Zero configuration needed.
A single minimal stylesheet handles typography, spacing, and reading comfort. Nothing else.
Double-click the file. No dev server. No install. No port. It just opens and works.
Drag the folder to Cloudflare Pages or Netlify Drop. Live URL in under 60 seconds.
A view-source-able, offline-capable, dependency-free page that will still open in 2046.
No authoring format has shipped to more devices, survived more platform shifts, or required fewer dependencies than plain HTML. The web's native language is also its most durable one.
Modern tooling built around HTML's strengths — not against them. Every piece of this stack is available today, runs without an account, and gets out of the way.
Start here. Write in plain text, convert with a single command, style with minimal CSS.
When HTML is the target format, agents can generate it directly — no compilation, no build step.
HTML is not a stepping stone to something better. It is the something better. The platform shipped the answer thirty years ago. We just kept building abstractions over it.
Pick a memo, a README, or a meeting summary. Write it as a single HTML file. No framework. Open it in the browser with double-click.
Take any page you already maintain. Remove everything except a single 50-line CSS file. Measure what breaks. Ship what doesn't.
Replace one Notion doc, Google Doc, or Confluence page with a plain HTML file hosted on Cloudflare Pages. Measure the difference.