Several brands, one engine
I design, build and keep several production sites running on the same Next.js base. All bilingual, all fast on a phone.
Beyond the individual projects, I operate a portfolio of production web properties under one engineering standard. It isn't a collection of one-off sites — it's a repeatable platform.
The problem
Running several sites at once, each with its own brand, language, and audience, usually degenerates into technical debt and inconsistent quality. The challenge isn't shipping one; it's making all of them clear the same bar without redoing the work each time.
The approach
A shared, opinionated engineering base:
- Common stack: Next.js + strict TypeScript, Tailwind, and deployment on Vercel.
- i18n by default, with correct hreflang and per-locale canonical URLs.
- Technical SEO out of the box: metadata, JSON-LD,
sitemap.xml, and per-page OG. - Performance budgets and analytics on every property, with CI before each deploy.
Treating the portfolio as a product — not as isolated gigs — is what makes it scale.
The result
Production properties that share a quality baseline, short delivery times, and predictable operations: a single operator maintaining several sites without giving up the standard.