July 2026: the Package Designer is gone, and the replacement UI came from a community developer

  • JD + AI
  • Sitecore
July 2026: the Package Designer is gone, and the replacement UI came from a community developer

If your content-promotion runbook still opens with "build a package", it describes a screen that no longer exists. Package Designer was removed from SitecoreAI on 7 July 2026 in base image 1.8.24, six days after the Content Transfer API and the Item Transfer API went generally available on 1 July.

That is the month, and it did not reach us through Sitecore's blog. It reached us through two people who wrote it up because they had to perform the migration themselves.

Why fourteen items out of eighty-six

July was the largest Sitecore month in our corpus: 180 articles harvested, 86 in scope for Sitecore, 14 cited below. When the ratio is that lopsided the filter is the story, so here is the filter, stated plainly.

An item earned a citation if it did one of three things: changed something you now have to do differently, carried a date or a version or a number instead of an adjective, or said something nobody else said that month. Everything else went.

That cut a lot. Five "Content Insights Tip #NN" posts, all useful, none of which changes a decision. Six package-version bumps from the Sitecore Content SDK repos, which your dependency bot already told you about. Two German-language posts about creative process that our vendor classifier caught but that have nothing to do with running a CMS. Two items whose title extraction failed so completely that the harvest recorded them as %title% %sep% %sitename% and No title — our bug, not theirs, and worth admitting.

And the biggest cut of all: four separate write-ups of the Content Transfer API in a single month. One is below. The other three said the same thing well.

The migration path changed, and it changed on a specific date

The Content Transfer API playbook — Vishal Khera, Insights with Vishal Khera The most complete account of what replaced Package Designer: content streams between environments in encrypted, compressed chunks, produces a .raif file, and the Item Transfer API consumes it on the other side. Both ship OpenAPI specifications, which is the part that matters — the migration becomes a pipeline stage rather than a person with a browser tab. Our harvest recorded the byline as "3× Sitecore MVP & DX MVPVISHAL KHERA", which is the MVP badge fused to the name by a bad extraction; the author is Vishal Khera.

Content Courier, a free UI for the new transfer APIs — Kiran Patil, Sitecore basics! Sitecore has said a graphical migration app is coming to the Marketplace. It is not there yet, and in the gap the transfer APIs are, in Patil's words, "API-only" — moving two pages from DEV to QA means "Postman collections, bearer tokens, and manually shuttling binary chunks around". So he built the wizard himself and open-sourced it. Patil is the author of the tool he is recommending, which is worth knowing before you read the recommendation, and it is still the most practical thing published about SitecoreAI in July.

Both authors trace the 7 July removal to Sitecore's own changelog for base image 1.8.24 and to the api-docs pages for the two APIs. We are relaying two community accounts of a vendor breaking change, not the vendor's own notice: confirm the date against that changelog before you plan a cutover around it. Neither source carries a declared commercial interest in our records, which is not the same as being independent of the outcome.

The .NET floor moved more than Sitecore's did

Four of the fourteen items below come from Microsoft's .NET blog. None come from Sitecore's. That is not an editorial preference, it is what the month looked like: the vendor shipped release notes and the substrate shipped decisions.

.NET 11 Preview 6 — credited to ".NET Team", with no individual byline, .NET Blog (Microsoft) Runtime, SDK, libraries, ASP.NET Core and EF Core all move. Vendor-official, which matters, because this is the layer every XM/XP instance and every rendering host actually runs on.

MCP C# SDK v2.0 — Jeff Handley, .NET Blog (Microsoft) Implements the 2026-07-28 protocol specification with a "stateless-first" design and stays backward compatible. Six of the 86 Sitecore items this month were about MCP in one form or another — Marketer MCP, an enterprise MCP server for XM Cloud, MCP explained for architects. This is the piece of plumbing all of them sit on, and it is the only one with an official version number attached.

.NET Modernization for Beginners — Pablo Lopes, .NET Blog (Microsoft) A free hands-on course that walks a legacy ASP.NET application to .NET 10 using the Copilot modernization agent. If you maintain an XP solution with a Framework-era core, this is the cheapest structured attempt at that problem currently on offer.

