Skip to main content

New Features in Sitecore 10 : Is it Worthy?

Finally Sitecore 10 is out and all the Sitecore developers are going crazy at this moment, especially the MVPs :P


LinkedIn has flooded with Sitecore 10 blogs about the first installation experience, the introduction of new features etc. So I got curious (like wasnt 9.3 launched a while back..and, when got a chance, deep dived into the Sitecore 10 Release Notes to understand what the newer version brings to the table for developers. Here is the list of Sitecore 10 features which I believe still makes it worthy in content management ecosystem -
  • Infrastructure-as-code - Sitecore 10 officially supports Docker, Kubernetes and new Sitecore-provided image repositories. This is really going to speed up on-boarding process for new developers into the project. So, Infrastructure-as-code enables the local setup to be source controlled (like code). New members have to setup the local repository and run few commands to setup their local instance. What's even greater is that the local setup across the team will be consistent. (Easy debugging of local environment issues.. right :P)

  • A new ASP.NET Core headless development option allows teams to build applications faster on the latest .NET technology. Dot net core (or dot net framework) is Microsoft's future development framework which is free, cross-platform, open source technology (I guess that's enough reason to help us understand why Sitecore went that way).
  • Sitecore for Visual Studio bring headless serialization by combining the best of TDS and Unicorn , making it easy for teams to script content changes and move them between different environments as part of deployment processes. This is the result of Sitecore acquiring Hedgehog (who developed the awesome TDS tool for item serialization and synchronization). Guess what, Sitecore is providing TDS capabilities with a new name now - Sitecore for Visual Studio (or Sitecore Module Explorer).

  • Sitecore CLI  allows console communication with a Sitecore instance. This will ensure higher level of automation. Developers have already experienced similar capabilities in JSS CLI. 

    • Getting Started dotnet new template via NuGet - Sitecore finally has provided a way to create your new Sitecore solution inline with Helix conventions using a single command (just like JSS commands). Till now, developers have manually created the Helix standard folder structure in the solution. Thanks to Docker and dotnet new that made this spin-off possible.
    • Improved Experience Editor When you paste content from Microsoft Word into the Rich Text Editor, it now cleans up the markup. There are more improvements and bug fixes. 
    • Improved JSS - JSS can now successfully handle forwarded deployment requests when it is installed behind a reverse proxy as it is in Docker.
    • Improved SIA - SIA now validates SQL Server and Solr connectivity and also validates the Sitecore license file.
    • Audience analytics filters allow for deeper insights on audience engagement and segmentation to drive powerful personalization across all your channels.
    • Additional HTML Email Templates for EXM provide more options when crafting emails, which translates to the quicker creation and delivery of targeted emails to customer inboxes.
    • Horizon editing interface updates give marketers in-context insight across multilingual and multisite experiences.
    • Stronger CMP integration supports additional field types and allows for persistent taxonomy associations when importing into XP taxonomy repositories and connecting CMP to XP.
    • Salesforce Marketing Cloud (SFMC) connector updates provide new capabilities to immediately send xDB data and trigger Salesforce Marketing Cloud plans in Journey Builder.
    • New marketing automation capabilities include capabilities to engage customers with automated birthday campaigns.
    • Support for GDPR compliance journeys including features that make it easier to enforce and manage consent options as well as supporting the anonymization of personal information submitted via Sitecore Forms.
    And the list goes on :P If you are nerdy enough to seek more, check it out here.

    To sum up, container support to enable infrastructure-as-code, dotnet new based solution template creation, dot net core based headless development option and Sitecore CLI are definitely good steps towards easing development experience. Hence, version 10 makes Sitecore an even more worthier CMS for the developers.

    Popular posts from this blog

    Sitecore PowerShell Script to create all language versions for an item from en version

      We have lots of media items and our business wants to copy the data from en version of media item to all other language versions defined in System/Languages. This ensures that media is available in all the languages. So, we created the below powershell script to achieve the same -  #Get all language versions defined in System/Languages $languages = Get-ChildItem /sitecore/System/Languages -recurse | Select $_.name | Where-Object {$_.name -ne "en"} | Select Name #Ensuring correct items are updated by comparing the template ID  $items = Get-ChildItem -Path "/sitecore/media library/MyProjects" -Recurse | Where-Object {'<media item template id>' -contains $_.TemplateID} #Bulk update context to improve performance New-UsingBlock (New-Object Sitecore.Data.BulkUpdateContext) { foreach($item in $items){    foreach($language in $languages){ $languageVersion = Get-Item -Path $item.Paths.Path -Language $language.Name #Check if language versi

    Export Sitecore media library files to zip using SPE

    If you ever require to export Sitecore media files to zip (may be to optimize them), SPE (Sitecore Powershell Extension) has probably the easiest way to do this for you. It's as easy as the below 3 steps -  1. Right click on your folder (icons folder in snap)>Click on Scripts> Click on Download 2. SPE will start zipping all the media files placed within this folder. 3. Once zipping is done, you will see the Download option in the next screen. Click Download Zip containing the media files within is available on your local machine. You can play around with the images now. Hope this helps!! Like and Share ;)

    Make Sitecore instance faster using Roslyn Compiler

    When we install the Sitecore instance on local, the first load is slow. After each code deploy also, it takes a while for the Sitecore instance to load and experience editor to come up. For us, the load time for Sitecore instance on local machines was around 4 minutes. We started looking for ways to minimize it and found that if we update our Web.config to use Roslyn compiler and include the relevant Nugets into the project, our load times will improve. We followed the simple steps - Go to the Project you wish to add the NuGet package and right click the project and click 'Manage NuGet Packages'. Make sure your 'Package Source' is set to nuget.org and go to the 'Browse' Tab and search Microsoft.CodeDom.Providers.DotNetCompilerPlatform. Install whichever version you desire, make sure you note which version you installed. You can learn more about it  here . After installation, deploy your project, make sure the Microsoft.CodeDom.Providers.DotNetCompilerPlatform.d

    Experience of a first time Sitecore MVP

    The Journey I have been working in Sitecore for almost 10 years now. When I was a beginner in Sitecore, I was highly impressed by the incredible community support. In fact, my initial Sitecore learning path was entirely based on community written blogs on Sitecore. During a discussion with my then technology lead Neeraj Gulia , he proposed the idea that I should start giving back to developer community whenever I get chance. Just like I have been helped by many developers via online blogs, stackoverflow etc., I should also try to help others. Fast forward a few years and I met  Nehemiah Jeyakumar  (now an MVP). He had a big archive of his technical notes in the form Sitecore blogs. I realized my first blog dont have to be perfect and it can be as simple as notes to a specific problem for reference in future. That's when I probably created my first blog post on Sitecore. At that time, I didn't knew about the Sitecore MVP program. Over the years, I gained more confidence to write

    Clean Coding Principles in CSharp

    A code shall be easy to read and understand. In this post, I am outlining basic principles  about clean coding after researching through expert recommended books, trainings and based on my experience. A common example to start with is a variable declaration like - int i  The above statement did not clarify the purpose of variable i. However,  the same variable can be declared as -  int pageNumber The moment we declared the variable as int pageNumber, our brain realized that the variable is going to store the value for number of pages. We have set the context in our brain now and it is ready to understand what the code is going to do next with these page numbers. This is one of the basic advantages of clean coding. Reasons for clean coding -  • Reading clean code is easier - Every code is revisited after certain amount of time either by the same or different developer who created it. In both the cases, if the code is unclean, its difficult to understand and update it. • To avoid s