CONCEPT Cited by 1 source
Content management as platform¶
Definition¶
Content management as platform is the architectural stance that editorial content management is a platform capability owned by a platform-engineering team — not a per-campaign or per-page engineering project shipped by the product team that happens to need a page this week.
In this stance, the platform exposes:
- A content model (entry types, validation, reference relationships) that authors compose pages from.
- An authoring UI so non-technical stakeholders can create, localise, review, and publish content without engineering involvement.
- A delivery runtime that renders the authored content inside the company's regular product surfaces (web, app, email) with the platform's usual observability, A/B testing, performance gates, and design-system integration.
- A contribution model (concepts/inner-sourcing) for other teams to extend the platform with new content types or new authoring affordances.
What the stance displaces¶
- Per-campaign engineering projects — each awareness campaign or category-inspiration page requiring a ticket, a branch, a PR, and a deploy.
- Hand-coded static pages checked into the codebase alongside application code, shipped through the engineering release train, and edited by engineers on behalf of copywriters.
- Per-surface upload flows — the same content uploaded separately to web and app, with inevitable drift (Source: sources/2022-09-28-zalando-more-editorial-content-please).
The empirical Zalando numbers the stance produces: page time-to-go-live 2 days → 4 hours, 2-week lead time removed, +82% YoY page publication volume, non-technical stakeholders owning the end-to-end flow.
Load-bearing property: engineers out of the hot path¶
The stance's architectural thesis is that when the authoring workflow is the bottleneck, the winning optimisation is moving engineers out of the hot path — not speeding up the backend. A faster engineering team that still sits between the copywriter and the published page does not remove the 2-week lead time; a drag-and-drop authoring UI that the copywriter operates directly does.
Engineers remain in the loop for one-time costs: introducing a new content-type (a new module, a new renderer). Post-introduction, that content-type is usable indefinitely without further engineering involvement.
Canonical wiki instance¶
Zalando's Landing Pages stack on Contentful + Interface Framework + inner sourcing (Source: sources/2022-09-28-zalando-more-editorial-content-please).