In this year special Sitecore Symposium there were a lot for new stuff and news around Sitecore Content Hub, a lot has been shared through the road map keynote by Desta Price, EVP Product Management at Sitecore and Tom De Ridder, Chief Technology Officer at Sitecore, starting from Content insights, Content Coverage until the new Content as a Service (CaaS) offering that is coming in the early 2021, also some new news about the CMP connector that has been recently release and the new versions on the roadmap, want to know more about these, keep reading!
What is the problem? what is the Solution?
As a start, we all should understand the problem and the solution around content and content hub, so I'll summarize quickly the problem and solution based on a couple of sessions I attended at Sitecore Symposium 2020, its all start with the Content Crisis problem, caused by a disparate Systems across dozens of business unit, content scattered across multiple siloed systems Content Management Lacked of control Duplicate Content, digitals rights management (DRM) over content issues, complex multichannel, multi-brand requirements and associated governance, systems used are legacy and disconnected which leads into inconsistent customer experience across different digital channels, or Inflexible Content data Modal, at this point Content hub raise to be the solution for all of these issues, but How? :
- Single, centralized content repository.
- Auditability and traceability across all content and assets, in addition to the technical capabilities to integrate with different solution.
- Deliver best value and fastest time to market.
- You can used (Digital Asset Management (DAM), Product Content Management (PCM), Digitals rights management (DRM), Marketing Resource Management (MRM) in a single unified platform.
- Integrations with other business application like salesforce.
- Fetch data for rendering page HTML in response to a page load request
- Fetch data to dynamically change sections of a page with AJAX
- CaaS serves is a truly headless, highly scalable offering. It does not have the same DXP and WYSIWYG page authoring functionalities that XP has.
- XP provides full DXP and CMS capabilities, provides experience optimization and personalization. Sitecore Headless SDKs (JavaScript SDK or ASP.NET Core SDK) can be used to achieve a “hybrid headless” solution with XP.
- XM keeps business users in control of presentation through Horizon and Experience Editor.
- CaaS allows business users to manage content, but developers build the presentation in the apps that consume the delivery API.
- The connector needs 3 places to be configured:
- Azure Service Bus
- Content Hub
- Sitecore Content Management
- When changes made in CH (entity creation, modification, deletion), using a trigger and action, changes will be messaged to the Service bus where the app is listening. The app will get the targeted entities from CH and write it into Sitecore, data like where used messaged will be shared by back to CH.
- Fault tolerant for sync, retry 3 times to complete the sync after entity failure
- Support all simple field types (support all non-complex field mappings between CH entity and sitecore items),
- Sync of tags (Sync Taxonomy values from CH as tags to the corresponding items in Sitecore).
- Introduce related Entities, bring an entity and maintain the relationships from CH to Sitecore.
- Enhanced DAM & media link support, attachments asset from CMP to public in sitecore, images can be pushed from CMP to XP if they are part of rich text, content piece as pdf.
- The content in CMP is written to target certain personas which will map to profile cards in XP that will allow us to infer the interests about a contact based on the content they are browsing
- Knowing where and how content is being used which allowed editors/authors to make the right changes to the content.
- Support of item versioning from the changes originated in CMP
- Support Item workflow from changes originated in CMP
No comments:
Post a Comment