Before your start, make sure to checkout the Technical Requirements and how to Install and enable the module. If you are unsure what Content Syndication is, you can learn more about it at Content Sync Use-Cases.


All connected sites must have roughly the same configuration for the entity types you want to share. Roughly means that if an entity type or bundle doesn't exist on target site, these entities won't be created and if a field that's required on the target site is not provided by the source site, that content won't be added to the target site to avoid broken content.


In the following steps we assume that all sites have our module installed and are registered.


Scenario

Umami is a leading food portal with a global presence that's focusing on target audiences from North America and Europe. They manage a global brand site and tens of satellite sites in each individual country they are focusing on. They also manage hundreds of small sites that are focusing on specific demographics like their veggie brand Green Beans that are operating in individual country sides where the target demographic has a strong presence.


Sites

  • umami.com
  • umami.us, umami.de, ...
  • greenbeans.de, greenbeans.us, ...
  • (other brand sites)


Objectives

Content Entry

Umami wants to centrally manage their taxonomies and menu items to be published to the country sites from the central umami.com site. The editorial process is simplified as all publishing activity is centralized. Centrally publishing, updating, unpublishing and removing core elements of the site structure makes content governance simple and effective.


Consistent Taxonomies & Navigation

All connected sites automatically receive any changes in taxonomies and the menu structure to ensure visitors are presented with consistent navigation and categories, streamlining the user experience.


Pools

To meaningfully group content for different workflows and scenarios, we are creating the following Pools (repositories):

  • Metainformation


Configure umami.com to share metainformation

Push Metainformation

Navigate to Web Services > Content Sync > Flows to create a new Flow. The first screen should look like this:


Settings:

  • Name: Push Metainformation
  • Type: Push
  • Pools: Metainformation
  • Pool Assignment: Assign All
  • Push: Immediately
    • This ensures that the taxonomies and menu items are shared immediately with all other sites whenever they are changed, including from import scripts etc.


Step 2: Define types to include


Settings:

  • Menu link content and Taxonomy terms are in the left column, so whenever they are created, updated or deleted, they are sent immediately to the other sites.
  • Everything else is in the right column and ignored by this Flow.


Continue to step 3 to review your configuration and submit.



Configure all other sites to receive Metainformation

Pull Metainformation

Navigate to Web Services > Content Sync > Flows to create a new Flow. The first screen should look like this:


Settings:

  • Name: Pull Metainformation
  • Type: Pull content
  • Pools: Metainformation
  • Pull new content: Immediately
  • Pull updates: Forbid updates
    • This ensures that taxonomies and navigation stays consistent across all sites.


Step 2: Define types to include

This mirrors the settings from your pushing site:


Continue to step 3 to review your configuration and submit.