Everyone knows that there is a push from Sitecore for users to move to its cloud-based version. However, Sitecore XP is still there and, considering Sitecore lifecycle support table, will still be available and supported for a long time.
Product | Initial Release Date | Mainstream Support End Date | Extended Support End Date | Sustaining Support End Date |
---|---|---|---|---|
Sitecore 10.2 | Nov 2021 | 31-Dec-2024 | 31-Dec-2027 | 31-Dec-2029 |
Sitecore 10.3 XM and XP came this December bringing some new features and improvements to the platform. In this article, we will cover some of the key elements brought with this new version.
Sitecore now allows us to use GraphQL API calls to perform authoring and management commands which were only before available using its user interface. A walkthrough to enable this API is provided in the Sitecore documentation. Not quite simple though, as it involves creating and build a MVC client application.
This is a very useful feature as it enables Sitecore to send to a third-party system information about items and workflow events.
The supported events are:
Event Name | Description |
---|---|
|
Raised when a new item from a template is added. |
|
Raised when a new version is added to the item. |
|
Raised when a new cloned item is added. |
|
Raised when the item is deleted. |
|
Raised before deleting the item. |
|
Raised when a version of the item is removed. |
|
Raised when the item is locked. |
|
Raised when the item is unlocked. |
|
Raised when at least one change is saved in the item. This event can occur multiple times during simple item operations on the UI. |
|
Raised when the item is copied. |
|
Raised when the item is moved to another parent. |
|
Raised when the item renamed. |
|
Raised when the sort order of the item changes. |
|
Raised when the item's template changes. |
|
Raised when the publishing of the item starts. |
|
Raised when the publishing of the item ends. |
|
Raised when the publishing of the item fails. |
|
Raised when the status of item publishing updates. |
Other than the table above, webhooks can be configured to be triggered on workflow state changes and configured to have validation being performed by third party systems. Using this an item will only be moved to the subsequent state if that external validation allows it for.
Using Sitecore Headless Services and the Layout Service, this new feature allows us to embed Sitecore form in any page, even non-Sitecore pages. This is done using Lit and Tailwind CSS framework. As described in the Sitecore documentation “Lit it is a lightweight library to quick-start development of web components with a declarative templating system, scoped styles, and state management.”, and “Tailwind CSS is a CSS framework with a comprehensive set of highly reusable CSS classes. This minimizes the amount of custom CSS that you must define. It can scan source codes and trim unnecessary CSS class definitions, to achieve the smallest possible final CSS stylesheet for production use.
A tool to export contact and interaction data from xDB to files, allowing for easy storage backup and sharing and use on external reporting systems.
Other features added and improvements made to Sitecore 10.3 include:
Beyond these features the following areas also had improvements we will cover in subsequent posts:
If you are not sure about whether you should upgrade to the newest version of XP or go with Sitecore XM Cloud, Sitecore’s recommendation is:
Sitecore 10.3 brings more power and flexibility specially for headless front-end development using SXA and JS based frameworks. The decision to upgrade, of course, should be taken considering all aspects from both sides, a technical and a business perspective. Staying ahead of competition by leveraging modern ways to integrate with external systems and delivering a state of art experience to your digital content consumers is definitely a good reason to look into Sitecore 10.3.
Thanks for reading!
Sign up to our bi-weekly newsletter for a bite-sized curation of valuable insight from the Sitecore community.