Sitecore

Learn how to set up a Sitecore XMCloud solution with Storybook and testing addons to streamline component development and testing in a SaaS environment using NextJS.

Recently, I've been part of looking at a rescue mission for a failed XM Cloud build and as part of doing a review of their solution, there were some solution design and configuration pieces which stood out as potential knowledge gaps for first-timers which I thought would make a good topic for an article.

Building Headless components for Sitecore XM Cloud has some notable differences in the way you construct your end-to-end component to ensure it supports Pages. This article is an walk through of some of the differences and gotchas for a simple CTA Button Component.

If you're currently considering a Composable SaaS migration to Sitecore XM Cloud, you're more than likely going to fit into one of the following categories described in this article. Let's take a look at how you might make an educated decision.

So you've made the leap or are about to make the leap to Sitecore SaaS and you want to understand how Single Sign-on (SSO) will work for you using Azure AD/Entra ID? This post is a quick walk through to get you going.

This post is an update to my previous post on this topic which covers the concepts and approach however Sitecore JSS/Headless has had some significant changes for Sitecore 10.3.X and XM Cloud to enable new capabilities so I wanted to include the steps to achieve this in the new world.

If you've started delving into the world of Composable SaaS in recent times, you may have encountered a common issue when it comes to security and the typical existing Security Posture businesses have which doesn't quite align to the way in which Composable SaaS architectures need to work.

Managing multiple heads means you have multiple env variable files and need to have environment-specific values for a lot of these as you move between environments. Let's also assume you want to have 3 seperate environments on top of your own local development environment

In this article we'll take a look at how you might want to add a SSG Head into a multi-site solution. What the key points of difference are and how you can configure your Headless solution to export to static files which you can host on any webserver that can serve JS, CSS and HTML.

This article covers what you need to know to apply the necessary Security Headers to lock down your Headless Sitecore solution at the application layer. We're using a NextJS Headless solution deployed to Vercel and Sitecore CMS deployed to Azure PaaS.

So you're building a headless solution in sitecore and you want to create a multi-site solution? How can you do this in a properly headless way? This article explores a simple/light-weight approach to setting this up using NPM Workspaces.

Recently I have been working on a 10.2 Sitecore JSS (NextJS/React) build using SXA for what I think it is best for which is adding Tenants and Sites and managing the Content Tree with Local Data and site-specific Media Library and Data Template management.

Sitecore Wildcard Pages with Item Buckets & JSS. If you're new to JSS/Sitecore Headless Services, this article covers the key differences you should know about to make this work.

Recently I have been working on a 10.2 Sitecore JSS (NextJS/React) build using SXA for what I think it is best for which is adding Tenants and Sites and managing the Content Tree with Local Data and site-specific Media Library and Data Template management.

Recently I had an opportunity to do some digging into Sitecore Send and thought I'd share a little bit of what I've uncovered.

Recently I have had a bunch of discussions with people in the Sitecore Community reflecting on my own Sitecore learning experience and how much more challenging it is to get started with Sitecore now days than it used to be.

There is often a situation where you have common types of data on a set of pages on your site which form the main purpose of your website.

In a previous post I discussed the management conundrum of Solr and Sitecore and the challenges faced with their differing eco-systems. This post will be more of a technical guide looking at how to configure SearchStax for your Sitecore Solution.

Solr is such an amazingly powerful product full of great features which is hard to beat however the challenge faced by most companies or Sitecore Development shops is that traditionally, Solr is hosted in a totally different ecosystem.

Often when having discussions with clients using Azure PaaS about DR and the available options, the ideal scenario comes at a sigificant cost.() LINQ to Sitecore capability.

This article describes an issue you may encounter when you are trying to use the faceting capability of Solr. It touches on the way you can use the Sitecore Search API to generate Solr queries which contain facets using Sitecore's FacetOn() LINQ to Sitecore capability.

In this article we look at how you might develop a Federated Search with data using both Sitecore Content and numerous other external data points.

In this article we'll take a look at a realtively simple way in which you can utilise Sitecore to look after managing the indexing of external data for you using Solr as the Search Provider.

This article is a quick look at a few ways in which you can enforce accessibility standards and best practice within Sitecore

Sitecore SXA Themes Enable gulp sync with Creative Exchange Error - 403.0 - The request could not be completed because the service is disabled.

It's as simple as this to stop drowning in config files and improve your build/release process while you're at it.

Setting up a Production-ready Solr instance can be a bit of a pain. Here is a quick guide to get you up and running with a Solr instance ready for your Sitecore 9.x solution.

I've used the Wildcard Page concept within Sitecore in a couple of solutions for clients in the past and have always enjoyed the clever piece of design that they are each time I've done so. I recently proposed using a Wildcard page solution in our Sitecore 8.2 Azure PaaS solution using Azure Search and decided to share some of my initial thoughts and learnings here.

During the move to Azure PaaS there have been a few instances where we've noticed a series of errors being logged about file I/O issues which often result in instances dying within a PaaS "load balancer".

As a 'back in the day' Sitecore developer I used to do more with Sitecore Queries than I'd care to admit. Recently I was looking for a 'good' way to set up a rendering with a default location which worked in a multi-site solution and was playing with Sitecore Queries once again. It occurred to me that the tooling that used to be available is no longer accessible through the Sitecore back end.

I have discussed the Helix design patterns before and I really love their modular approach to code architecture however whilst trying to discuss this with some colleagues and working out the cleanest way to work with Helix and a Multi-site Sitecore solution it occurred to me that if you are familiar with the "Enterprisey" Three-tier design architecture principles, well the same principles can be applied to your Helix development at a modular level.

It's been quite some time since we started our journey using Sitecore 8.2 and Azure PaaS. There has been no small amount of experimentation, failings and most importantly, learnings as we worked towards an automated build and release pipeline using VSTS so I thought I would take the opportunity at long last to share some of my experiences.

Last month was the start of an exciting new website development project to bring my company's Sitecore website into the current era. I'd been aware of the [Sitecore Helix](http://helix.sitecore.net/) design approach for quite some time and was interested in the idea however this finally afforded me the opportunity to really explore what it was all about while I was shopping around for the right approach to building the new site.

For quite a few months now, my workplace has been looking at moving our website from a fully automated, cloud-based AWS solution over to Azure. Every person I've mentioned this to has had a similar reaction, mostly of disbelief. "AWS is far more mature and robust cloud offering".