-
Continue reading →: Search Playground: design Sitecore search in your browser, then take the code with youEvery Sitecore search project I’ve worked on has started the same way. Before there’s any UI, I spend a day in the API reference: building requests in Postman, working out which widget ID goes where, and deciding which of the SDKs fits the project. Then I build the same search…
-
Continue reading →: SitecoreAI · Marketplace app · Version 2Content Transfer v2: no credentials, and a safety net for every transfer What’s new since the first version of my Content Transfer app, and how it helps the developers and content authors who move content between SitecoreAI environments. In July I shared the first version of my Content Transfer Marketplace…
-
Continue reading →: Making Sitecore Content SDK + Next.js Layout Inspection Easier1. The Next.js App Router Revolution: React Fiber Extraction The Problem In legacy Next.js Page Router apps, inspecting the page structure was as simple as typing __NEXT_DATA__ in the console. However, Next.js App Router apps stream content using React Server Components (RSC). Layout data is hydrated directly into components like SitecoreProvider or SitecoreContext, leaving the…
-
Continue reading →: Beyond Package Designer: A Better Way to Transfer Content in SitecoreIf you’ve worked with Sitecore for a while, you’ve probably used Package Designer to move content, templates, or media between environments. It was a reliable tool for many years, but with Sitecore AI and modern SaaS architecture, Package Designer has been deprecated. Instead, Sitecore now provides Content Transfer APIs and…
-
Continue reading →: Where Did __NEXT_DATA__ Go? Two Ways to Debug Sitecore Layout DataIf you’ve worked with Sitecore JSS on Next.js, you probably had a daily habit: open DevTools, type __NEXT_DATA__, and dig into layoutData. Route, placeholders, context — all in one place. After upgrading to the Sitecore Content SDK and Next.js App Router, that trick stops working. You’re not doing anything wrong. The data didn’t disappear —…
-
Continue reading →: OrderCloud Token Refresh in Next.js: A Production Pattern for SSR StorefrontsOrderCloud project I’ve worked on ships its first version with a token refresh bug. It rarely shows up in dev. It doesn’t show up in QA. It shows up in production — three weeks after launch, on a real device, when two requests happen to refresh at the same moment…
-
Continue reading →: Part 2 — Implementing a Reusable Sitecore Search + OrderCloud BridgeIn the first part, we discussed the architecture behind connecting Sitecore Search and OrderCloud through a centralized bridge. Now let’s look at the actual implementation approach. The idea was never to build something tightly coupled to a single project.The goal was to create a reusable pattern that can work across…
-
Continue reading →: Tracking Custom Click Events in Sitecore Search Using PageControllerProblem If you are using Sitecore Search (formerly Discover), it automatically tracks user interactions inside its official React widgets. For example: Clicking a search result Selecting a filter or facet Navigating through search pages This works perfectly out of the box. However, real-world websites often contain CMS-driven components that are…
-
Continue reading →: Client-Side API Caching with IndexedDB in Sitecore XM CloudIn many Sitecore XM Cloud projects built with Next.js, components often call the same APIs or GraphQL queries multiple times. For example: When a page loads When navigating between pages When components re-render Each time this happens, the browser sends the same request again. This leads to: Extra network requests…

