Sitecore First Development Approach for Sitecore Headless component development with Nextjs

There are a few approaches you can use when creating components with Next.js in a Sitecore headless solution, they are well explained in this blog post. Sitecore first is the mostly commonly used approach, in this blog post I am going to walk you through high-level diagram and steps for creating components using this approach. … Continue reading Sitecore First Development Approach for Sitecore Headless component development with Nextjs

Troubleshooting “Unknown or Incomplete Layout Service Configuration” in Sitecore JSS

Recently, I had to switch my Next.js application from GraphQL to REST. Sitecore have a simple and straight forward article to do just that and apparently it is simply changing one environment variable but it turned out to be a nightmare to get it to work. I wanted to document my experience so it can … Continue reading Troubleshooting “Unknown or Incomplete Layout Service Configuration” in Sitecore JSS

Fixing the Sticky Tooltip AutoComplete Issue in Sitecore’s GraphQL Playground UI

The Sitecore GraphQL Playground UI also called GraphQL IDE is a handy tool for developers working with Sitecore’s GraphQL APIs. It provides a clean, interactive interface for testing your GraphQL queries. If you’ve ever used Sitecore’s GraphQL Playground UI, you might have run into an annoying problem: the tooltip/autocomplete gets stuck on the screen and … Continue reading Fixing the Sticky Tooltip AutoComplete Issue in Sitecore’s GraphQL Playground UI

How Sitecore’s Default Next.js Dictionary Implementation Can Hurt Performance and Bandwidth Usage

In Sitecore, the dictionary is often used to provide translations for labels, buttons, messages, etc. In simple terms, the dictionary is a way to store text in different languages and easily retrieve it. If you are using Sitecore Headless with Next.js and analyze the page's payload you will see that it outputs the whole dictionary … Continue reading How Sitecore’s Default Next.js Dictionary Implementation Can Hurt Performance and Bandwidth Usage