# Why we rebuilt our content layer on Contentful

A six-week migration from a legacy CMS, and what we'd do differently next time.

![Abstract code on dark background](https://images.ctfassets.net/vn734mok6jmo/seed-blog-1/6b990367b6509bd475036f2077031ce1/seed-blog-1.jpg)

When we started Roboto in late 2024, we inherited a legacy WordPress install that had grown into a content monolith. Editors loved the WYSIWYG, but every release required a cache stampede and a prayer.

Contentful's content-as-data model gave us strict schemas, an API that's a joy to consume, and a Live Preview SDK that finally closed the editor feedback loop. Six weeks later we'd migrated every entry and retired the old stack.

The biggest unlock wasn't speed — it was confidence. Editors can now ship copy at 5pm on a Friday without paging the on-call.

**READ MORE**

## Get articles like this in your inbox

Engineering essays on content platforms, React, and the modern web. One email a month.