José MavarezCase 02 / 03
ESEN All work
02 — Aquinas Network SAS · Performance · headless WordPress

Headless WordPress architecture with a React front end

Role
Senior consultant
Period
Independent practice, 2022 — 2025
Platform
Headless WordPress · React
Note

The visualizations in this case are representative reconstructions of the architecture. The site live today at aquinasnetwork.com is a different build, on WordPress and Elementor, and does not show this work. The LCP figure is the one I report in my CV.

Representative visualization · no real brand or content
Traditional WordPress
  1. WordPress
  2. Theme
  3. Page
Headless WordPress
  1. WordPress (content)
  2. API
  3. React front end
  4. Page
Fig. 0 — Illustrative sketch: WordPress stays as the content manager and the React front end consumes it through an API. It does not reproduce the project’s infrastructure.

01 — Context

Aquinas Network SAS brings together solutions for schools —an online library, consulting and accreditation, content development, technology and educational marketing— and needed to present them on one site without them competing with each other.

02 — My role

Senior consultant. I designed the headless WordPress architecture, built the React front end and set up an AI-assisted development process with linting, modularity and code review.

04 — Decisions

  1. A. Separate content from presentation

    WordPress stays as the content manager, and the front end is built in React and consumes that content through an API.

  2. B. AI-generated components, under strict rules

    AI-assisted component generation went through linting, modularity and code review before being integrated.

Fig. 1 — Generic component structure (states and scale). It does not reproduce the project interface.

05 — System

The outcome: LCP dropped from 4.2 s to 1.1 s with the headless architecture.

Next case — 03Chile Energy Hub · GovTech accessibility