Engineering
How we build, with receipts.
This site is the worked example. What it is built with, what we measured on it, and the habits behind it. Figures carry the date they were read.
This site, as built
- Framework
- Next.js 15 static export on React 19, styled with Tailwind 4. No server at request time.
- Content
- One bilingual content layer (English and Spanish) rendered into both languages, with hreflang and a sitemap generated from the same route list.
- Type
- Self-hosted fonts (Plus Jakarta Sans and Instrument Serif), no third-party font requests.
- Structured data
- JSON-LD generated per page: organization, founder, services, products, articles, FAQs and breadcrumbs.
- AI readiness
- An llms.txt, an open robots.txt for AI search crawlers, and a published security.txt.
What we measured on it
- 0automated accessibility violations (axe, WCAG 2.2 AA rules) on every page we scanned, in light and dark themes and both languages
- 100Lighthouse accessibility, best-practices and SEO scores in the latest local run
- 99Lighthouse mobile performance on the production site, with a 1.7 s largest contentful paint
Measured October 20, 2026 with Lighthouse and axe on this site.
Quality gates on every build
Nothing reaches a client on trust. A build has to pass automated checks first.
Markup validation
The HTML of every page is validated before a person sees it.
Accessibility scan
An automated accessibility scan runs on every route.
Performance and SEO audit
Lighthouse measures speed, accessibility, best practices and SEO.
A second opinion on coherence
Model judges from different vendors review the finished pages for consistency.
How we run things
Written scope first
Nothing is built before both sides agree, in writing, on what done means.
Edge-gated admin
Admin paths are intercepted at the edge before any application code runs.
Secrets stay out of code
Keys and credentials are never committed and are rotated when access changes.
Recoverable by design
Every engagement ships with runbooks, recovery procedures and credential escrow.
Engineering notes
Building a benchmark harness that survives its own failures
To score 808 websites we ran headless browsers, Lighthouse, accessibility scans and AI judges for hours. The first run died at site 327 without an error. What we changed so a failure costs minutes, not the whole run.
Read the note →Silent failures: the bug shape that costs us the most
Loud failures get fixed in an hour. The expensive bugs are the ones that report success. Four patterns we have hit while running our own products, and the one rule that catches them.
Read the note →Turning a PDF dump into a public atlas: how we built Atlas Criminalidad CR
A country’s crime data was open and unreadable at the same time. Here is the architecture that turned a quarterly stack of PDFs into a tool anyone can read in 5 minutes — and that keeps working every release.
Read the note →Open source and experiments live in Labs. Open Labs
Want this level of detail on your project?
Every engagement starts with a written scope and ends with documentation. Book a call and bring the hardest requirement.