Shared Components allow you to create and share a single component throughout a site. Any changes to the source component are reflected wherever it is used.
This guide requires a user with at least a Restricted or Group Editor role. If you do not have these permisions, you will NOT be able to preform the necessary tasks.
Quick Start Overview
- Create a new "Shared Component." (Content → Add content → Shared Component)
- Add components and content.
- Save and publish your shared component.
- Once published, add it to any page using the "Shared Component Container" component.
- Publish the page through the moderation workflow.
Once placed, only the shared components will need to be republished to update all placements where it used.
Detailed Usage
There are two elements used in creating Shared Components.
The first is creating the content to be shared. This is managed as a "Shared Component" content type that lets users create and publish components. A subset of the same components used throughout the site is available and should be familiar to you.
The second part is placing the shared component on other pages. This is facilitated through the same component architecture used to create most other content on the site.
Creating a Shared Component
- Create a component to share:
Content → Add content → Shared Component - Add a components and content to share.
More about working with components. - Once ready, submit for review and publication.
More about content moderation - Once published, you can place a shared component in a page.
Placing a Shared Component
- Once the source component is published, go to any pages where the shared component will be placed.
- Use the "Shared Component Container" component on the destination page.
- Browse and select your shared component.
You can filter by the title or the description to help narrow the listed components. - Review and publish or submit for review when ready.
Things to note
- Shared components are available site-wide regardless of the group or owner. This was done to facilitate the sharing of components across groups or sections. For example, suppose a center wants to cross-promote an event with related departments or partner centers. In that case, the center can create a shared event component, which can be placed on the department pages while maintaining ownership and editing access to that shared component.
- One exception is shared components created within private groups. These are not visible when placed outside of that group to users without access to that group.
- Shared component display can be enabled or disabled through the source component once published. This allows you to show/hide ALL placements of the component at once
As always, if you have any questions please submit a ticket.