Multi-site CMS: shared content and local rules
Publishing several retail sites from one CMS? Decide which content is shared, who can override it and how each site receives the approved policy version.
- Published
- Last updated
A multi-site CMS manages content for several websites while keeping each site’s rules and publishing permissions distinct. Share a record when the same approved fact applies everywhere. Keep a local record or explicit override when a store has a different returns rule, even if both stores use the same language.
Choose what the sites share
Decide whether the sites share content, layout or administration before choosing how to connect them. These choices produce different editing and recovery behaviour.
| Arrangement | What is shared | What a change affects |
|---|---|---|
| Shared content record | One source record referenced by several pages | Every destination that reads that record after publication and refresh |
| Reusable template | Page structure and presentation rules | Layouts using the changed template, even when their copy differs |
| Separate site instance | A distinct site with its own content and settings | That instance, unless an explicit integration copies changes elsewhere |
| Regional or language variant | A version selected for a market or language | Destinations that request that variant or use it as a fallback |
WordPress Multisite is a useful distinction. Its network administration guide says network sites don’t share content by default. Users need a role on a site to access it, while theme code changes affect every site using that theme. Shared administration alone doesn’t create shared policy records.
Contentful’s reference fields let entries reuse another entry’s content. Its documentation also identifies cross-space references as a Premium feature. Choose the supported relationship that fits your account and site structure. A copied paragraph becomes a separate maintenance responsibility unless a defined process keeps it updated.
Assign the content owner
Keep customer-facing guidance with the team responsible for its meaning. A shared CMS record can describe how a jacket’s fabric behaves. The product team owns that advice. Central marketing owns approved brand copy, with each brand’s differences recorded separately.
The commerce system remains the source for selling prices and available stock. A content editor must not create a second stock figure in a reusable paragraph. Use product data governance to assign ownership of changing catalogue facts.
The policy owner approves delivery and returns conditions for each store. Store the applicable brand and market with the policy, including its approved version. Keep order records and inventory movements in the commerce system, even when the CMS presents explanatory content beside them.
Set overrides and editorial authority
Define editable local fields and central approvals before giving local teams access. A local editor can change a store’s contact instructions without gaining permission to replace centrally approved eligibility conditions.
Use a field-level rule sheet for the content model. For each field, record its owner, allowed destinations, approval role and behaviour when a local value is absent. An override must name the shared field it replaces and why that exception exists.
In Contentful, locales are language-region pairs. Its publishing modes can publish all locales together or selected locales separately, with the mode set at environment level. A locale therefore needs an explicit publication decision. Brand identity and commercial policy need their own content relationships.
Work through two fictional stores
Consider two fictional Australian stores, Harbour Home and Ridge Outfitters. Harbour Home accepts eligible change-of-mind returns within 30 days. Ridge Outfitters uses a 14-day window. These invented policy examples illustrate content design, not legal advice or suggested policy terms.
Both stores can reference centrally approved instructions for finding an order number. Each has a separate eligibility record, approved by its own policy owner. A shared page template displays the correct eligibility record and the common instructions.
A local editor can change the store’s return-contact wording. Changing the return window requires policy approval. If Ridge Outfitters translates its page, the translation retains Ridge’s approved 14-day rule. The translator must not copy Harbour’s 30-day rule just because that text is available in the target language.
Set fallback behaviour separately for each kind of field. Shared brand-neutral guidance can fall back to an approved common value. A missing eligibility rule must block publication or omit the unsupported promise, according to the agreed design. It must not silently inherit another store’s conditions.
Before implementation, compare your required permissions with the selected CMS’s actual controls. Contentful’s roles documentation says custom roles require Premium. A model that depends on custom restrictions needs that supported capability or a different separation of sites. The CMS platform comparison covers the broader selection decision.
Publish to the right destinations
Treat a shared change as several delivery outcomes, with a result for each site and connected shopping-answer source. Publishing one shared record doesn’t prove that every destination has refreshed.
Continue the fictional two-store example. The central content lead approves version 4 of the shared order-number instructions. Ridge’s policy owner also approves a local return-contact change. The eligibility windows remain 30 days for Harbour and 14 days for Ridge.
- List the intended destinations. Record each site, brand, locale and referenced content version, plus any local override that must survive.
- Approve the shared instructions and Ridge’s local change through their assigned roles. Inspect referenced records and media before publication.
- Publish the required records and locales. Trigger each frontend’s normal build or refresh, then record whether it completed.
- Inspect each public page through its normal cache without editor access. Confirm the store’s identity, version 4 instructions and correct local contact wording.
- Check the connected shopping-answer source for each store. Confirm its source records, then ask a returns question whose answer distinguishes the two eligibility windows.
- Close each destination separately. Both stores must receive the shared instructions, while Ridge alone receives its local contact change.
If Harbour refreshes and Ridge’s build fails, record Harbour as delivered and Ridge as failed. Inspect Ridge’s publication input and build result before retrying that destination. Avoid republishing Harbour’s older content merely to make both status labels match.
If Ridge’s page is correct but its shopping answers show the old contact, check the answer-source refresh and site selection. Keep the incident open for that destination until the approved wording arrives. A successful CMS publication cannot resolve a failed downstream refresh.
Test isolation and recover an incorrect change
Test permissions with site-specific accounts and deliberately distinct draft content in an isolated environment. An editor’s restricted menu alone doesn’t demonstrate that preview links or content interfaces enforce the same boundary.
For the fictional stores, create a Harbour editor and a Ridge-only draft with a recognisable test phrase. Attempt each operation below with the Harbour account.
- Edit or publish Ridge’s policy record. The operation must be denied.
- Change Harbour’s centrally controlled eligibility field. The account must lack that authority even if it can edit local contact wording.
- Open Ridge’s restricted preview or request its draft through the content application programming interface (API). The restricted content must remain unavailable.
- Read the Harbour content the account is authorised to use. This must succeed, so a blanket access failure cannot masquerade as correct isolation.
Contentful documents separate delivery, preview and management APIs. The management API can retrieve unpublished content. Keep credentials with that authority out of public website code, and check each integration’s access independently from editor roles.
Recover the affected record and destinations
If a shared edit accidentally replaces Ridge’s 14-day rule with Harbour’s 30-day rule, identify the changed record and all destinations that consumed it. Preserve Ridge’s intentional contact override before restoring anything.
Compare the bad version with the last approved version. Contentful’s version controls support comparing published versions and selecting changes to restore. That doesn’t prove that referenced records, media or downstream websites have also been recovered.
Restore only the affected fields or record through the selected CMS’s supported procedure. Obtain policy approval, then republish the affected destinations and refresh their shopping-answer sources. If a shared record served both stores, check both even when only Ridge displayed the wrong rule.
Verify that Ridge again shows 14 days, Harbour still shows 30 days and Ridge keeps its approved contact change. Repeat the access checks after recovery. Recovery is complete when each destination presents its intended policy and the local editor still has only the authority assigned to that site.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.