Content Hub
Common syndication models
Content that is syndicated by Content Hub starts on a Drupal site. Any Drupal site can become a Content Hub publisher by enabling and configuring the acquia_contenthub_publisher module.
Publishers create content on their sites. This content is automatically queued for export to the Content Hub service. Dependencies of the content are calculated and exported so that the Content Hub service has everything it needs to syndicate the full entity to subscribers.
Any Drupal site can become a Content Hub subscriber by enabling and configuring the acquia_contenthub_subscriber module.
Subscribers import content from the Content Hub service, along with all dependencies of that content. When content is changed on the publisher and is exported to the Content Hub service, subscribers automatically pull the updates.
The following are the ways for sites to subscribe to content:
Individual content entities and their dependencies can be manually imported into one or more subscribers by using the Publisher’s Dashboard. After the manual import, a content entity is subscribed to all subsequent updates to that content and its dependencies.
Administrators can configure filters using the Publisher’s Dashboard to enable automatic import of content into subscribers. Filters can use facets to determine the content that must be sent to the designated subscribers, including taxonomy terms, content type, and the publisher from which it is originated.
Any Drupal site can become a publisher or a subscriber by enabling the appropriate module. Enabling both modules can turn a Drupal site into both a publisher and a subscriber. This flexibility allows for a variety of syndication models.
The following syndication models are commonly used with Content Hub:
This is the simplest and recommended model for syndication with Content Hub.
This model involves a single Drupal site that acts as the Content Hub publisher. All content from the publisher is exported to the Content Hub service, and is made available to subscribers.
The publisher must be publicly accessible to all subscribers.
Content is imported into subscribers using a manual or automatic import. To configure an automatic import, administrators set up filters with facets that leverage taxonomies or content types to automatically import content into specific subscribers.
The advantage of this syndication model is that the network of Content Hub sites has only a single source of truth. The content and configuration of the entities on the publisher is what is syndicated to subscribers. Everything that is in the Content Hub service comes from a single source that controls what content is syndicated with filters and manual import.
This is a complex model for syndication with Content Hub.
This model involves multiple Drupal sites acting as Content Hub publishers. All content from these publishers is exported to the Content Hub service, and is made available to subscribers.
Content is imported into subscribers using a manual or automatic import. To configure an automatic import, administrators set up filters with facets that leverage taxonomies or content types to automatically import content into specific subscribers.
The advantage of this syndication model is that a single Content Hub service can provide syndication for a network of heterogeneous Drupal sites. For example, one publisher can have a set of content types configured with fields and other dependencies that allow for a certain kind of content to be syndicated, such as a product detail page with file attachments. Another publisher can be marketing-focused and can syndicate blog content or press releases. Each publisher can be owned by a different team within the same organization, with their own workflow rules and a pool of content authors. Any subscriber in the network can import the relevant content from either of the publishers.
The disadvantage of this model is that the network of Content Hub sites does not have a single source of truth. This model requires more planning and governance to maintain and avoid situations such as circular dependencies.
When designing a Content Hub network consisting of multiple publishers, only the original publisher can make updates to its entities. Publishers cannot export changes to the entities that are originally authored by other publishers.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Content Hub