scher.nl
Personal project · November 2026

CMS on scher.nl

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.

Try the demo → Edit mode on the homepage, without logging in. What you type stays in your browser and is not saved.
Functions
4
Editable pages
10
Translation
NL → EN
From save to live
± 2 min
The scher.nl homepage in the edit mode demo: the heading has an orange frame because the mouse is on it, the introduction a green frame because it was changed, and at the bottom a bar with 1 text changed and the buttons Save, Reset and Stop.
The homepage in the demo: a changed text gets a green frame, the bar at the bottom counts the changes.
At a glance

From text to live site

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.

How a text change goes live A text is changed in the text file on GitHub, in the CMS at scher.nl/admin or on the page itself with edit mode. All three write to the page's text file, with Dutch and English per text. The GitHub Action Teksten has Claude update the English and builds the HTML from the texts and the template with the layout. Cloudflare puts the page live in both languages. Text fileon GitHub CMSscher.nl/admin On the page?bewerk TextsNL and EN per text Templatelayout, just once Action TekstenClaude translates · builds Cloudflarelive NL + EN
Starting point

How it used to be

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.

Built

Four functions, each one a step further

  1. 1

    Texts separate from the layout

    Claude CodeGitHub

    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.

    BeforeThere was no function for editing texts. Every change was a prompt to Claude, which edited the HTML of both the Dutch and the English page on a branch with a pull request, after which you checked the preview and merged. Even for a comma. Doing it yourself meant editing the HTML directly, with a chance of breaking the page.
    ImprovementOne clear file per page, NL and EN side by side. You no longer touch the layout, so it cannot break either.
    teksten/*.yamlsjablonen/npm run buildnpm run check
  2. 2

    Automatic translation with Claude

    Claude APIGitHub Actions

    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.

    After step 1Clear, but every change still done twice: translating yourself and running the build yourself.
    ImprovementOnly edit the Dutch. Translating, building and going live happen automatically, and the translation passes the same HTML filter as every text.
    Claude Sonnet 5.5changed texts onlyHTML filter
  3. 3

    A CMS at scher.nl/admin

    Sveltia CMSCloudflare Worker

    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.

    After step 2Only Dutch, but still opening a YAML file on GitHub and finding the right key.
    ImprovementJust a form in the browser, on a phone or tablet too. No files, keys or git needed any more.
    Sveltia CMSGitHub App, 1 repologin via own Worker
  4. 4

    Editing on the page itself

    Claude CodeOwner

    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.

    After step 3In the CMS you edit fields away from the page, and have to work out which field belongs to which sentence.
    ImprovementWhat you see is what you edit, exactly where it sits. No more searching, and you see straight away how it looks.
    ?bewerksame login as /adminchanged texts only
Under the hood

The Claude API

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.

AspectClaude app (desktop)Claude API
Who it is forA person who chats, writes or buildsA program, such as a GitHub Action
How it startsYou type a questionAutomatically, on every push
Without youNo, someone has to askYes, also after a change in the CMS or with ?bewerk
ReplyFree text in a conversationFixed format that code checks and processes directly
PredictableEach conversation a little differentThe same instructions and the same model every time
CostFixed monthly amount (subscription)Per use, with a spending limit
Strong atThinking along and building, like this site with Claude CodeRecurring work in a build pipeline

Why the API here

  • Translating has to happen without anyone doing anything. A text from the CMS or edit mode arrives as a commit, and the Action runs on a GitHub server, where there is no Claude app.
  • The translation goes into the site without anyone in between. So the reply needs a fixed format that code can check, rather than a chat message.
  • Every translation follows the same fixed rules: keep HTML tags, link to the English pages, do not translate proper names. That makes the result predictable every time.
  • Only changed texts go to Claude, so usage per change is small, and it can be traced per request.
  • The Claude app remains the tool for building and improving the site. The API handles the automatic part behind it.
Comparison

Then and now

TaskBeforeNow
Changing a sentenceOpen two HTML files and search between the tagsClick on the page and type
English versionTranslate and enter it yourselfClaude translates on every change
WhereA computer with the code, or a prompt to Claude CodeAny browser, on a phone too
Risk of a broken pageA forgotten tag breaks the layoutLayout is separate; the build checks every text
New pageKeep texts in two languages up to date by handShows up in the CMS and edit mode automatically
Try it yourself

The demo

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.

Works like the real thingClick and type over any visible text on the homepage, changed texts light up, the counter in the bar, and putting everything back with Reset. On the English homepage too.
SimulatedSave only shows what happens for real: a commit, the translation by Claude and live within two minutes. What you type exists only in your own browser window and is gone after a reload.
Why no real saving for visitors? Every change on main is live within two minutes. Writing therefore requires a GitHub login with rights to this one repository.
Try the demo →