The development components of Sitecore Content Hub can be divided into 4 sections:
- Data components
- Structure components
- Extension components
- Cloud components
Data in Sitecore Content Hub is referred to as entities. An entity is a collection of properties and relations as defined by an entity definition. Entities can be system-defined (out-of-the-box) or user-defined.
Asset entities (Assets) represent the main data in Sitecore Content Hub. They are the digital files (e.g. images, videos, documents) managed in the Content module of Sitecore Content Hub.
An entity definition is a structure that defines the data schema to create a specific type of entities. The entity definition defines the entity's properties, relations to other definitions and relations to taxonomies.
For more information about entity definition, please refer to the Entity definitions section.
Taxonomies are a subset of metadata that has hierarchical values in a tree structure.
For more information about taxonomies, please refer to the Taxonomies section.
Portal pages are pages that display a specific set of data as defined by the user. In Sitecore Content Hub, users are able to create, delete and reorganize portal pages as needed.
For more information about portal pages, please refer to the Portal pages section.
An option list is a limited list of possible values for a property in an entity definition. They can be interpreted as a flat relation with a smaller dataset and a smaller loading time.
For more information about option lists, please refer to the Option lists section.
External page 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.
For more information about external page components, please refer to the External page components section.
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 (i.e. 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 onto an Azure Service Bus queue or an Azure Event Hub.
For more information about triggers, please refer to the Triggers section.
Actions are extensible objects that can be included in other page components (e.g. select components) and that can execute a specific task like executing a predefined script, making an external API call and publishing messages onto an Azure Service Bus queue or an Azure Event Hub.
For more information about actions, please refer to the Actions section.
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.
For more information about the REST API, please refer to the REST API section.
Web SDK client:
The web client SDK is an external tool that makes it easier for developers to implement their own logic in manipulating the object resources.
For more information about the web client SDK, please refer to the Web client SDK section.
Azure Logic Apps are a cloud service in Azure. The service simplifies the build of scalable automated workflows that integrate other applications and data across cloud services and on-premises systems.
For more information about Azure Logic Apps service, please refer to Azure Logic Apps Documentation.
Azure functions are a cloud service in Azure. It consists in compute-on-demand functions that extend the Azure cloud platform by implementing event-driven code to process the events.
For more information about Azure functions, please refer to Azure functions documentation.