The Sitecore JavaScript Rendering SDK (JSS) offers GraphQL services and clients that streamline the process of querying and updating data with GraphQL. Although we can create and choose different content item resolver, for complex queries and data we can opt for Graphql. JSS applications provide various choices for utilizing GraphQL. If you’re working with a […]
Posts Tagged ‘Headless CMS’
Sitecore JSS Development Essentials: Use of Middleware in Next.js
Middleware serve a purpose of augmenting or modifying the request and response objects before the request reaches the actual page or API route handler. There can be instances where you want to validate if user has valid token or check if the request has valid header from security perspective or update cookies, log some information […]
Sitecore JSS Development Essentials: Error pages
Continuing my Sitecore JSS Development Essentials blog series, I will share how to handle error pages in Sitecore JSS website in this blog An error page, is an essential component of any website. It serves as a fallback page that appears when a user tries to access a specific URL that doesn’t exist or encounters […]
Sitecore JSS Development Essentials: Create new placeholder in Sitecore Next.js app
In the previous blog, I demonstrated how to create a new component in JSS Next.js app. If you must have noticed, I added it to an existing Main placeholder, however most of us come across scenarios where we have to create new placeholders to build the desired page design. So, in this blog, I will […]
Sitecore JSS Development Essentials: Create new component in Sitecore Next.js app
As Sitecore has started supporting Headless CMS architecture, from my working experience on headless JSS projects, I thought of putting together a series of blogs demonstrating the basics that one has to do in Sitecore Next.js project. In my first blog, I will explain about creating new component in sitecore and frontend project. The prerequisite […]
Headful or Headless AEM? Why not both with Hybrid? – Part 2
Previously I presented a common situation where an engineering team might push for Headless AEM and covered why, in my opinion, a Hybrid solution is a better approach. I discussed how Content Fragments, Experience Fragments, and Sling Model Exporters are used in combination to deliver the Headless side of the AEM experience. In case you […]