Sitecore getting started to advanced

 The most anticipated feature from Sitecore that arrived in XMCloud is the ability to have multiple repositories for the XMCloud website, as well as the option to use different programming languages to create environments. Consider a scenario where a client requires both Next.js and ASP.NET solutions within the same Sitecore XM Cloud project . This new capability directly addresses such a need. It empowers the client to maintain separate code repositories for each technology, alongside the Sitecore editing host . This separation allows for independent management of environments for each application. I'm really happy to see this feature available, allowing .NET developers like myself to explore more in the .NET world and leverage the same offerings that Sitecore XM Cloud provides with Next.js. Let's dive into the step-by-step process to configure both Next.js and ASP.NET applications in a single XM Cloud project. Enable this multiple repo feature Go to the XM Cloud Deploy por...

 Our previous article detailed how to enable the new Project Beta feature, offering support for multiple repositories and programming languages within a single project. Following that, we established two separate environments, leveraging distinct repositories (the Next.js Starter Kit and the ASP.NET Core Starter Kit from our GitHub).  To finalize the XM Cloud setup for these environments, Metadata Editing must be configured. As detailed in our previous article, the Next.js application was configured with the default Editing Host options during its initial project setup, thereby providing automatic Metadata Editing capabilities. In contrast, for the ASP.NET Core application, we have created its environment but omitted the creation of an Editing Host.  The screenshot below shows that only a single Editing Host is currently configured, dedicated to Next.js. To switch from the default Editing Host provided by the Starter Kit for Next.js, simply follow the steps below to enab...