scher.nl
Personal project · October 2026

Website with Claude Code

How scher.nl came to be: a domain at mijn.host, hosting on Cloudflare, the source code on GitHub and a fixed route to publish a page from any project. Claude Code did the work in the terminal. The owner registered the domain, linked the accounts and gave approval at every step that put something live or deleted it.

Domain · mijn.host
€ 6.04 per year
Hosting · Cloudflare
free
From push to live
± 1 minute
Source code
GitHub (private)
At a glance

From project to scher.nl

From project to scher.nl A page is created in a project. Claude Code uses the skill to put it in a branch of the GitHub repository and opens a pull request. Cloudflare builds every branch into a preview URL. After the merge to main the page is live on scher.nl. The domain is registered at mijn.host, which points to Cloudflare with nameservers. Every projectgmail · taipan · … Claude Codeskill + privacy check PR GitHubbranch · main push Cloudflarebuilds branch Preview URLcheck it first merge scher.nllive · https mijn.hostdomain registration nameservers point to Cloudflare
The route

From domain name to first project page

  1. 1

    Register the domain

    mijn.hostOwner

    scher.nl is registered at mijn.host, a Dutch registrar. The domain stays there: ownership and renewal run through mijn.host, separate from the hosting. The registration costs € 6.04 per year, including VAT.

  2. 2

    DNS to Cloudflare

    CloudflareOwner

    The domain was added as a zone in Cloudflare. At mijn.host the nameservers were replaced by the two that Cloudflare provides. From that moment Cloudflare handles the DNS, the https certificates and the traffic to the site.

  3. 3

    Build the homepage

    Claude Code

    A single static page in HTML and CSS, with no framework or build step: a card per project with what it does, its status and what it costs.

    HTML · CSSArchivo · IBM Plex
  4. 4

    Git and GitHub

    Claude CodeGitHub

    The project folder became a git repository, with a .gitignore that keeps keys and .env files out. Claude created a private repository with the GitHub CLI and pushed the first version. The main branch is from now on what is live.

    gitgh (GitHub CLI)
  5. 5

    A Worker for static files

    Claude CodeCloudflare

    A small configuration tells Cloudflare that everything in the site/ folder is served as a website. Before pushing, Claude checked the configuration with a dry run that deploys nothing.

    {
      "name": "scher-nl",
      "assets": { "directory": "./site", "not_found_handling": "404-page" },
      "routes": [
        { "pattern": "scher.nl", "custom_domain": true },
        { "pattern": "www.scher.nl", "custom_domain": true }
      ]
    }
    wrangler.jsoncWorkers static assets
  6. 6

    Connect Cloudflare to GitHub

    OwnerCloudflare

    In the Cloudflare dashboard the repository was imported, with access to this one repository only. The owner made that connection personally, because it involves access to an account. The first build was live within half a minute on a workers.dev address.

    Workers Builds
  7. 7

    Own domain and 404 page

    Claude CodeCloudflare

    With the routes in the configuration, Cloudflare creates the DNS records and certificates for scher.nl and www.scher.nl itself. About seventy seconds after the push the site was reachable on its own domain, and an unknown address shows a neat "Not found" page.

  8. 8

    Adding the new cf CLI

    Claude CodeCloudflare

    In September 2026 Cloudflare released cf, a new command-line tool for the whole Cloudflare API. Claude first verified that the npm package really comes from Cloudflare and then added it to the project as a development dependency. That way Claude and my own terminal use the same version.

    npm i -D cf
    npx cf cli search "<what you want to do>"
  9. 9

    A skill for publishing

    Claude Code

    The whole route is captured in the Claude skill publiceer-op-scher. From any project, one instruction is now enough to prepare a page as a pull request with a preview. This page was published with it too.

Why this way

The benefits of publishing through GitHub and Cloudflare

One source

Everything kept, everything reversible

Every version of every page is in git. If something goes wrong, an earlier commit restores the old site. There is no debate about which copy is the right one.

Preview

Look first, then go live

Every pull request gets its own preview address with exactly the new version. The merge is the moment of approval; before that, nothing is on scher.nl.

Automatic

Publishing without uploading

A push to main is enough: Cloudflare builds and deploys within about a minute. No FTP, no copying files, and the projects need no Cloudflare keys.

