Sitecore

Hello everyone! I hope you’re doing well. Let’s continue exploring how we can customize asset action visibility in a Content Hub external component. In my previous blog, Beyond Permissions: Customizing Asset Actions in Content Hub , we discussed how to hide the Download button on the asset search page for assets belonging to a specific source system. However, there’s another important aspect we haven’t covered yet: What happens when a user tries to download the same asset using a bulk operation? Hiding the Download button from the asset card is one thing, but ensuring that the same restriction applies to bulk operations is equally important. In this blog, we’ll explore how we can handle this scenario using a Content Hub external component. When policies cannot fully address this requirement, we can still rely on our trump card: an external component. In this scenario, we’ll continue using the same source system, KOL , to demonstrate how we can control asset actions for assets belo...

Hello everyone, Welcome to another blogpost. This blog will focus on Sitecore Content Hub development. We will discuss a use case that is highly relevant to practical development and reflects real-world business scenario. Let's get started without wasting any more time. Sitecore Content Hub provides a powerful security model through User Groups, Policies, Permissions, and Conditions. While these controls determine what users can do within the platform, they do not always control what users see in the user interface. Our blog will be exactly around this functionality. We received a requirement to restrict the download of certain assets from the Asset Search page. Specifically, any asset tagged with a particular taxonomy value should not be available for download by users. We explored using policies and permissions, particularly DRM rights in Content Hub, to address this requirement. However, none of the available configuration options provided a way to hide the Download button on...

Hello everyone, in this blog we will explore how the Sitecore Marketplace has transformed the Sitecore AI ecosystem. We will also look at how to get started with development and build a practical application that will be hosted on Vercel. So, let’s get started. If you’ve ever seen a content author navigate through multiple levels of the Sitecore AI content tree just to find a page they edited yesterday, you know how frustrating the experience can be. Similarly, when Sitecore developers work on stories and need to test their changes end-to-end, they often have to manually keep track of all the pages where a particular component has been added. SC Bookmarks is a Sitecore Marketplace custom app that gives Page Builder authors the ability to pin frequently edited pages, see recently visited pages, and search through their bookmarks — all from a sidebar panel that lives right next to the canvas. No more drilling through the content tree. In this post, I'll walk you through every ...

Hello Everyone. In this blog, we will see one of the pain point while working locally with Docker and Sitecore AI. Developers often experience slowdowns in local environments due to the need for manual publishing. This becomes even more frequent given how Docker setups can sometimes become unstable or require restarting (docker down) because of various unpredictable issues. When running your project locally using Docker (docker up), you typically: Start containers Wait for CM to be ready Manually trigger publishing This becomes repetitive, time-consuming, and error-prone. In this blog, we’ll explore how to eliminate manual publishing by enabling auto-publish during Docker startup, along with a real-world use case. Now let's see, how we can implement the same. Step 1: Update your project csproject file with this below entry. The RuntimeIdentifier = win element in a .csproj file tells .NET which operating system/runtime your application is targeting. <R...

Hello everyone, In this blog we will learn and see an important concept i.e XDT transformation which is widely used in Sitecore ecosytem even if it is XP, SXA, Headless or Sitecore AI. Let's start quickly. What is XDT tranformation: Managing configuration changes across multiple environments can quickly become difficult. We might have many important credentails that may vary across your different environment like third party api url, credentials or even emails that can be triggered during workflow publishing. This are mostly run time configuration changes and this is mostly after deployment process. I will mostly focus on Sitecore AI, By default we have transformation configuration node that can be added to xmcloud.build.json file. So when this config is available, during Sitecore AI deployment, it auto pickup the tranformation file and perform the transformation directly. Check the below screenshot which will give you fair idea. Now let’s move on to the interesting part—ho...