About Me Platform
An editorial platform to transform over 18 years of trajectory, projects, and scattered evidence into structured, publishable, and consultable content.
Summary
About Me Platform was not born as a landing page. It is an editorial and technical product that converts a trajectory distributed across CVs, repositories, backups, captures, and projects into a maintainable source of truth.
Payload organizes the content; Next.js publishes it; shared packages connect UI, tokens, and AI. The result serves the portfolio, the professional timeline, and a corpus prepared for RAG queries with traceability.
01From static CV to source of truth
The professional trajectory existed, but not as a system. CVs, screenshots, repositories, backups, documents, and projects told different parts of a story spanning over 18 years. The opportunity was to transform that scattered archive into a living editorial base, with context, evidence, and the ability to evolve.
An extensive professional trajectory doesn't need another static page: it needs a source of truth capable of preserving context, evidence, and editorial judgment.
- Facts, personal memory, and confidential material needed clear editorial boundaries.
- Projects and experiences needed to be updated from a maintainable source, not from duplicated pages.
- ES/EN content, SEO, and evidence required consistency without losing nuances per locale.
- Information needed to be prepared for RAG without publishing private notes or local sources.
02Dispersion is also a product problem
Without a content model, each update required reconciling isolated pieces. Maintaining equivalence between languages, distinguishing public from private, and reusing evidence in the portfolio, timeline, or an AI-assisted response became slow and fragile.
03Structured content, reusable presentation
The solution is a Next.js + Payload application where pages, projects, and experiences are related documents. Blocks allow composition without hardcoding; adapters translate the CMS into UI contracts; i18n, SEO, drafts, and live preview transform editing into a real publishing workflow.
content sources
-> Payload collections + blocks
-> localized adapters
-> Next.js routes
-> portfolio + timeline + RAG corpus04An operable product, not a demo
The monorepo separates the UI web application, tokens, AI, and shared configuration. It includes local media or Firebase/GCS, emulators, localized routes, sitemaps, forms, Playwright and Vitest tests, plus utilities to migrate, audit, repair, and synchronize content.
Architecture and decisions
01. Content as Data
Experiences, projects, evidence, and visibility are modeled as structured data. The same source can feed a public page, timeline, career materials, and RAG corpus without rewriting the story for each channel.
02. Block-based CMS
Payload retains editorial authority, and the block system controls composition. The template defines a stable hierarchy; the dynamic zone allows extending technical cases without turning each project into a new component.
03. Design Connected to Code
Sketch and Stitch support visual exploration and direction; W3C tokens pass through Style Dictionary and end up as variables consumed by Tailwind and the UI package. The visual reference evolves without breaking the content source.
04. Bilingual and Discoverable Publishing
Localized fields, canonical ES/EN paths, drafts, live preview, sitemaps, redirects, and SEO metadata are part of the editorial product. The translation preserves structure but is audited per document to avoid poor automatic equivalences.
05. Media with recovery path
The system supports filesystem and Firebase/GCS, emulator, and optimized variants. Auditing, repair, regeneration, and backfill utilities treat files as an operable asset, not as links impossible to reconstruct.
06. AI with editorial context and boundaries
Ask AI and the RAG corpus reuse curated content, with traceability and separation between public and private data. AI is integrated into the research and consultation workflow; it does not replace source validation or convert the roadmap into already delivered capabilities.
07. Operational quality
Integration and e2e tests, migration scripts, audits, and visual verifications reduce the cost of evolving CMS, locales, and media. The criterion is to be able to change content and structure with a clear way to verify the result.
Evidence and records
Editorial case study in five slides: problem, content system, product architecture, and demonstrated professional value.
Specialized document on Ask AI: real execution, RAG pipeline, citations, operational controls, and multi-vendor architecture.
Technical log of the design-to-code flow, bilingual publication, media, testing, and system governance status.