Concept
A one-page bilingual concept note for a food brand: plain markup, capped WebP images with identifying metadata stripped, no build step and no framework, because a concept page does not need one. What it does need — and what makes it worth a place on this map — is that it was the first product in the fleet deployed by a daemon pulling a signed, tagged image rather than by a CI job pushing credentials into production.
The page is hardened against the casual kind of scraping a public menu concept actually attracts: a strict content policy, transport security headers, a frame-denial header, and hotlink protection on its own images and fonts. None of this is presented as unbeatable — a screenshot always exists — it is priced to stop casual and semi-clever copying, not a determined attacker.
Because it carries no application logic at all, it also doubles as the fleet's simplest proof that the pull-based deploy pattern works end to end: build an image, tag it, let the runway pull it, gate on health, and roll back automatically if that gate fails — the same mechanism every later product now relies on.
← back to the map