Koushik Mukherjee - Sitecore MVP

  In my previous blog post on the Sitecore XM Cloud Content SDK, I discussed how you can install and start working with the Content SDK. In this blog, I'll focus on the differences between the JSS SDK and the Content SDK, along with some of the new concepts introduced in the Content SDK. Comparison with JSS SDK 1. Reduced Folder Size and Complexity The Content SDK removes functionality not strictly required for XM Cloud, leading to smaller, less complex starter applications that are inherently easier to understand and maintain. 2. Experience Editor Removal This is one of the most impactful changes. Unlike JSS, the Content SDK does not support the Experience Editor. Instead, all visual editing is handled through the XM Cloud Pages Builder in metadata integration mode. This eliminates the need for chromes integration mode—previously central to the Experience Editor—and enables further code optimizations. 3. Mapping Components In the Content SDK, all components must be manually reg...

  Sitecore has announced the release of the Content SDK . The Content SDK helps developers integrate XM Cloud content with their front-end applications. It is set to replace the existing JSS SDK for XM Cloud. This new Content SDK will exclusively support XM Cloud, providing a cleaner and more streamlined solution. In this blog, I’ll discuss the key features of the Content SDK, how to install it locally, and how to connect it with an XM Cloud instance for local development. Key Features Starter Template: Provides a ready-to-use Next.js template for fast project setup and seamless integration. Framework-Specific Support: Leverages Next.js features like locale-based routing for multilingual sites, plus multiple rendering modes including SSR (server-side rendering) and SSG (static site generation). GraphQL Utilities: Includes prebuilt queries to fetch content, layouts, site information, and dictionary data directly from Sitecore APIs. Multi-Site Capabilities: Supports ...

In my previous blog , I discussed how we can migrate content, media, and users using the XM to XM Cloud Migration Tool – GUI option . In today’s blog, I’ll walk you through the CLI (Command Line Interface) option , which provides the same functionality but is also ideal for scripting and automation . Step 1: Configuration Setup It is very important to use the same configuration settings as in the GUI version, stored in the appsettings.json file. If needed, you can adjust some values manually. You can also refer to a sample appsettings.json file here . Key Configurations RAIFs Configuration The XM to XM Cloud Migration Tool transfers content and media via RAIFs (batches) . The default values in appsettings.json are balanced for most customers. ItemsPerRaif defines the number of items per transfer. Too low → creates too many RAIF files. Too high → may impact transfer speed. MediaSizeLimit defines the maximum media size per RAIF. Must be a long value. Conte...