Layer02 website

Two languages, 34 static pages, zero third-party requests before the booking click

The problem

A studio that builds websites has to show one it built, and the site has to hold to the same rules it sells: honest labels, both languages complete, no tracking before a visitor decides to book, and every visual change checked in a browser before it goes live. Most agency sites fail at least one of these, usually the second and the third.

The system

This site. The copy and every case study live as MDX files, one per language, and a check runs before every build: a key missing in German or English fails the build, so a half-translated page cannot ship. The pages are built once as static HTML and served from Vercel; fonts are self-hosted, and no request leaves for a third party until "Book a meeting" is clicked. The hero window is a hand-built demo with a 155-check browser suite behind it; the home page and every route are walked by a smoke check that counts external requests and console errors, and screenshots at 375 px and 1280 px are compared before a change is merged.

What it does now

It runs at layer02.co. Content changes are a text edit and a push; the checks say within minutes whether anything broke. Copy is drafted with AI and read by a person before it goes out, and the legal pages are written by a person, not generated.

Where AI checks and where it decides

Step	Who decides
Draft copy, translations and the diagram texts	AI drafts, a person reads every page
Impressum, privacy text and what the site claims	A person decides