Add caching to Sitecore JSS Next.js public directory

January 8, 2023

☕️ 1 min read

By default assets from the public directory have no cache headers set. Usually you have assets that never change and are quite large in this directory. It's worth fixing this.

Multiline underline transition

November 27, 2022

☕️ 1 min read

To create an underline transition on multiline text links, one solution is to use a pseudo element with a background. This can be further customized with tweaks to the animation flow. Here is an example using React and extending the MUI Link component.

Sitecore JSS Next.js on Azure Static Web Apps

October 26, 2022

☕️ 5 min read

Azure Static Web Apps now support non-static features of Next.js, including Incremental Static Regeneration and Server Side Rendering. Learn more about the steps taken to deploy a Sitecore JSS Next.js project to Azure Static Web Apps, including working around problems encountered.

Sitecore JSS Next.js without Vercel

October 10, 2022

☕️ 3 min read

Yes, you can still run Sitecore JSS Next.js on Azure Functions without Vercel. This can be done with custom Azure Functions and a Azure storage account with a YARP proxy in front of it.

Auto-format typescript with a npm task

October 2, 2022

☕️ 1 min read

To help keep non-JavaScript developers from encountering issues when making changes to a React rendering, a simple npm task can be added to the project's package.json file to automatically format typescript using Prettier and ESLint rules. This keeps the code consistent without requiring additional tooling to be installed.

Create a scalable head for Sitecore JSS

September 26, 2022

☕️ 6 min read

I recently worked on a headless project with Sitecore, the way of working I choose there worked really well in my opinion. In this post, I like to talk about the choices I made and how they helped the team create a good workflow.

Can we keep up with Vercel?

April 5, 2022

☕️ 1 min read

Last year the I spent time getting Sitecore JSS Next.js to work on Azure but encountered issues when updating to Next 12 and with Azure functions v4. I wonder if it's worth maintaining custom hosting solutions for Next.js.