Dynamic Page Builder

overview

A content team needed more flexibility in how they published stories. The existing CMS forced every article — regardless of format — into the same rigid template. Photo essays and breaking news posts looked identical. Anything outside the template meant filing a request and waiting on a developer.

the problem

the solution

I was one of three frontend engineers on this, alongside a full-stack and a backend developer — each of us owning a slice of a shared component library that editors could mix and match to build their own layouts. My pieces were a photo and video carousel, a four-item media grid, and a scroll-triggered typewriter effect that types text in as the reader scrolls to it, plus a handful of simpler primitives like buttons. Every component followed the same prop/emit contract, so from an editor's side, blocks built by three different developers behaved like one consistent system.

outcomes & impact

tech stack