Plain HTML
A blog post template is not just a blank page with prettier boxes. It is a small promise about what kind of writing belongs here.
This weblog now has templates, which means the next post starts with a shape instead of a negotiation.
The blank page is too vague
A blank HTML file is freedom, but it is also a little bit hostile. It asks every question at once. What should the title look like? Where does the date go? Is this a short note or a full essay? Should there be an image? How much introduction is enough before the first heading?
None of those questions are hard by themselves. The problem is that they all arrive before the writing has even started. The page becomes a design task, a publishing task, and a writing task at the same time.
A good template removes small decisions without removing the writer's judgment.
A template carries taste
The useful part of a template is not that it saves typing. That is nice, but it is not the main thing. The useful part is that it carries taste forward. It remembers the narrow article width, the warm paper, the quiet date, the single marmalade accent, and the rule that paragraphs should stay human-sized.
It also says no. No generic hero section. No fake stat row. No decorative feature grid pretending to be an argument. If the post is an essay, the shape should protect the essay from turning into a landing page.
The promise is small on purpose
A big template tries to predict the whole article. It adds too many sections, too many optional blocks, too many little knobs. Then the writer has to spend attention deleting the template before they can use it.
A small template does less. It provides the title, metadata, lead, a few headings, one quote or note, and a place to leave. That is enough structure to start and not so much structure that the post has to apologize for being itself.
Plain HTML still benefits from ceremony
The nice thing about plain HTML is that nothing is hidden. The template is a file. The post is a file. The archive is a file. The whole system stays visible enough that an agent can edit it and a person can understand what changed.
But visible does not have to mean improvised. A small amount of ceremony — a canonical post shape, a consistent metadata block, a real archive entry — makes the simple system easier to trust.
That is the promise: start with a shape, write a real thought, publish a page that still feels like it belongs to the same hand-kept notebook.