For years the default was a single platform that stored the words and drew the pages. It was convenient until a studio wanted its stories to appear in an app, a newsletter and a partner's site at the same time.
Content first, presentation second
The alternative is a content system that only manages structured stories and hands them to whatever needs them. Editors keep a familiar writing interface; developers get clean data.
Separating content from presentation is an editorial decision as much as a technical one.
The trade-off is operational. Someone has to decide how quickly a published change reaches readers, and what happens when one part of the system is unavailable.
Studios weighing this change often start with the editorial basics.
Related reading: Headless publishing, explained for editors.