Fast and secure

Worldwide, with https, for € 6.04 per year

The pages are served from Cloudflare's network, close to the visitor, with automatically managed certificates. The hosting is free: requests for static files cost nothing with Workers, and neither does the private repository on GitHub. The only fixed cost is the domain: € 6.04 per year, including VAT.

Skill

From any project, always the same

Whether a page is created in the Gmail project or the Tai Pan project: the skill puts it in the same place, in the same style, with the same privacy check and the same check after publishing.

Division of roles

Each part can be replaced separately

The domain is at mijn.host, DNS and hosting at Cloudflare, the source code at GitHub. Claude does the work; the owner makes the decisions. Anyone who later wants to switch hosting does not have to move the domain.

Version control

What GitHub does here

Pages are created in different projects, but they all end up in one repository. GitHub is thus the hinge between the work in the projects and the live site.

WhatWhy it helps
One sourceAll projects deliver to the same repository, so there is one true version of the site.
Automatic publishingThe repository is connected to Cloudflare. A push to main puts the site live, with no Cloudflare keys on the laptop or in the projects.
Preview per pull requestA new page first runs on its own address. That is the checkpoint.
HistoryEvery change can be found and reversed.
ActionsRoom for automatic tasks, such as fetching cost figures of projects overnight or checking links.
IssuesA place for the list of pages and ideas still to come.
Tooling

Wrangler or the new cf CLI?

Until now Wrangler was the command-line tool for Cloudflare Workers. With cf Cloudflare is making a tool that covers the whole Cloudflare API and was designed from the start for AI agents such as Claude Code. According to Cloudflare, agents already accounted for almost half of Wrangler's usage.

Wrangler · oldcf · new
ScopeAbout 280 commands, mainly for building and deploying Workers.The whole Cloudflare API, over 3,000 operations: also DNS, firewall, Access, email, domains, D1, R2 and more.
Made forPeople in the terminal. Agents use it, but have to adapt.Agents first. With cf cli search an agent finds the right command in plain language, without reading all the help texts.
OutputText and tables; JSON only with extra options.JSON by default: formatted readably for people, compact for agents. That saves tokens.
Configurationwrangler.jsonc or wrangler.toml.cloudflare.config.ts in TypeScript, with type checking and autocompletion in the editor.
Buildingesbuild.Vite, with instant reloading during development and Vitest for tests. cf migrate converts a Wrangler project.
StatusStable. Gets another 18 months of maintenance after cf's beta.Open beta. For now cf still lets Wrangler build Python and Rust Workers.
Role at scher.nlDeploying: Cloudflare runs wrangler deploy for main and wrangler preview for branches.Management and research from Claude Code, through npx cf in the project.

For deploying, Wrangler stays in use for now: the connection between GitHub and Cloudflare works reliably, and cf is still in beta. Switching can happen later with cf migrate.

Making it repeatable

Publishing with a skill

A skill is a captured way of working that Claude Code loads as soon as a request fits it. The skill publiceer-op-scher lives in my own Claude folder on the laptop, and therefore works in every project. A sentence like "put this write-up on scher.nl" is enough.

  1. Determine which page it is and under what name: scher.nl/projecten/<name>/.
  2. A clean copy of the site repository fetched into a temporary folder, so that ongoing work elsewhere is left untouched.
  3. Prepare the page: a complete HTML document, dark theme, a link back to the homepage.
  4. Both languages: the same page in Dutch and in English, at /projecten/<name>/ and /en/projects/<name>/, with hreflang links and a language switch.
  5. Privacy check: searching for email addresses and keys, and reading through for real names and data.
  6. The project card on both homepages pointed at the new page.
  7. Check locally: view the page in the browser and test the configuration with the same Wrangler version as Cloudflare.
  8. Branch and pull request, after which Cloudflare builds the preview.
  9. Merge only after approval, and then check that the page and the link on the homepage are live.
Why a skill rather than explaining it every time? The pitfalls from the first time are now built in, such as a missing setting that made the first preview build fail, and that shortly after a merge the old version can still appear for a moment. Every next page therefore goes right the first time, whichever project it is created in.
Agreements

What Claude does and does not do itself