Keep a plain directory of HTML files, then use a coding agent as your writing and publishing assistant.
Why this setup feels different
Most writing tools want to put a system between you and the page: a CMS, a generator, a theme, a plugin chain, or a content format that eventually turns into HTML. This site flips that around.
The published page is the source of truth. I write in chat, and the agent turns that into a real page that I can inspect, edit, and deploy directly.
What the agent actually helps with
I do not care much about “AI wrote my blog post.” I care that an agent can do the fiddly web work around writing.
- Create a new post page with the right structure.
- Update navigation and archive pages consistently.
- Make coordinated edits across multiple files.
- Tweak layout, spacing, and styling without introducing a framework.
Why skip Markdown
Markdown is great when you want a narrow, predictable writing format. But if HTML is your final output anyway, it can be refreshing to work with the final medium directly.
That means headings, links, lists, emphasis, and structure can be exactly what the page needs. If I want to add a callout, a small visual block, or a custom layout later, I do not have to fight a content pipeline first.
Why I like it
It keeps the stack small. There is no static site builder, no admin panel, and no large abstraction layer to maintain. Just writing in chat and generating HTML directly, with full freedom over layout and design.
For a personal site, that feels like the right tradeoff: fewer moving parts, more ownership, and pages that stay easy to understand years later.