Flows: Configure how to distribute content

All of your sites that you connect to Content Sync can act as publishers and subscribers meaning you can push content from your site into your central content repository and you can pull content from that repository into your sites. Content Sync doesn’t force you to follow any specific approach on what content to push and what content to pull- in fact there are many options available so you can customize Content Sync to work exactly the way you want it to, for example to configure what bundles (like a Page or a News Article) you want to syndicate or not syndicate per site.

Each Flow is either used to publish content or to subscribe to content but you can create as many Flows per site as you like, meaning you can also have sites that both publish their content and subscribe to content from other sites.

Content Sync doesn’t work just with content -or nodes as Drupal calls them- we support a wide range of standard and contributed entity types like files, media elements, taxonomy terms, paragraphs, bricks, webforms and so on. There’s a full list of contributed modules we support in the technical documentation section if you’re interested.

Content Sync works 100% with standard Drupal elements meaning that any distributed content works exactly the same on all sites- it will display the same way and integrate the same way with lists from views and other Drupal elements. This means Content Sync will distribute embedded elements like paragraphs or bricks automatically along with the actual content- by default it will also syndicate taxonomy terms like tags and media elements like images along with the content you publish.

If you just want to get an overview of how Content Sync works, we recommend you continue with the other articles in this section:

If you are interested in all the details of what you can configure with Flows, we have provided a list of all options below: