Learning Sitecore - Tips and Tricks

Triggers: In Sitecore Content Hub, triggers are events or conditions that initiate automated actions. These can include changes to assets, metadata updates, or other predefined criteria. Triggers serve as the starting point for automation workflows, reacting to specific events within the system. Actions: Actions in Sitecore Content Hub are the executable steps triggered by an event or condition. These steps can be a variety of operations, such as updating metadata, moving assets, or triggering notifications. Content Hub provides a set of predefined actions, and users can also create custom actions to suit their specific workflow requirements. Scripts: Scripts enhance the automation capabilities in Sitecore Content Hub. Users can write scripts using languages like JavaScript, C# to define custom logic for triggers and actions. These scripts allow for more flexibility and can be leveraged to perform complex operations, extending the automation capabilities beyond what predefined actions ...

⮚ Sitecore Content Hub - Triggers, Actions and Scripts ⮚ Setup Sitecore XM Cloud Dev Environment using Docker ⮚ How to test Next.js pages and components with Jest for Sitecore Headless Development ⮚ Fetch component-level data in Next.js app using GraphQL - Sitecore Headless Development ⮚ Multisite configuration in Next.js application using Middleware ⮚ Generate a sitemap for Sitecore Headless Next.js app ⮚ Create Hero Banner component in Next.js app using the Sitecore-first development workflow ⮚ Fetch Site Settings in Layout Service using GetLayoutServiceContext Pipeline ⮚ GraphQL query to fetch Site Settings item in Next JS application ⮚ Create Custom Rendering Contents Resolver for Sitecore Headless Application ⮚ GraphQL query to fetch the country specific state list - Sitecore Headless Development ⮚ Sitecore Item Service Rest APIs for Client Apps ⮚ Sitecore OrderCloud SDK Client Library for .NET ⮚ Custom validator for Sitecore Rich Text field ⮚ Useful PowerShell sc...

  Below are some helpful PowerShell scripts that prove beneficial for any Sitecore developer when making bulk changes in Sitecore or generating self-signed certificates. #1. Insert a user in Sitecore using the Sitecore PowerShell Extensions (SPE): # Set the user credentials $userName = "user1" $password = "passw0rd123" $email = "user1@example.com" $role = "sitecore\ContentAuthor" # Specify the desired role # Get the user manager $userManager = Get-UserManager # Check if the user already exists if ($userManager.GetUser($userName) -eq $null) { # Create a new user $newUser = $userManager.CreateUser($userName, $password, $email, $null) # Add the user to the specified role if ($newUser -ne $null) { $roleProvider = [Sitecore.SecurityModel.Roles.RoleManager]::GetRoleProvider("switcher") # Get the role $sitecoreRole = $roleProvider.GetRole($role) # Add the user to the role $sitecoreR...

The Rich Text Editor (RTE) stands out as the tool most frequently and extensively utilized by content authors. This is the interface extensively utilized for manipulating the HTML of the page/components. As a result, developers must implement fundamental validations for Rich Text fields. Nevertheless, there are instances when basic validations are insufficient. In such cases, it becomes necessary to implement a custom validator. In this blog, I will dig into a practical scenario where the implementation of a custom validator was imperative. This validator goes beyond merely validating HTML; it also performs instant corrections as needed. Let me give you the background why we need to implement a custom validator for Rich Text. I would like to highlight here the  Links to cross-origin destinations are unsafe  SEO audit issue. Lighthouse tool flags unsafe links to cross-origin destinations, if it is not handled properly. Linking to a page on another site with the target="_bl...

Core Web Vitals are a set of specific  metrics  that Google considers important in a webpage’s overall user experience. These metrics are crafted to assess the genuine user experience, encompassing loading performance, interactivity, and visual stability of a webpage. Core Web Vitals metrics: First Input Delay – FID First Contentful Paint – FCP Largest Contentful Paint – LCP Cumulative Layout Shift – CLS HOW TO IMPROVE FID SCORE? FID (First Input Delay) measures the duration from the moment a user initially interacts with a page. In order to deliver a positive user experience, websites should aim for a First Input Delay of 100 milliseconds or lower. FID is a metric that measures a page's responsiveness during load. As such, it only focuses on input events from discrete actions like clicks, taps, and key presses. Potential interactions examined in FID: Clicking on a link or button Adding input text into a blank field Selecting a drop-down menu Clicking a checkbox Here are...