Sitecore Stream introduces a modern, real-time, event-driven architecture to the Sitecore ecosystem, enabling more scalable and reactive digital experiences. While it’s built to thrive in the cloud, developers often want to test it locally, especially in Experience Platform (XP) environments. This blog post walks you through how to install and configure Sitecore Stream on a

Sitecore Stream is a new SaaS-based Digital Asset Management (DAM) and Content Hub capability designed to enhance content delivery pipelines. When integrated with Sitecore XP (Experience Platform) and Sitecore XM (Experience Manager), Stream enables headless, cloud-native content streaming, especially for modern composable DXP scenarios. What is Sitecore Stream? Sitecore Stream is: It’s most commonly associated

In this new era where cloud computing is common, we want to save resources and time managing our apps, and all new front-end frameworks are capable of doing a lot of things, this is where we use “Headless” applications. Since Sitecore released the JSS version of their CMS, the development of a website changed a

Part of the upgrade in a Sitecore project is to remove the package.config file and change the way how we handle all Sitecore references. So, let’s follow these steps: Ok, so until here isn’t a big deal, right? So let’s do the following in the project At this point, you just need to add the

One of the critical things when we do an upgrade to our Sitecore Instance is to upgrade the code and the helix structure in the solution. So, I will describe the primary topics that everyone has to keep in mind in the upgrade process: Remove Gulp Files When we have an old solution using gulp