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...

 In the previous articles, we have seen the following How to connect Sitecore with Sitecore Content Hub How to export the Sitecore Media library items and import them into Sitecore Content Hub Update all the reference media items with the assets' public links from the Sitecore Content Hub . In this article, we will see how to migrate this content from Sitecore XP to Sitecore XM Cloud. As we have already updated all the Sitecore media library references to Sitecore Content Hub Public links, it will be easy for us to migrate all the content to XM Cloud using the XM to XM Cloud migration Tool Steps to migrate from Sitecore to Sitecore XM Cloud. After downloading the tool, extract and open the folder Go to the doc folder and follow the steps provided in  appsettings.md dependencies.md install.md Here are the steps mentioned in the above files Install the SitecorePackage.zip on the local Sitecore instance. Update the Web.config file with the assembly binding details provided in t...

In part 1 of the article, we saw how to connect Sitecore XP with Sitecore ContentHub, and in part 2 , we saw how to import all the assets to Sitecore Content Hub. In this article, we will explore how to export the content from Sitecore Content Hub along with the assets public link, and update all the media items in Sitecore with the relevant asset's public link based on the identifier ( SitecoreItemIdentifier) that we have exported from Sitecore XP and added in Sitecore Content Hub. We will export all the assets from Sitecore Content Hub based on the search condition, like SitecoreItemIdentifier not empty. To set this Filter condition, go to the Assets page and select the Search Component , and the Query Builder  Select the Assets with SitecoreItemidentifier , as these are the new assets imported from the Excel upload. Once we retrieved the assets, then exported them to Excel for updating the reference in Sitecore XP like below. After getting all the results, export the data fr...

This article covers how to migrate the media library content from Sitecore XP to Sitecore Content Hub.  In the previous article, we have seen how to connect Sitecore XP with Sitecore Content Hub for accessing the assets from DAM. Steps to migrate the content from Sitecore XP: Create an Excel file import with all the media library items with the required fields that need to be imported in Sitecore Content Hub as Assets Fields to be added in the Excel sheet for the Asset creation in Sitecore Content Hub are provided below. ItemName SitecoreItemId ( SitecoreItemIdentifier ) Alt (Title) FinalLifeCycleStatusToAsset (Approved) ContentRepositoryToAsset (Standard) LocationToAsset (For multilingual Content) We will create a PowerShell script that will loop through the media library and create an Excel sheet. Once the Excel is created, we will import the content to Sitecore Content Hub. #Domain url to public else Content Hub will not be able to access the images from Excel. $donainNameUrl ...