Blueprint
A bilingual engineering lab built around original work and documented decisions.
The question
How can a personal lab make engineering decisions visible without becoming a résumé? Blueprint organizes its public work into Builds, Experiments, and Notes.
Architecture
The approved v1 uses Next.js, TypeScript, Tailwind CSS, and repository-owned MDX. Public content is generated at build time. English is the source language; reviewed pt-BR translations live under /pt.
A single validated content registry connects article routes, listings, translations, and SEO metadata. No database, authentication, or CMS is required for v1.
Decisions and trade-offs
- Static generation favors simple deployment and reviewable content. Content updates require a new build.
- Repository-owned MDX keeps changes visible in pull requests. Authors must review MDX as build input.
- Translation happens during authoring, preserving technical names and code. English publication does not depend on translation availability.
- Vercel Web Analytics is the approved minimal analytics solution. Metrics stay private.
Current boundary
Blueprint is in implementation. Production deployment and the public launch remain pending. This entry does not claim measured performance, completed experiments, or deployment results.
See the lab's purpose and the repository design note.
Engineering Log
First production deployment — pending resolution
The first Vercel production deployment failed after Next.js completed static route generation. The failure occurred in Blueprint's custom post-build output verification: it expected .next/server/app/index.html, a fixed internal Next.js output path that was not present in the Vercel build environment.
The engineering lesson is that custom verification should not depend on undocumented or environment-specific framework output paths. Resolution remains pending until the corrected production deployment and the custom domain blueprint.app.br over HTTPS are successfully verified.