Value Research Learn Platform

The content team at Value Research needed to publish and update pages without raising a ticket and waiting on a new deployment. Every layout change, every new page went through engineering. That needed to stop.

The solution was a headless CMS connected to the existing Next.js app. I worked out the initial data flow: how content is structured in Strapi, how it maps to components in Next.js, and how pages are generated dynamically from a single entry point. There wasn’t an existing pattern to follow internally, so a lot of it came from research and trial and error.

The key constraint was developer experience. Developers writing components should not need to think about routing, layout wiring, or page structure. They write a component, the CMS handles everything above it. I directed that initial contract and kept refining it as the team built on top and the requirements evolved.

The result: content editors publish pages independently. Developers write standalone components. The pipeline between them runs without manual intervention.