hetwiel

How the wheel turns

A method in six steps

How the experiment works, from a sentence in plain words to a working application. The explanation is automated too.

Swipe sideways to see the whole drawing.

Flow of one change the maker has an idea 10 an AI turns the sentence into code, builds a trial, checks it 20 Git repository private content styles and scripts server configuration 30 CI pipeline on every push and every night 40 a VPS a small server, somewhere in Europe 50 reverse proxy handles HTTPS and routes each request to the right place 52 the website hetwiel.dev 54 experiments subdomains of hetwiel.dev 56 still to come 58 DNS translates the name into an IP address 60 a visitor types hetwiel.dev 70 How the wheel turns hetwiel not to scale Plate II 2026 sheet 1 of 1 “Make the heading less playful.” shows the result or edits it himself git push over SSH, with a key looks up the IP address opens the site

Fig. 1. Method for reinventing the wheel.

  1. 10the maker
  2. 20an AI
  3. 30Git repository
  4. 40CI pipeline
  5. 50VPS
  6. 52reverse proxy
  7. 54the website
  8. 56experiments
  9. 58still to come
  10. 60DNS
  11. 70a visitor
  • the route of one change
  • the maker edits something himself
  • a visitor opens the site

Step by step

No.StepWhat happensUnder the hood
1The ideaA sentence in plain words: what should change, and why.a prompt, not code.
2Build and testAn AI writes the code, builds it locally and checks the result on desktop and mobile before anything moves on.local build, headless browser, screenshots.
3Version controlEvery change is a commit in a private Git repository, so every version can be restored.Git, private repository.
4The pipelineEvery push, and every night, a CI pipeline rebuilds the whole site from text files and templates.continuous integration, static site generator, nightly build.
5DeployThe pipeline logs in to a VPS with an SSH key and places the new files. No passwords involved.SSH, key pair, containers.
6OnlineDNS points hetwiel.dev to the server. A reverse proxy handles HTTPS and routes each request to the site or an experiment.DNS, reverse proxy, certificates that renew themselves.