Engineering / Platform / Tech stack
Built To Last.
React / TypeScript / Design systems / CMS / Delivery
The tools follow the problem, and I can tell you why each one is there.
01 / The engineering mindsetDecisions / Not checklists
Technology serves / the experience
A good stack is
an informed decision.
The architecture has to work for visitors, for the people who edit the content and for the business. I go for clear boundaries, small components, strict types and numbers I can measure. A dependency has to earn its place.
02 / The working stackCurrent tools / Selected for fit
What I use, when it fits.
01 / Product engineering
React & TypeScript
Interfaces built from reusable parts, predictable state, and clear lines between the parts of the business.
- React 19
- TypeScript
- React Router 8
- Next.js 16
- Vite
- React Compiler
- tRPC
- TanStack Query
- Zustand
- Redux / RTK
- Zod
02 / Experience system
UI systems & front-end
Layouts for every screen, design systems built on tokens, and components everyone can use.
- HTML / CSS
- Tailwind CSS 4
- CSS custom properties
- OKLCH tokens
- ARIA patterns
- Headless UI
- Storybook
- React Hook Form
03 / Content operations
Custom CMS & integrations
Content models, every language, and editing workflows shaped around what the client publishes.
- Headless CMS
- Adobe AEM
- i18next
- REST / API
- Node.js
- Hono
- Drizzle ORM
- PostgreSQL
04 / Verification & delivery
Quality & infrastructure
Tests, a clean build, deployment and monitoring, from the first week.
- Playwright
- Vitest
- Testing Library
- MSW
- Sentry
- GitHub Actions
- GitLab CI
- Docker
- AWS Lambda
- SST
- Cloudflare Workers
- PWA
03 / Production principlesHow good code stays useful
This site, for example.
This site is React Router 8, prerendered to static HTML. Its content pages load no React in the browser; one script of about 3 kB does the rest. Tokens, strict types, tests and a weight budget keep it easy to change.
Engineering & CMS service
04 / Engineering standardsChecked on every release
Four standards, all checked.
Accessible by design.
WCAG 2.2 AA at least: proper HTML, full keyboard use, a visible focus, and content everyone can perceive.
Fast in real conditions.
Core Web Vitals measured, modern image formats, caching, and pages rendered ahead of time where possible.
Clear to maintain.
Typed contracts between the parts, documented components, and behaviour that tests can cover.
Ready to evolve.
Versioned releases, CI/CD, the security basics, and clear ownership after launch.
05 / The proofEngineering applied to real products
A product, built from scratch.
Divorcio is a web app; this site is a set of static pages. They need different choices and the same care.
Divorcio / React + TypeScript + PWA
View the Divorcio case study
Stack / Start a conversation
Good Systems. Better Work.
Tell me what your product has to do, and I’ll pick a stack that can do it.
Start a project