
r352.com
A site that checks itself before it ships
- 80+
- Pages, One Build
- 4
- Blocking Checks per Release
- 6
- Releases in One Day
This site is our own case, and the point of it is practical: how one person keeps a large bilingual site consistent and safe to publish. More than 80 pages in two languages come out of a single build, the rules live in the system rather than in someone's head, and nothing reaches production until four automated checks pass. People make the decisions, AI does the assembly in between.
The site, live
The problem
A small team cannot review 80+ pages by eye every time something changes, and a site that says 'we build systems' cannot be maintained by hand. Speed without checks breaks things quietly: a meta description that is too long, a link too small to tap on a phone, a Polish page pointing at an English one.
What we took responsibility for
Everything, which is the point: positioning, design, code, both language versions and the checks that decide whether a release is allowed to go live.
Capabilities at work
- Strategy & Design
- A written design system and machine-readable tokens are the source of truth for the team and for every AI session that touches the site.
- Digital products
- 80+ pages prerendered to static HTML from one build, in English and Polish, with mutual language pairs checked on every release.
- Creative delivery
- Changes ship the same day through one pipeline: six production releases in a single day during the September 2026 update.
- AI elevation
- AI builds and verifies between decisions. A person approves every release, and the gates hold the standard when the pace goes up.
Decisions
One deploy command, no shortcuts: build, then four blocking checks, then release. The crawl check reads every page for titles, descriptions and headings. The link check looks for orphan pages and language leaks. The mobile check opens key pages at 390 px and counts tap targets under 44 px against a budget. The interaction check clicks every control to make sure nothing crashes. A separate brand check compares the written guide with the code.
How we delivered
Content lives in data, pages are compiled from it, and AI writes the difference instead of the page. When the offer moved from three areas to four capabilities, the home page, the services map, the services page and three case studies changed together, in both languages, because they read from the same structure.
The work
Every page, from one build

Living backgrounds: WebGL and motion
Light mode: the same system, inverted
The same cockpit on a phone





Navigation that tells the same story



One image language: graphite and a single lime signal







Brand Centre: the rules, written down
The mascot: a friendly robot
"Two releases were stopped that day. Neither of them reached a single visitor.
Outcome
During the September 2026 update the site went through six production releases in one day. Two more were blocked by the checks before going live: one for meta descriptions over the length limit, one for new links that were too small to tap on a phone. Both were fixed at the source, not by loosening the budget.
Reflection
The checks are not there because we distrust the work. They are there so the work can move fast without anyone having to remember everything.