We didn’t set out to invent a migration framework. We needed physician-related templates (and a bit of lookup content) on Sitecore AI DEV — with the same item IDs as the legacy XM database — so anything that already keyed off those GUIDs wouldn’t fall apart later.
Packages felt like the quick button (but that is gone :( ). YAML ended up being the better long-term play. This is how that played out, including the boring parts that actually burn the day.
One of those Sitecore issues that looks simple at first, but turns into a few hours of digging.
We had Sitecore Pages working perfectly against the open *.vercel.app URL, but the moment we switched to our protected custom domain, editing started failing with a rather unhelpful 500. The interesting part was that the problem wasn’t really Pages, Vercel, or the domain restriction on its own — it was how the Content SDK makes an internal request back to the app during editing.
Here’s what we found, and what finally fixed it.
If you came from Sitecore XP, you probably used Aliases: short, friendly paths that resolve to a longer item path without changing what the visitor sees in the address bar. In SitecoreAI / XM Cloud headless, classic aliases aren’t the tool anymore. Authors work with Redirect Maps, and the type that behaves like an alias is Server Transfer.
If you’ve ever dropped a perfectly valid Sitecore rendering into a nested <Placeholder> and watched Pages Builder (or your local app) complain that it can’t find the component in component-map.client, you’re not alone — and you’re probably not looking in the wrong place.
This post walks through a real debugging session from an XM Cloud / Sitecore Content SDK Next.js App Router site: adding a Video rendering inside an Interior Media Hero Banner placeholder. The component existed. The GraphQL query existed. The Sitecore rendering componentName was set. And yet the client still couldn’t resolve it.
Headless Sitecore gives you rich page data; Next.js App Router gives you a structured way to turn that into HTML metadata. The two fit together well once you know where metadata is defined, what Next.js actually renders, and which CMS fields you want to own
Recently, I was working on setting up a webhook using the Sitecore Experience Edge Admin API for a cache revalidation scenario. The goal was straightforward: whenever content is updated in Sitecore, trigger a webhook that tells the frontend application to clear or revalidate cached pages.
The implementation itself is well documented by Sitecore, but I ran into an authentication issue that was not immediately obvious. Every request to create the webhook returned a 401 Unauthorized response with the message:
edge.cdn.11: Unauthorized. Failed to find tenant.
After troubleshooting, I discovered the issue was related to the type of OAuth credentials I had created in the Sitecore Deploy app.
If you run into the same problem, this post may save you some time.
[Americaneagle.com] [Mohammed Syam] Recognized as a Sitecore Most Valuable Professional
Honored for commitment to sharing expertise with the global Sitecore community
When working with Sitecore XM Cloud (SitecoreAI), Next.js, and the Sitecore Content SDK, scoped Context IDs are strongly recommended — especially for values exposed to the browser.
I followed the official Sitecore documentation, created a scoped Context ID, wired it into my Next.js app… and still ended up with a runtime error that wasn’t obvious at all.
This post documents what went wrong, why the error message is misleading, and what you actually need to scope correctly.
When working with Sitecore XM Cloud and the Content SDK, adding a Form to a page can suddenly cause a runtime error that wasn’t there before. The error points to Cloud SDK initialization, but the connection between Forms and the Cloud SDK isn’t immediately obvious. This post explains why Sitecore XM Cloud Forms depend on the Cloud SDK Events package, what triggers the IE-0014 error, and where the SDK must be initialized to avoid breaking preview and production environments.
If you’re working with React and Next.js — especially with Sitecore JSS — you might have run into a confusing warning like this:
“This Suspense boundary received an update before it finished hydrating.”
It sounds scary, but it basically means React got confused while it was trying to “wake up” the server-rendered HTML and make it interactive on the browser.
In this post, I’ll explain what hydration means, why this error happens, and how I fixed it when rendering Sitecore placeholders inside a React component.
I've been working recently on my first Sitecore search project, finally i got a chance to work on this amazing product by Sitecore, I dealt with different sources types, and once of the challenges I got is to deal with paginated APIs that we need to index its data, in this blog post I will walk you through how you can index data from all pages, interested, keep reading!!
During a recent project, I encountered a strange issue while deploying a Sitecore XM Cloud solution to a new Netlify environment. The problem was related to Deno installation, which unexpectedly disrupted the deployment process. If you've run into a similar issue—or you're just curious about what Deno is and how it ties into Netlify—keep reading. I’ll walk you through what happened, explain what Deno is, and show you how to resolve the issue.
While working on a recent Sitecore XM Cloud project, I ran into a frustrating issue when trying to build my Next.js app locally using pnpm run build. No matter what I tried, the build kept failing with a 60-second timeout. The error message always began with:
⚠ Sending SIGTERM signal to Next.js build worker due to timeout of 60 seconds. Subsequent errors may be a result of the worker exiting.
If you’ve encountered this error and are stuck like I was — don’t worry. In this post, I’ll walk you through what’s causing it and how to fix it.
In recent months, we’ve seen many Sitecore hotfixes and security patches. While essential, applying these updates—first locally and then through your DevOps pipeline—can quickly become confusing without a proper setup. To ensure your patches are applied consistently, tracked effectively, and deployed securely, you need a structured approach baked into your solution. In this post, I’ll walk you through how to manage Sitecore hotfixes the right way. Interested? Let’s dive in.
Recently, I was asked to conduct an audit for a Sitecore headless website built using Sitecore JSS and Next.js. As part of this process, I reviewed various aspects of the solution—from content modeling and rendering strategies to performance, deployment, and developer experience. In this blog post—and in upcoming entries—I’ll be sharing some of the critical areas you should evaluate, along with best practices to follow when auditing or building a Sitecore JSS/Next.js application. Whether you're a Sitecore developer, architect, or technical lead, these insights can help ensure your implementation is scalable, maintainable, and optimized for a modern digital experience.
Curious to learn more? Keep reading!
In this post I will share my experience working with Coveo content recommendation, in a recent project we wanted to implemented content recommendation for blogs items, while we utilized the wildcard approach for blog details page, this was challenging, specially with Coveo analytics and view event, keep reading to know more!!
Continuing on this series of a useful Sitecore PowerShell scripts that you will need while working on a Sitecore Audit, in this post we will discuss how you should not have excessive use of rendering variants, For Sitecore SXA best practices, it's recommended to limit the number of rendering variants to 15 or preferably below 10 to maintain a manageable and efficient development process. will explain in this post why? and if you're performing a sitecore audit, how you can catch that with simple PowerShell script, keep reading!!
[Americaneagle.com] [Mohammed Syam] Recognized as a Sitecore Most Valuable Professional
Honored for commitment to sharing expertise with the global Sitecore community
Sitecore marketplace has been announced at this year Sitecore Symposium, it has been discussed during MVP summit in addition to a great roadmap session by product team, in this blogs post I will summarize my takeaways including a definition of Sitecore Marketplace, what it means for developers, customers and partners in addition to the current and future roadmap, not to be missed reading!
Sitecore Symposium 2024 took place last week in the country music city Nashville, Tennessee where the city become the digital experience city fir the whole week, where all sitecore experts from around the world meet and share experiences, knowledge and listen to Sitecore latest news and announcements, in this post I will share my key takeaways from this year symposium, from the main keynotes to the roadmaps and to the fun party we had at broadway street, keep reading!!
One week left for Sitecore Symposium 2024 in Nashville, as always, Sitecore symposium carry a lot of news and knowledge for everyone. from keynotes to R&D roadmaps to long list of sessions that excite every developer and marketer, here is a quick post to share what to look for at next week Sitecore Symposium!!
If you worked with Sitecore SXA before, you must be familiar with the virtual media folder concept, mainly the folder that you usually see with the name "Media" under each website you create under your tenant, but have you ever tried or needed to create such folder out of a tenant with a different name than MEDIA as example, lets say to make it easier for your content author to get into a long path folder. not? then don't try, its not going to work! interested, keep reading!
Continuing on this series of a useful Sitecore PowerShell scripts that you will need while working on a Sitecore Audit, as setting a source for image fields is a best practice when working with Sitecore image field, in this post will share a PS script that will help you find any image field that has no source configured which will save you a lot of time to find these instances, interested, keep reading!
In this quick blog post I wanted to share my experience working with code: datasource type, if you didn't hear of this type of datasource in Sitecore with SXA, this blog will be a good article to go through, in addition I wanted to share how we can configure datasource caching OOTB and in some cases using custom code if needed, interested, keep reading!
This is a quick blog post where I want to share a useful script that you would need when working on a Sitecore Audit, if you have been working with Sitecore for a while, you mush have seen or worked on Sitecore Audits for existing website, one of the items that you audit is to confirm and make sure that the implementation avoid the existing of duplicate fields, in this post I will share a Sitecore PowerShell extensions script that you can use to find such incidents, interested, keep reading!
Have you worked on a sitecore XM Cloud yet? Are you preparing for your XM Cloud project? Is it a brand new or a rewrite of an existing website, if it s rewrite or a redesign, you probably need to plan content migration in addition to probably some code migration to speed up your project timeline, in this blog post will share some of tools that you can for your content migration & code migration. Interested… keep reading!
I've been learning and trying XM Cloud over the last few weeks, one of the issues that I came across & worth sharing is a CLI deployment issues that need you to pay attention to details when reading documentation, through to highlight it here in case anyone else came through, following is the error message I got when trying to crate CM deployment through CLI:
You are not authorized to perform the task you are attempting, you may need to assign addition permissions.
In a recent project I was working on, we needed to create a custom Coveo for Sitecore facet which looks like a toggle, if you know Coveo for Sitecore Hive OOTB components you probably know that OOTB we don't have such a component, so, we would need to create a custom implementation for such component, if you got excited, keep reading!
Sitecore recently released Sitecore Cloud forms as part of the XM Cloud product, so if you have an XM Cloud instance, if you check the launch PAD now, you will see a new icon for FORMS!! in this blog post I will share what cloud forms have and what is still developing and missing in the current released version, keep reading!
In this article, I'll demonstrate the process of configuring a submit action in XM Cloud forms. As you're aware, Sitecore XMC forms have recently been released, featuring a range of functionalities including setting up webhooks and assigning them to forms for data submission. Moreover, the introduction of a test webhook functionality allows for seamless testing of form webhooks to ensure successful connections. Excited to learn more? Keep reading!
[Americaneagle.com] [Mohammed Syam] wins Sitecore Most Valuable Professional award
Elite distinction awarded for
commitment and dedication to the Sitecore community
I believe a lot of architects working with Sitecore ecosystem is eager to learn CM cloud, if they're not already started, while working with XM Cloud has some close enough implementation to headless implementation with XM on premise or PaaS it has some differences, a great presentation I attended in the SUGCON NA last month where Andy Cohen shared some very important tips when working with XM Cloud, in this post I will share some of my takeaways out of that session.
While setting up my local instance for an XM Cloud project I got into a strange error while trying to build images locally, an error "failed to register layer: Cannot create layer with missing parent acf3d164746bcef47b6a7fd46c5912a1103931480f6bcf9336efa664f58ad669: The system cannot find the file specified." keep happening, in this post I will share the steps I tried to resolve the error, hopefully it will be useful for someone.
As you know Sitecore this year decided to go with smaller events called Sitecore DX instead of the well known Sitecore Symposium, to make it simpler and easier for everyone to attend this event in their region, this time the DX event was at Minneapolis and my company Americaneagle.com was a diamond sponsor for this event, their was big announcements in this event, in this post I will share my recap from this one day event!
We had an amazing Sitecore MVP Summit last week at Minnesota, we did meet with other mvps from all around the world, also we had a great conversations with Sitecore people, discussing latest and coming updated to the different products, we also had a wonderful night on Monday with a lot of fun games! In this post I will share with you my recap of this couple days event, some of the news that we can share!
Are you planning to be Sitecore Content Hub certified developer? are you curios where you should start? where you can find resources? what topics you should be focus on for the exam? in this blog post I'm sharing my experience preparing for the exam and some of the topics/areas that should focus on, excited? keep reading...
