Learning@Sitecore

If you have worked in Sitecore, then one of the most common term which is being used is called Placeholder keys. They are like the specific area kept reserved in the html structure where you can bind more component. These specific areas are given a name which us being used as key name, see the below example: <div class=”main-content”>               <Placeholder name="placeholder-key-1"…. </div> In XM Cloud, if you are using NextJs as your frontend framework, then adding a placeholder key requires some configurations. I will discuss the steps required and configuration required. Approaches As far I know, there could be three approaches one can follow to bind the components on layout. First approach is stacking the components to same placeholder key available at layout.tsx in NextJs app. The problem with this approach is that it restricts flexibility, reusability, and scalability in case o...

Language fallback is a powerful feature provide by Sitecore, that allows showing the content in the set fallback language if the content is not found in current language. Example, if you have setup your site in 2 languages in which English will be the default and other as Arabic, with Language fallback settings are enabled, if content for Arabic language is not created and accessed then English language content will be use instead. According to me, the best feature it offers is that it lowers down the risk of showing 404 Page not found error if any page content is not available in secondary language due to any reason. In this blog, I would show you how you can enable these settings in XM Cloud CMS along with creating the patch and show you how it works. In case if you are seeking any documentation on How to add additional Language in your XM Cloud site, then you can follow this blog . Types You can setup Language fallback setting in 2 ways: On Item Level I recommend usi...