Skip to content
CMS

Broadsheet: Headless CMS for a media group

A shared headless publishing platform that lets each title keep its identity without duplicating content or code.

Start a similar project
Sector
Media
Typical client
Publisher running several regional brands
Typical timeline
18 weeks
Typical team
4 engineers, 1 designer
Structured story editor with content tree, publishing controls and brand targets
Editorial queue tracking drafts, review stages and scheduled publishing
Audience reporting across brands, returning readers and subscription starts

About this project

Regional publishers often run each title on its own ageing website. Journalists duplicate work, developers maintain several codebases and a small improvement has to be made many times.

A headless CMS gives every brand a shared editorial workflow and a shared component library. Editors publish to one or many titles from the same screen, without losing each title's identity.

Objectives

  • Bring several titles onto one publishing platform
  • Let editors publish without developer involvement
  • Migrate the archive without losing search traffic

What’s delivered

  • Structured content model and block library
  • Draft, preview, approval and scheduling workflows
  • Next.js front ends sharing a design system
  • Scripted archive migration and redirect mapping

Target outcomes

<5 min

story-to-published goal

90+

Lighthouse performance

100%

URLs redirected

1

platform for all titles

Technology

  • Payload
  • Next.js
  • PostgreSQL
  • Algolia
  • Cloudflare

Services involved

More work like this

Have a similar challenge?

Book a free consultation. We’ll scope your project, pressure-test the plan and give you an honest estimate, with no commitment required.

Start your projecthello@vantorel.org