Using Site Studio with Acquia Content Hub

Using Site Studio with Acquia Content Hub

The Site Studio Content Hub module is a wrapper module and must not be enabled. This module is hidden from the module list in the Drupal UI. Enabling it provides no additional features to the site. Instead, enable one or both submodules: sitestudio_contenthub_publisher or sitestudio_contenthub_subscriber. These submodules are used in the same way as Content Hub submodules for publishing and subscribing, contenthub_publisher and contenthub_subscriber respectively.

Setup for Publisher sites

If a website with Site Studio must publish content through Acquia Content Hub as a publisher site, enable Site Studio Content Hub Publisher.

To enable the submodule after the download of Site Studio Content Hub is complete:

1. Access the Drupal UI and navigate to the Extend menu.

2. Alternatively, run the drush pm-enable sitestudio_contenthub_publisher -y Drush command.

Setup for Subscriber sites

If a website with Site Studio must receive content as a subscriber site from Acquia Content Hub, enable the Site Studio Content Hub Subscriber module.

To enable the submodule after the download of Site Studio Content Hub is complete:

1. Access the Drupal UI and navigate to the Extend menu.

2. Alternatively, run the drush pm-enable sitestudio_contenthub_subscriber -y Drush command.

Setup for dual-role sites

If a website must function as both a publisher and a subscriber, enable both submodules.After the download of Site Studio Content Hub is complete:

1. Enable the submodules through the Extend menu in the Drupal UI.
2. Alternatively, run the drush pm-enable sitestudio_contenthub_publisher -y drush pm-enable sitestudio_contenthub_subscriber -y Drush commands.

Using Content Hub with Site Studio

Review the following features for content syndication with Site Studio:

• Default module behavior: The new Site Studio Content Hub module prevents the publication of Site Studio configuration entities through Acquia Content Hub. This design ensures the publisher site theme does not override the subscriber site theme.
• Required configuration entities: The subscriber site must have the required configuration entities before you publish content entities built with Site Studio. This requirement applies to Components, Base Styles, Custom Styles, Templates, Style Guide and Style Guide Manager settings.
• Machine names and UUIDs: Configuration entities must use the same machine names and UUIDs for syndication to function correctly.
• Component dependencies: While you syndicate a page that uses Site Studio components, ensure the subscriber website has the component configuration and all dependencies. For example, if a component includes a color picker field, then the subscriber site must have the same color variables as the publisher site. In case of mismatch, a color selected on the publisher may not appear on the subscriber site. This results in the element too being invisible where the field was applied.
• Layout Canvas storage: Content within components is in a single Layout Canvas field. When a publisher updates a page, the entire Layout Canvas content is replaced on the subscriber site.
• Package synchronization: To ensure the subscriber site possesses what it needs, export a package from the publisher site and import it into the subscriber site. This ensures that the Publisher and Subscriber sites use the same Site Studio configuration entities.
• Rebuild limitations: Rebuilding Site Studio configuration entities does not add them to the publisher site export queue.
• Entity references: Content entity references in the Layout Canvas on a published content entity are in the dependency list.
• Automatic updates: If a subscriber site has the Site Studio Content Hub Subscriber submodule enabled, the system updates entity references in Layout Canvas fields to the relevant entity IDs during import.

The Site Studio Content Hub module is a wrapper module and must not be enabled. This module is hidden from the module list in the Drupal UI. Enabling it provides no additional features to the site. Instead, enable one or both submodules: sitestudio_contenthub_publisher or sitestudio_contenthub_subscriber. These submodules are used in the same way as Content Hub submodules for publishing and subscribing, contenthub_publisher and contenthub_subscriber respectively.

Setup for Publisher sites

If a website with Site Studio must publish content through Acquia Content Hub as a publisher site, enable Site Studio Content Hub Publisher.

To enable the submodule after the download of Site Studio Content Hub is complete:

1. Access the Drupal UI and navigate to the Extend menu.

2. Alternatively, run the drush pm-enable sitestudio_contenthub_publisher -y Drush command.

Setup for Subscriber sites

If a website with Site Studio must receive content as a subscriber site from Acquia Content Hub, enable the Site Studio Content Hub Subscriber module.

To enable the submodule after the download of Site Studio Content Hub is complete:

1. Access the Drupal UI and navigate to the Extend menu.

2. Alternatively, run the drush pm-enable sitestudio_contenthub_subscriber -y Drush command.

Setup for dual-role sites

If a website must function as both a publisher and a subscriber, enable both submodules.After the download of Site Studio Content Hub is complete:

1. Enable the submodules through the Extend menu in the Drupal UI.
2. Alternatively, run the drush pm-enable sitestudio_contenthub_publisher -y drush pm-enable sitestudio_contenthub_subscriber -y Drush commands.

Using Content Hub with Site Studio

Review the following features for content syndication with Site Studio:

• Default module behavior: The new Site Studio Content Hub module prevents the publication of Site Studio configuration entities through Acquia Content Hub. This design ensures the publisher site theme does not override the subscriber site theme.
• Required configuration entities: The subscriber site must have the required configuration entities before you publish content entities built with Site Studio. This requirement applies to Components, Base Styles, Custom Styles, Templates, Style Guide and Style Guide Manager settings.
• Machine names and UUIDs: Configuration entities must use the same machine names and UUIDs for syndication to function correctly.
• Component dependencies: While you syndicate a page that uses Site Studio components, ensure the subscriber website has the component configuration and all dependencies. For example, if a component includes a color picker field, then the subscriber site must have the same color variables as the publisher site. In case of mismatch, a color selected on the publisher may not appear on the subscriber site. This results in the element too being invisible where the field was applied.
• Layout Canvas storage: Content within components is in a single Layout Canvas field. When a publisher updates a page, the entire Layout Canvas content is replaced on the subscriber site.
• Package synchronization: To ensure the subscriber site possesses what it needs, export a package from the publisher site and import it into the subscriber site. This ensures that the Publisher and Subscriber sites use the same Site Studio configuration entities.
• Rebuild limitations: Rebuilding Site Studio configuration entities does not add them to the publisher site export queue.
• Entity references: Content entity references in the Layout Canvas on a published content entity are in the dependency list.
• Automatic updates: If a subscriber site has the Site Studio Content Hub Subscriber submodule enabled, the system updates entity references in Layout Canvas fields to the relevant entity IDs during import.