Sitecore Content Hub
Content Hub content management and content operations
Introduction
Sitecore Content Hub™ offers multiple modules. Here is a brief overview of these modules and their features.
Sitecore Experience Edge™ for Content Hub
Manage and publish your content for multiple functions and audiences using numerous devices.
Sitecore DAM™
Centralize and categorize photos, layouts, artwork, video, 3D, source files, and more.
Sitecore PCM™
Manage access, real-time update and publication of your product-related content across channels.
Sitecore CMP™
Plan, manage and collaborate effectively on your content strategies.
Sitecore MRM™
Plan and schedule complex, multi-layered marketing activities.
Sitecore Web-to-Print™
Create and control central customizable templates.
Getting Started
User Documentation
Developer Documentation
SDKs/ Tools for integration
The following tools allow users to integrate Sitecore Content Hub with external systems.
| Tool | Description |
|---|---|
| Triggers | Triggers are a push mechanism in Sitecore Content Hub that executes certain actions if certain conditions are met after specific events occur. Triggers are defined by a set of triggering events (Objectives), a set of conditions, and a set of actions. Triggers can be used as a push mechanism towards external systems by making API calls (e.g. invoke an Azure Function) or by publishing messages to an Azure Service Bus queue or an Azure Event Hub. |
| Actions | Actions are extensible objects that can be included in other page components (e.g. selection component) and that can execute a specific task like running a predefined script, making an external API call and publishing messages to an Azure Service Bus queue or an Azure Event Hub. |
| Scripts | Sitecore Content Hub allows users to integrate custom scripts in their business logic. Scripts can be manually triggered by end-users or automatically triggered by the application (e.g. using Triggers) depending on the script type and the use case. Sitecore Content Hub offers different script types, with each type having different context properties. |
| CLI | A command-line interface (CLI) processes commands to a computer program in the form of lines of text. The program which handles the interface is called a command-line interpreter or command-line processor. The CLI is used for communicating with Sitecore Content Hub™ instances through the REST API using the C# Web SDK. |
| Import/Export | Sitecore Content Hub offers an import/export package feature that allows users to migrate their structural changes between different instances of Sitecore Content Hub. |
| External components | External page components are extensible components that can be integrated into portal pages. They allow the integration of external libraries within Sitecore Content Hub pages. External components contain a code section that gets executed when the component is initialized, as well as a template section that contains an HTML markup that gets injected in the DOM when the component is initialized. |
| C# Web SDK | The C# Web SDK is an external tool that makes it easier for C# developers to implement their own logic in manipulating the object resources. |
| JavaScript SDK | The JavaScript SDK is an external tool that makes it easier for JavaScript developers to implement their own logic in manipulating the object resources. |
| REST API | The REST API of Sitecore Content Hub is a Hypermedia API built on top of HTTP where all objects are modeled as resources. Each resource represents the state of the object at the time of the request. Standard HTTP requests and responses are used to query and manipulate the state of the objects. |
Learn more about Sitecore Content Hub
See all videosOpens in a new tabSitecore Content Hub SSO Authentication with OKTA
Sitecore Personalize: Advanced Decisioning with Content Hub for an E-commerce Use Case
Demo - Using Sitecore Content Hub for video reviews
Questions from the community
See allOpens in a new tabby Yatish Kumar Published 5/10/2023
1 comments
74 views