Active solarpunk office with professional knowledge projected onto a glass wall
PORTFOLIO + CMS + AI

About Me Platform

A personal publishing system for a bilingual portfolio with Payload CMS, reusable blocks, structured content, and AI-ready flows.

Status:Active
Period:2024 - Present
Role:Product Builder, Full-stack Developer
Primary stack:Next.js, Payload CMS, TypeScript, Firebase

Summary

About Me Platform is not just a landing page: it is an editorial and technical product for consolidating professional trajectory, projects, evidence, and narrative into a maintainable system.

The platform organizes scattered information into collections, blocks, and reusable flows for publishing the portfolio, experience timeline, and content prepared for AI-assisted queries.

Next.jsPayload CMSTypeScripti18nFirebaseDesign System

01Context

The portfolio needed to move beyond a static page and become a living editorial base for experience, projects, articles, and contact.

It is not just a landing page: it is an editorial and technical product for consolidating career, evidence, and narrative into a maintainable system.

  • An 18+ year profile needed editorial structure, not loose sections.
  • Projects, experience, articles, and evidence had to update from a maintainable source.
  • ES/EN content needed equivalent meaning without manually duplicating every page.

02Problem

Professional information was scattered across documents, repositories, histories, and visual materials. Without structure, it was hard to keep ES/EN, evidence, and narrative aligned.

03Solution

Build a Next.js + Payload platform where projects are modeled as rich documents with templates, relationships, localized fields, and shared UI components.

projectDetailTemplate
  collection: projects
  locales: [es, en]
  adapter: mapPayloadProjectToTemplate()
  checks: visual QA + integration tests

04Execution

Collections, blocks, UI adapters, localized routes, forms, media, integration tests, and an architecture separating Payload content from reusable presentation were implemented.

Architecture and decisions

01. Payload as editorial source

Payload centralizes projects, pages, articles, and editable configuration so content can grow without changing components for every update.

02. Bilingual routes and content

The site keeps canonical Spanish and English routes with localized document content instead of duplicating page structures.

03. CMS-to-UI adapters

Adapters transform Payload data into UI contracts, keeping shared packages free from CMS dependencies.

ProfileStructured professional trajectory
EvidenceProjects treated as cases
ES/ENBilingual editorial profile

Evidence and records

Five-page editorial case covering the problem, content system, product architecture, and demonstrated professional value.

View case study

Specialized brief on Ask AI: verified execution, RAG pipeline, citations, operational controls, and provider architecture.

Explore Ask AI and RAG

Technical record of the design-to-code flow, bilingual publishing, media, testing, and system governance.

Review architecture and operations

Let's talk.

Currently exploring new opportunities. If you have a question or just want to say hi, I'll do my best to get back to you.

[email protected]