CoreCLR progress and the Mono timeline for .NET MAUI — David Ortinau, .NET Blog (Microsoft) The weakest item in this set, and we are keeping it in view rather than pretending otherwise. It changes nothing for a Sitecore team. It is here because the runtime consolidation it describes is the same consolidation that eventually reaches server workloads, and because our harvester follows the .NET blog. Skip it without guilt.

Next.js v16.3.0-preview.10 — no human byline; release notes published by an automation account, Next.js releases on GitHub Prefetching and route-cache work, which is exactly the area where a Sitecore rendering host feels changes. It is a preview tag, not a stable release. Read it to know what is coming; do not pin a client project to it.

The platform is arguing with itself about what it is

Sitecore's twenty-four-year swing from monolith to composable and back — *the page carries no byline we can verify; our record captured the comment form's "Name " label instead, thebitsthatbyte.com A version-by-version account of where each Sitecore release sat on the monolith-to-composable spectrum, ending at SitecoreAI as a single unified platform on a single licence. The argument is that the two poles "aren't a permanent choice so much as a pendulum that tracks vendor economics". The harvest flags this source as commercial in nature, and we cannot name the author, so weigh it as an argument rather than as testimony.

What the Scrunch acquisition actually signals — Daivagna Nanavati The most interesting framing of the month: the acquisition matters less as a product move than as an admission about where discovery traffic is going. Nanavati builds the case on figures he cites from Gartner and Cloudflare Radar; we have not verified those independently, and the post is flagged commercial in our harvest. Treat the roadmap implications as one practitioner's reading, and confirm anything you would put in a client deck with Sitecore directly.

June's twenty-seven updates, told as five stories — Kiran Patil, Sitecore basics! Twenty-seven changes across SitecoreAI, Content Hub and Search in one month, compressed into something a human can retain. This is Patil's second appearance in this post, and Jason St-Cyr appears twice below; between them those two names carry four of our fourteen citations.

SmartPages builds the page instead of you dragging components — Yamini Punyavathi Muttevi, Sitecore Me (our record prefixes the byline with the WordPress "Published by" chrome) A Marketplace app that takes a reference URL or a layout description, detects the sections, and matches them against your component library. Flagged commercial in our harvest. The honest question it raises is not whether the AI assembles pages competently, it is whether your component library is named and structured well enough to be matched against. Most are not.

The Sitecore developer roadmap for 2026 — Chirag Goel, Coders Lifeline The skills inventory for the job as it now exists: XM Cloud, headless, Next.js, Search, Personalize, Connect, and MCP-based workflows. Goel frames the shift as moving from "CMS Developer" to "Digital Experience Engineer", which sounds like a LinkedIn title until you notice that none of the Solr and MVC pipeline knowledge that defined the role for a decade appears on the list.

Two items that are really about dates

Security Compliance Management 3.8.0 and the Puppetlabs modules roundup for June — both Jason St-Cyr, St-Cyr Thoughts Infrastructure housekeeping for teams still running on-premise XP or XM, where compliance scans and Puppet modules are part of the deployment story rather than someone else's problem. Two cautions. The version number for SCM 3.8.0 reaches us from a personal blog rather than a vendor release page, so confirm it before you schedule an upgrade window. And both posts are republications: the SCM piece says it was originally posted on 16 June, the modules roundup on 9 July. They landed in our July window on their syndication dates, not their announcement dates, which is a reminder that a harvest date is not a news date.

What we would actually do about it

The most useful Sitecore documentation published in July 2026 was written by people who do not work for Sitecore, about a screen Sitecore removed. That is not a complaint about the community, which performed well. It is a statement about the shape of the risk.

Package Designer did not break. It was removed, on a date, in a base image, and if you were not reading changelogs that week you found out when a deployment failed. SitecoreAI will keep doing this, because that is what a SaaS-first platform does, and the mitigation is not reading faster. The mitigation is that every manual click left in your content-promotion path is a scheduled outage with an unknown date. Price it that way. A runbook step that says "open X and build a package" is not a process, it is an unfunded migration you have already agreed to.

The counter-argument is real: automating a content path against APIs that went GA six days before the old tool vanished is its own risk, and the graphical Marketplace app Sitecore has promised may make the community wizard redundant in a quarter. We would still automate now. The tool that gets deleted next has not been announced yet either.

Sources

sitecore · deployment · ai · how-to · product · community · frontend · release