Nidhi Paneri | Blogs

We've been working on Sitecore projects using the JSS SDK for a while. Now that the Content SDK has been released, we're wondering which one to choose going forward. Both tools support building modern, headless websites but they approach it differently. Let's break down how each works and helps to decide which one is the best fit for your project. What Are These SDKs? We can consider these SDKs as a toolkit that helps us as developers to build websites faster and easier. ·        JSS SDK (JavaScript Services SDK) -  JSS has been around for a while. It's like a bridge that connects your website's frontend (what users see) with Sitecore's backend (where content is stored). You can use it with popular frameworks like React, Vue, or Angular. ·        Content SDK -  Content SDK is the newer block. It's built specifically for Sitecore XM Cloud that is Sitecore's cloud platform. It focuses on making websites super-fast...

Sitecore has introduced a developer-friendly , cloud-native way to access XM Cloud content without the overhead of traditional rendering. The Content SDK delivers clean JSON, leaving rendering fully to the frontend and it’s evolving fast. As the digital experience landscape shifts toward composable architectures and headless content delivery, Sitecore continues to evolve with modern developer needs. One of its most exciting and practical additions for XM Cloud users is the Content SDK, A lightweight, REST-first way to access Sitecore-managed content. If you're building fast, modern frontend apps and want to escape the complexity of layout engines, placeholders, and personalization infrastructure, the Content SDK might help you. Content SDK releases: Version 0.1.0(Beta) released in April 2025 First public beta, stripped-down JS package optimized for XM Cloud, smaller than JSS, GraphQL ready, tied to XM Cloud Pages for metadata editing. Version 0.2.0 released in May 2025...

If you're building a modern web application using Sitecore Headless (JSS), you’ll often need to fetch dynamic content lists like employee directories, articles, or products. To make this dynamic and user-friendly, you’ll want: Filtering – Narrow down results (e.g. by department or name) Sorting – Order by fields like name, date, or custom rank Pagination – Load data page by page In this post, I will walk you through how to build a Sitecore GraphQL query step by step, from basic retrieval to fully paginated, sorted, and filtered results. Demo Setup: Sitecore Content for Querying To demonstrate these GraphQL features, we’ve prepared the following in Sitecore. Template: UserInformation A custom template named UserInformation was created with 5 fields: Field Name Field Type UserName Single-Line Text Designation Single-Line Text Department Single-Line Text ...