September 2025: the Content SDK migration was documented by everyone except Sitecore

  • JD + AI
  • Sitecore
September 2025: the Content SDK migration was documented by everyone except Sitecore

September 2025 produced one fact that changes an XM Cloud plan: move a front end from JSS to the Content SDK and the Experience Editor does not come with you. Visual editing goes to XM Cloud Pages, the chromes integration mode disappears, and there is no compatibility path back.

Every account of that in our September harvest is somebody's personal blog. Forty-five Sitecore items cleared the window: forty-three from individual practitioners, two from a consultant at a Sitecore partner, none from a vendor-official page.

Take that last number carefully. We reached this month through feed archives rather than live crawling, and archives lose vendor pages faster than they lose blogspot, so read it as a gap in our coverage rather than as proof that Sitecore published nothing. What it does say reliably is where a practitioner would have found their answers that month, which was from each other.

The migration, written by the people doing it

Migrating Next.js Apps to Sitecore Content SDK — nikitavashisht29, TECHHUB The clearest sequencing of the move: get to JSS 22.8 first, then migrate. The inventory of what changes is short and expensive. sitecore.config.ts and sitecore.cli.config.ts become the configuration surface, a SitecoreClient class replaces the REST and GraphQL services, defineMiddleware replaces the middleware plugins, and a component map replaces componentBuilder. Our record credits the author by handle only. The version claims here are this author's rather than a vendor page's, so confirm them before you commit a sprint.

Sitecore XM Cloud Content SDK vs. JSS SDK: Key Differences and New Features — the page carries no byline in our record; it was published on the blog "Koushik Mukherjee - Sitecore MVP" Read this one second. Eight differences with a cons list that does not flatter the SDK: teams "relying heavily on EE must adapt their workflows", migration means dependency, configuration and code changes, and there are new concepts to absorb before anything compiles. The detail most likely to bite you is component registration, which is manual in .sitecore/component-map.ts with no file watcher unless you opt into the CLI's generate-map command. The companion getting-started post from the same blog, also unsigned in our record, covers the install.

Content SDK 1.1: Design Library Enablers, Cursor Rules, Optimized Editing & Preview, and More — Nidhi Paneri The only release write-up in the month, and it doubles as an upgrade diff: import map and code generation for the Design Library, Cursor rules in the box, display-name routing with UTF-8, ESLint 9 with flat config. Paneri walks the 1.0.0 to 1.1.0 change line by line, including the writeImportMap addition to the CLI build section. A community source carrying a version number and a feature list is exactly the claim to check against the vendor's release notes before it reaches an estimate.

The one post with an engineering argument in it

The Secret Sauce to Extending the Sitecore XM Cloud Content SDK Layout Service — Ben Sewards, Tech Appetite The problem is real and boring in the way real problems are: shared route data fetched independently by every component, multiplying calls to Edge. Sewards builds a CustomLayoutService to push it down the tree once. What makes the post worth more than its code is the history it traces. The extension point was a C# getLayoutServiceContext pipeline under XP, became a ComponentPropsPlugin override under JSS, and now lives behind the SitecoreClient. If you have wondered why your old approach has no obvious equivalent, that is why.

Content Hub, where the problem turns out to be people

Sitecore Content Hub Implementation: What You Should Know (From One Digital Native to Another) — girish jain Almost no code. It is a discovery checklist for a DAM rollout, arguing that the project "is really about people, content, and how your organization works together". Learn the current system's habits before pitching features, plan metadata as a foundation rather than an afterthought, and pin down who logs in and how before the integration list grows. Hand it to whoever is writing the statement of work.

Sitecore Content Hub Developer Certification Preparation Tips — Rinku Jain Six competencies, and one constraint that shapes how you prepare: Content Hub is SaaS, so there is nothing to install and practise on. You need a sandbox. Jain, who has taken several Sitecore exams, needed multiple attempts at this one and says so plainly.

XP is not finished with you

EasyLingo 3.0 — Gert Gatogordo Gullentops, EPAM Belgium A language-version overview module for XM/XP, dusted off for Sitecore 10.4 because a customer on an upgrade project was still running it years after its author assumed it was dead. Gullentops works at EPAM Belgium, which implements Sitecore commercially, so this is a partner's post rather than an independent one. It is also the most honest thing in the month: 3.0.1 shipped without Experience Editor support because he could not fix a JavaScript break, the code is public on GitHub, and the post asks the reader to fix it. Check the 10.4 compatibility claim against the repository before installing it anywhere real.

How to Create and Retrieve Sitecore Items in Sitecore XM Cloud Using Content Authoring and Delivery API and Custom Routing in XM Cloud Starter Kit — Chandan The first walks the client credential flow into the Content Authoring API with Postman, the path you take when an external application has to write items rather than read them. The second breaks the starter kit out of its single catch-all route so a /services/* branch can carry its own layout and its own fetching. Both are on a personal blogspot; our harvest recorded the outlet name as "Sitecore", a feed-title artefact rather than a vendor publication.

Beginner's Guide: Step-by-Step Local Installation for Sitecore XM Cloud — Nidhi Paneri A local XM Cloud environment, from prerequisites onward, and a clear statement of why you would bother: debugging GraphQL and validating previews against a cloud instance is the slower and more expensive loop.

AI showed up as a diagram

Building an AI Shopping Assitant on top of Sitecore OrderCloud — Himadri Chakrabarti Part one of a series, and architecture rather than a running system: a React front end, an LLM orchestrated by LangChain, an OrderCloud MCP server exposing search_products and add_to_cart as tools, Pinecone holding the catalogue embeddings, OrderCloud staying the system of record. The honesty about what it is, a proof of concept with the data foundation deferred to the next post, is worth more than a finished demo would be. Our source record captured the author as "Posted on", which is an extraction failure; the page itself is signed by Chakrabarti.

Sitecore Stream - Platform DxP Evolution — Daivagna Nanavati A release timeline for the Stream platform DxP package, the on-prem XP/XM piece rather than the composable one. The useful detail is that setup collapsed from editing both Sitecore.AIClient.config and the connection string to just the connection string, with a client ID and secret from the portal. The release count and dates come from an enthusiast tracking it rather than a vendor changelog, so treat them as a map and not a schedule.

What we would do about it

The operational knowledge of the largest front-end change XM Cloud has asked for is spread across a dozen personal blogs, and one of them supplied eight of the forty-five items we harvested. That is what happens when a vendor ships an SDK transition faster than it documents one, and it works right up until the month those blogs go quiet.

So two things. If a JSS to Content SDK move is on your 2026 roadmap, do not budget it as an SDK swap: removing the Experience Editor changes how your editors work, which means training, workflow rewrites and a conversation with people who are losing a tool they like. The npm upgrade is the cheap part. And whatever you learn doing it, write it down somewhere your own team owns, because the posts above are why this migration is survivable and none of their authors owes you a maintenance commitment.

One item from this month's harvest is missing above. Its recorded link resolved to the blog's homepage rather than to the article, and we do not cite what we cannot link.

Sources

sitecore · xm-cloud · sitecore-headless · how-to · sitecore-xp · ai · content-hub · sitecore-search