The standard behind the work, applied to my own

Why this is here#

The development service asks a buyer to trust a standard. The fairest evidence of a standard is work nobody commissioned and nobody was going to inspect, so this page describes the codebase behind avanserv's own product and this site. The repository is private, and what follows is drawn from it.

What every change goes through#

No single green check merges anything. A change passes type checks, lint, unit and end-to-end tests, a scan for secrets and known vulnerabilities, and a prose check that holds comments and documentation to a written style. Every public page is swept against WCAG 2.2 AA in both themes, and ships in two languages, neither falling back to the other. Then the change is reviewed: by an automated reviewer on every pull request, and by me. A failing check blocks the merge.

How it reaches production#

The infrastructure is code, on European hosting, and every environment is built from what the repository says. The path from a merge to a running environment is written down as runbooks rather than remembered, so someone who is not me can follow it.

Where to read more#

The build log is the long form. Three posts cover this page's ground in detail: the gate every change passes before review, holding the site to WCAG 2.2 AA, and staging environments built from git.