Himmat Singh Dulawat (4x Sitecore MVP)

In this blog post, I will describe to you how to delete the Taxonomy from Sitecore Content Hub: Step 1: Go to the manage icon and navigate to the Taxonomy page using the Taxonomy option: Step 2: For instance, I want to delete the Department Taxonomy, but you see Delete button is disabled. But when you hover over the delete button, you will get a message that says, “You cannot delete a definition that has been published to the delivery platform. It should be unpublished first.” Step 3: It means we need to disable this taxonomy from the Delivery platform. Go to the Manage icon and navigate to the Delivery Platform Page using the Delivery Platform option. Step 4: Locate the taxonomy using the search box in the left panel, then select the Delivery Platform icon. Proceed to disable the Delivery Platform from the relevant settings, ensuring you save and publish your changes. Step 5: Return to the Taxonomy page and click the ...

In my previous blogs, we have discussed how to create a Custom Rendition using Media Processing. See the blog post for more details:  Custom Rendition in Sitecore Content Hub In this blog, we will discuss the deletion of the Custom Rendition created by Media Processing. Step 1: Go to the Dashboard using the Manage icon and click on the Entities: Step 2: On the Entities page, search for Rendition and click on the Rendition Link form left Panel. Step 3: On the Entities page, locate the right panel where you will see the name of your custom Rendition that was previously created. Select the desired Rendition name you wish to delete and click on 'Details'. Step 4: You will be redirected to the Entity Details page, where the Delete option for removing the Custom Rendition is available. Select the Delete button to proceed with deletion. Step 5: After deletion, review the assets to confirm that the Custom Rendition has been removed from...

In a Digital Asset Management (DAM) system, a rendition refers to an alternative version of an original digital asset. This could mean: A different file format (e.g., converting a PNG to JPG) A different dimension, resolution, or size (e.g., resizing an image for web vs. print) A different color space or compression level (e.g., RGB vs. CMYK) For example, the marketing team needs the same product image for the Website (High Resolution), Mobile App (optimized size), and social media (specific aspect ratio). Instead of storing multiple copies of assets in different formats, the DAM module in Sitecore Content Hub provides the features to generate the renditions dynamically using media processing. This saves space and ensures consistency. Sitecore Content Hub by default provides server renditions under the media processing flow, which are Original, Metadata, PDF, Preview, Medium, Thumbnail, and Big Thumbnail. But if you want to create a cus...

You are all aware of the installation of Sitecore Connect for Content Hub on the premise environment. In this blog post, I am going to describe how to install Sitecore Connect for Content Hub in Sitecore Azure Cloud Service PaaS 2.0 environment. In PaaS1.0, you can install it using by Sitecore Azure Toolkit and SXP ARM templates, but in PaaS2.0, you cannot directly access the App Service as it provides an extra security layer using Bastian. Azure Bastion is a fully managed service that is provisioned in the PaaS 2.0 Hub environment to securely connect virtual machines via a private IP address. You can find more information here:  Azure Bastion for PaaS 2.0   What is Azure Bastion? Step 1: Log in to the Sitecore Content Hub and collect the following details: Need to create an OAuth Client ID and secret. (click Manage > OAuth Clients >) Need to create an Action to get the Hub in and Hub out value.  (click M...

Problem Statement: While working with the CKEditor (Rich Text Editor) in Sitecore Content Hub, I have encountered one issue in which my content was listed in alphabetical order. When the author updates any content in the particular CKEditor field and saves the changes, the alphabetical list automatically changes to a numbered list.  After the author edits and updates the content, and clicks on save: Solution: It appears we are experiencing an issue in the Content Editor where nested numbered lists are displayed as alphabets in the editor:  Another example: However, after saving, the lists appear as numbers: To ensure the display is consistent, we need to add the following CSS to the Content Detail page in the page settings:  .content-field ol ol {     list-style-type: lower-latin; } For more information, please refer to the documentation for the CSS tab in the page settings: Sitecore Content Hub CSS Documentation ...

In the Previous blog post, we have seen how we can create and taxonomy and connect it to the M.Asset definition. Please see the blog post for more information: Sitecore Content Hub Taxonomy and Categorization In this blog post, I will explain how to apply this taxonomy on the Search Component and use it as a facet search on the Asset Page.  Step 1: Click on the manage icon, top right corner Step 2: Navigate to the Pages Step 3: In the left panel, click on the Asset page and choose the Search component from the Right panel Step 4: Go to the Facet tabs and click on the "+" icon and add taxonomy as a new facet type: Step 5: Navigate to the Asset details page from the top navigation bar, and in the left panel, you can see the new Taxonomy added as search facets, and you can see that currently, I have tagged only Assets with the Science taxonomy: You can now filter assets based on the selected taxonomy values. Happy Sitecoreing  😊

Sitecore has introduced the AI features into the Sitecore Content Hub. It's an advanced tool to provide features and functionality to content generation, virtual search, content Translation, Image tagging, and many more.  In this blog post, I am explaining a few of them and how to use them from the context of the Content Entity. But before getting started, we need to enable the AI features in Sitecore Content Hub. Enable AI features in Sitecore Content Hub: Click on the manage icon and choose the AI features option. Click on the Enable button for both Content Generation and Visual Search to enable AI features. Content Generation: After enabling AI for content creation, you can generate original content, update or enhance existing content, refine tone, summarize, and check grammar and spelling. To use these features, open any content entity in Content Hub and navigate to a single-line text, multi-line text, or CKEditor field. You’ll see a star...

The Sitecore Content Hub system does not display information about the author who submitted the content on the content detail page for review. To make the author’s information visible on the content detail page, we need to perform the following activities  Create a new member group with the additional Fields Create a Script, Action, and Trigger to set the values Enable the setting on the page component to display the details Create a new member group with the additional Fields: To add information about the author who submitted the item in Content Hub for review, follow these steps to configure it: Step 1: Navigate to the manage icon and choose the Schema option Step 2: On the Schema page, search for M.Content and on M.Content page, click on the “New Group” option and fill in the details, and click on the save button: Step 3: Once you create a new group, click on the New Member option and add the following new members with respective type...

In this blog post, I will explain the Experience Edge for Sitecore Content Hub, Experience Edge for Content Hub APIs, GraphQL IDE, and GraphQL. Experience Edge exposes data through GraphQL APIs and media through a CDN. The CDN is responsible for routing and caching queries that flow to and from the delivery platform. Whenever Content Hub detects changes to approved content or the schema, it raises an event that triggers the automatic publishing process. Refer to the document for more details about the Experience Edge:  Experience Edge for Content Hub To start with Experience Edge IDE, we need to first understand the Preview Vs Delivery APIs: Preview API: A GraphQL API that exposes a preview of your content. This API provides access to all content, including drafts and other content that is not yet approved. Delivery API: A GraphQL API that exposes your published content. This API provides access to approved and published cont...