Learning@Sitecore

Embracing the Future: Sitecore AI – What It Means for Digital Experience Artificial intelligence is no longer the future; it’s the present — and with SitecoreAI , the landscape of digital experience is shifting dramatically. Sitecore says, One Platform. Unlimited possibilities. At its core, SitecoreAI is a unified, cloud-native platform that brings together content management, customer data, personalization, search, and AI-powered workflows in a single system. It provides a centralized workspace called Agentic Studio , where marketers and AI collaborate seamlessly. Users can also design their own custom agents and workflows, all without writing code. In this post, I’ll break down what SitecoreAI is, why it’s a big deal, how it works, and what it means for marketers, developers, and businesses. Why SitecoreAI Matters 1. Efficiency Through Automation Instead of juggling multiple tools — CMS, personalization engines, analytics dashboards — teams now have a single platform. SitecoreAI’s ...

In real time scenario, when you are working on projects, sometime for testing purpose you might have to perform some actions on the guest profile in Sitecore XM Cloud stored in CDP. In this case, I have found the Engage API becomes very useful to add/update or manage the CDP guest profile using the REST APIs. Example: Suppose you are working on some Decision Model which need to return some offer based on some Guest Extension Properties. But in order to put the values under the extension properties you might have to build a complete form to push the values into CDP. Rather going that path, it would be easier to push the Guest and their properties using Engage API and running the test on Decision Model on the same guest, showing the results and lowering the dependency on other teams. In this blog, I will show how you can setup the APIs quickly using Postman and run the GUEST REST API using it.   Setup API Access Key Token Before we proceed further you need to create a C...

While working on real-world Sitecore projects, there are many scenarios where you need to fetch global content values that are reused across the entire site. Although we can retrieve item field values from data source items inside components in Next.js, there are times when we need to fetch content directly from the Sitecore CMS rather than through a component’s data source. One of the most recommended approaches for this requirement is to execute GraphQL queries which use the Sitecore Edge API under the hood and return data in a strongly-typed schema. In this blog, I will explain how to configure and execute GraphQL queries in a Next.js application using the Sitecore Content SDK . About Sitecore ContentSDK Sitecore XM Cloud brings a headless, API-first approach to content delivery. While GraphQL queries can be executed directly through Edge endpoints, Sitecore has introduced the Sitecore Content SDK to make this development experience even easier. The Sitecore Content SDK is a l...

If you have worked in Sitecore, then one of the most common term which is being used is called Placeholder keys. They are like the specific area kept reserved in the html structure where you can bind more component. These specific areas are given a name which us being used as key name, see the below example: <div class=”main-content”>               <Placeholder name="placeholder-key-1"…. </div> In XM Cloud, if you are using NextJs as your frontend framework, then adding a placeholder key requires some configurations. I will discuss the steps required and configuration required. Approaches As far I know, there could be three approaches one can follow to bind the components on layout. First approach is stacking the components to same placeholder key available at layout.tsx in NextJs app. The problem with this approach is that it restricts flexibility, reusability, and scalability in case o...

Language fallback is a powerful feature provide by Sitecore, that allows showing the content in the set fallback language if the content is not found in current language. Example, if you have setup your site in 2 languages in which English will be the default and other as Arabic, with Language fallback settings are enabled, if content for Arabic language is not created and accessed then English language content will be use instead. According to me, the best feature it offers is that it lowers down the risk of showing 404 Page not found error if any page content is not available in secondary language due to any reason. In this blog, I would show you how you can enable these settings in XM Cloud CMS along with creating the patch and show you how it works. In case if you are seeking any documentation on How to add additional Language in your XM Cloud site, then you can follow this blog . Types You can setup Language fallback setting in 2 ways: On Item Level I recommend usi...