Deploying your Sitecore application on Vercel might come as a surprise if you're accustomed to hosting on platforms like Azure or on-prem servers. While Vercel offers an impressive infrastructure, it works quite differently from traditional hosting solutions. Therefore, it's essential to understand how Vercel charges for its services and how to optimize your application to … Continue reading Sitecore on Vercel: Tips for Optimizing Your Application Usage and Keeping Costs Down
Next.js
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
Leveraging Vanity URLs with Sitecore and Next.js to Ensure Customers Always Access the Latest Product Versions
In today’s fast-paced agile world, product updates and new releases happen frequently often every few weeks or months. For marketing teams, this presents a challenge: ensuring that all promotional materials, including emails, websites, and other digital assets, are consistently updated to reflect the latest product version. One effective solution is the use of a vanity … Continue reading Leveraging Vanity URLs with Sitecore and Next.js to Ensure Customers Always Access the Latest Product Versions
Sitecore Nextjs Error serializing .componentProps[“b53f473e-4cf1-4570-b6e5-aa46c9872634”].fields.title returned from getStaticProps
We have a Nextjs based Sitecore headless solution with Sitecore Experience Edge deployed to Vercel. We are prerendering most used pages during build to make sure they are always available even after a deploy so that even the first user who hits the page does not have to wait a few seconds to see it. … Continue reading Sitecore Nextjs Error serializing .componentProps[“b53f473e-4cf1-4570-b6e5-aa46c9872634”].fields.title returned from getStaticProps
Cache Revalidation in Sitecore Website Built Using Next.js Incremental Static Site Generation
In the ever-evolving world of web development, delivering highly performant and dynamic websites is crucial. When building a Sitecore website with Next.js, utilizing Incremental Static Site Generation (ISSG) and hosting it on Vercel, one of the key aspects to ensure optimal performance and up-to-date content delivery is on-demand cache revalidation. This blog will dive into … Continue reading Cache Revalidation in Sitecore Website Built Using Next.js Incremental Static Site Generation
Next.js API Route for On-Demand Cache Revalidation using pages or app folder
If you're looking for an API endpoint implementation that can take a dynamic path from a query string to revalidate page cache and force page regeneration, you've come to the right place. The biggest challenge with using statically generated sites is the difficulty of pushing content updates quickly in urgent situations. You can't set the … Continue reading Next.js API Route for On-Demand Cache Revalidation using pages or app folder
Next.js Static Site Generation (SSG) vs Server-Side Rendering (SSR)
When it comes to building server-rendered React applications, Next.js has become a popular choice among developers. One of the key decisions developers have to make is choosing between Static Site Generation (SSG) and Server-Side Rendering (SSR). Both have their own benefits and tradeoffs, and choosing one over the other depends on the requirements of the … Continue reading Next.js Static Site Generation (SSG) vs Server-Side Rendering (SSR)
Sitecore Headless Multiple Layouts using Next.js
This post is inspired by https://www.techguilds.com/blog/how-to-use-dynamic-layouts-in-headless-sitecore-applications Problem Statement It is very common to use more than one layout in Sitecore and there could be many reasons. Back in the old MVC days, you would simply link the layout to separate MVC or ASPX files. With Sitecore headless and Next.js you need some code customization as … Continue reading Sitecore Headless Multiple Layouts using Next.js