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
