Writing, quietly
This site used to be a card: one page, one stance, nothing to scroll. Now it has a place for writing, and this is the first post — partly an announcement, partly a test of the plumbing.
The mechanics are deliberately boring. A post is a markdown file in the repository; publishing it is a commit. The same pipeline that verifies the homepage verifies every article before it ships: tests, the build assertion, a deploy, and then a check of what production actually serves. Nothing here is hand-published.
A few things worth writing down:
- The stance is unchanged. No metrics, no catalog, no hero. Articles are allowed to be plain.
- The address of a post is its filename. Renaming a file moves the URL, so filenames are chosen as if they were permanent, because they are.
- Everything the site verifies about itself applies to these pages too — including the rule that no hosting provider is ever named in rendered output.
How a post ships
Write the file, commit it, and the pipeline does the rest — the same verification chain that guards the homepage guards every article. The quiet signal applies to prose as much as to the homepage: plain sentences, no decoration.
A post that needs a landing page, a hero image, or a metrics row is probably two posts and a problem.
Links behave like links — see the repo for
everything this site is built from, and inline code looks like this.
More on small models, serving loops, and product taste as the work produces it.
# the whole publishing pipeline, from one command line
npm run verify