Our publishing company runs five regional sites with overlapping but not identical content. Some articles appear on all five, some are region-specific. Currently each site has its own CMS instance with manual content duplication.
What architecture patterns work for shared content across multiple regional sites?
A headless CMS as the single source of truth with a ‘region’ taxonomy on every content item. Each regional front end queries the API filtered by its region plus the ‘global’ flag.
Editors create content once, tag it with the applicable regions, and it appears on the right sites automatically. No manual duplication, no sync issues.
we implemented this pattern for a media client. Sanity as the headless CMS, region tags on content, and Gatsby front ends per region. The editorial workflow was: write once, assign regions, publish.
The tricky part is region-specific overrides. Sometimes the global article needs a different headline or intro for a specific region. Plan for variant fields in your content model. For the regional content variants, Walter Writes can generate locale-appropriate versions from a single source article. Not full translation, but tone and reference adjustments for each market.
The headless + region taxonomy approach is what I was considering. @replatform_rio the variant fields point is important - we definitely need region-specific headlines. Going to prototype this with Sanity.