From JSS to Content SDK: The Future of Sitecore Frontends on XM Cloud

The Sitecore Content SDK is here — and it’s set to transform how developers build frontends for XM Cloud. Designed as a next-generation replacement for the legacy JavaScript Rendering SDK (JSS), the Content SDK brings a more modern, lightweight, and Next.js-native approach to headless Sitecore development.

Simpler, smaller, faster: the shift from JSS to Content SDK.

Still in public beta, this SDK is already gaining attention for its streamlined architecture, performance improvements, and forward-looking approach.

Sitecore Content SDK and XM Cloud

With Sitecore XM Cloud becoming the flagship delivery model for Sitecore experiences, the Content SDK delivers what developers have been asking for:

• Out-of-the-box integration with XM Cloud and Experience Edge

• Full support for Next.js Pages Router

• Reduced frontend footprint — eliminates the need for complex proxy configurations and verbose scaffolding

• Developer-first workflows — supports static generation, SSR, ISR, and preview modes natively

  
  

What's New?

The new Sitecore Content SDK introduces a cleaner, more modular approach to working with Sitecore headless apps, moving beyond the legacy JSS model. With its latest versions, the SDK brings major architectural refinements and breaking changes that aim to improve clarity, extensibility, and alignment with modern web frameworks like Next.js and React.

1. No More JSS Boilerplate

Forget sitecore-jss-proxy, verbose GraphQL scaffolding, and rigid app structures. The Content SDK integrates directly with XM Cloud APIs (Layout Service and Dictionary API), giving you the same editing experience with a fraction of the codebase.

2. Native Next.js Pages Router Support

The SDK currently supports only the Pages Router, not the newer App Router. But it’s built in a modular way that prepares the ground for future App Router compatibility. This means you can start building with confidence today — and evolve tomorrow.

3. Lean, Lightweight Projects

One of the biggest wins: Content SDK projects are significantly smaller and simpler than JSS-based ones. You get:

• Less configuration

• Fewer dependencies

• Clean component mapping

• Streamlined integration with XM Cloud environments

As stated in the official documentation

“the chromes integration necessary to integrate with Experience Editor has been removed from Content SDK.”

This is consistent with XM Cloud’s shift to the new Pages editor, which replaces Experience Editor entirely and renders the old inline editing approach obsolete. Consequently, it will no longer support compatibility with XM/XP Headless solutions.

4. Preview & Personalization

Built-in support for Next.js Preview Mode lets you see edits in context before publishing. Plus, you still get personalization and multi-language support through Layout Service serialization, just like with JSS — but with reduced configuration overhead.

Still in Beta — But Already Impressive

The Sitecore Content SDK is currently in public beta, and while not yet feature-complete, it's already suitable for production projects using Next.js with the Pages Router and XM Cloud.

It is built with support for the latest versions — React 19 and Next.js 15 —  ensuring compatibility with the latest ecosystem advancements.

It does not yet support the App Router, which is planned for a future release. Sitecore is actively gathering feedback and evolving the SDK rapidly — so early adopters will benefit from a head start. Here is the GitHub repository and official documentation.

Get Started: Starter Kit for XM Cloud

The best way to dive in is with the official starter kit:

npx @sitecore-content-sdk/create-sitecore-jss@beta nextjs --destination ./xmcloud-foundation-head-next-level --prerender SSG --yes

This gives you:

• A ready-to-run Next.js project using the Content SDK

• XM Cloud integration (via Layout Service and Dictionary API)

• Editing and preview features built-in

• Sample components, routing, and multi-language support

Developer Insight

If you're starting a new XM Cloud project, the Content SDK is the recommended approach — especially if you want a cleaner codebase, better performance, and future flexibility.

Even though the App Router isn’t supported yet, Sitecore’s architecture choices show a clear direction: embrace Next.js standards, and simplify developer experience.

Summary

Feature	Content SDK
Framework	Next.js (Pages Router)
App Router support	Not yet (planned)
Compatibility	Sitecore XM Cloud, Experience Edge
Editing support	Layout Service & Dictionary API
Reduced SDK Size and Dependencies	Much smaller than JSS (reduction by ~89%)
Experience Editor	No longer supported
XM/XP Headless solutions	Not compatible
Status	Public Beta
Starter Kit	npx @sitecore-content-sdk/create-sitecore-jss@beta

Key Features of the New Leaner Sitecore Starter

Feature

(Nearly) No temp Folder

(Nearly) No lib Folder

Reworked CLI

One-Stop-for-All Client

Pipeable Middleware Functions

Simplified next.config.js

No getStaticProps Blackbox

Central Configuration File

No Plugins (at all) Anymore

Update React to version 19 and Next JS to version 15

Upcoming Enhancements in Sitecore Content SDK

Feature/Area

Maturation of Content SDK

More Demo Templates

App Router

Installable Components/Templates

Consolidation of Starter Kits

Middleware Optimization

And much more...

The Sitecore Content SDK represents a shift toward scalable, maintainable, and cloud-native frontend architectures. While still maturing, it’s already a compelling option for XM Cloud developers seeking simplicity without compromise.

Start small, build fast, and leave the old JSS baggage behind.

Technical Breakdown: JSS SDK vs Content SDK (XM Cloud)

Differences of JSS SDK and Content SDK for XM Cloud