Until early November, every text change on scher.nl meant working in HTML, and doing it twice: in the Dutch and in the English page. That changed in four steps. Now you edit a text in a form or right on the page, and Claude takes care of the English.
There are three ways to change a text. All three end up in the same text file, and from there it happens automatically: translating, building and going live.
Each page existed as two HTML files, one Dutch and one English, with the text right in the middle of the markup. Changing a sentence meant finding the right file, locating the sentence between the tags, editing it without breaking a tag, and then doing the same in English, translated by hand. That usually took a prompt to Claude Code, even for a comma.
All texts now live in one text file per page (teksten/<pagina>.yaml), with the Dutch and English versions one below the other. The layout sits in a template shared by both languages. A build turns them into HTML and checks that the Dutch and English pages have the same structure.
After every push, the GitHub Action Teksten finds which Dutch texts have changed, has Claude (Sonnet 5.5) translate only those into English, rebuilds the HTML and commits the result back. An English text you write yourself is kept. If HTML is still edited directly, or a new page is created as HTML, the Action pulls those texts into the text file as well.
At scher.nl/admin there is a CMS with a form per page and readable field names. You log in with GitHub, through a dedicated GitHub App that can only reach this site; the login runs through scher.nl's own Worker. Save becomes a commit, and the Action from step 2 does the rest. The forms are generated from the text files on every build, so a new page shows up automatically.
Add ?bewerk to the address of a page, and every visible text becomes clickable. You type over it, the changed texts light up, and Save writes only those texts to the text file. It works on every page and in both languages, with the same login as the CMS. For texts you cannot see, such as the page title or texts inside a figure, the CMS remains the place.
The translation in step 2 runs through the Claude API: access to Claude for programs rather than for people. On every push, the GitHub Action sends one request per page with the changed Dutch texts, plus the existing English texts as context, so terms and tone stay consistent. Claude (Sonnet 5.5) replies in a fixed format: exactly one English translation per text. That reply first passes the HTML filter and only then goes into the site.
There is no human at the wheel in this step. The Action uses an API key that is stored as a secret in GitHub and is only available in the translation step. Usage is billed per request, separately from the Claude subscription, and it has a spending limit.
| Aspect | Claude app (desktop) | Claude API |
|---|---|---|
| Who it is for | A person who chats, writes or builds | A program, such as a GitHub Action |
| How it starts | You type a question | Automatically, on every push |
| Without you | No, someone has to ask | Yes, also after a change in the CMS or with ?bewerk |
| Reply | Free text in a conversation | Fixed format that code checks and processes directly |
| Predictable | Each conversation a little different | The same instructions and the same model every time |
| Cost | Fixed monthly amount (subscription) | Per use, with a spending limit |
| Strong at | Thinking along and building, like this site with Claude Code | Recurring work in a build pipeline |
| Task | Before | Now |
|---|---|---|
| Changing a sentence | Open two HTML files and search between the tags | Click on the page and type |
| English version | Translate and enter it yourself | Claude translates on every change |
| Where | A computer with the code, or a prompt to Claude Code | Any browser, on a phone too |
| Risk of a broken page | A forgotten tag breaks the layout | Layout is separate; the build checks every text |
| New page | Keep texts in two languages up to date by hand | Shows up in the CMS and edit mode automatically |
The demo is the same edit mode, with ?bewerk=demo in the address. Only saving does nothing: there is no login and no connection to GitHub, even if the owner is logged in in the same browser.
main is live within two minutes. Writing therefore requires a GitHub login with rights to this one repository.