This blog explores an experimental approach to running Sitecore’s Layout Service on ASP.NET Core, shifting logic traditionally managed by Custom Content Resolvers from .NET Framework to a more flexible ASP.NET Core environment. The project introduces capabilities for modifying and caching GraphQL API calls, offering insights into alternative architectural strategies for Sitecore projects.
With a few lines of code you can show a loader while navigating on a single-page application (SPA).
You can download the slides from my SUGNL presentation here.
The Hybrid Placeholder 1.1 has improved Experience Editor support.
The Hybrid Placeholder for Sitecore JSS is now available as a NuGet package.
In this video I will explain why I created the Hybrid Placeholder for Sitecore JSS. After that I will also go through all the files to show how it works.
The Hybrid Placeholder now has an improved version which is available as a package for Sitecore.
By using the Hybrid Placeholder it's possible to use asynchronous loading for heavy parts of a custom Rendering Contents Resolver.
The next version of Sitecore JavaScript Services for React will be able to get the Sitecore context with Hooks.
With the contract-first workflow the frontend and backend developers can work in parallel based on a data structure 'contact'.