Sitecore

Lately more and more people get interested in running Sitecore in Docker containers. So how do you make Sitecore a good Docker citizen?

Nowadays SDK Visual Studio project format is mainly used by .NET Core projects. It is lean, offers a lot of great features and is generally awesome. But can we use it in traditional ASP.NET Sitecore solutions? What are the benefits and pitfalls?

I have already touched upon deploying JSS apps in my Guide on migrating your solution to Sitecore JSS. In this post I want to extend a bit on the topic, in particular on configuration management.

When developing with Sitecore JSS, you can use 2 approaches for shaping JSON data for a rendering in LayoutService output: using a Rendering Contents Resolver or integrated GraphQL. They are mutually exclusive by design, however, there are situations when you might want to use both of them for the same rendering.

Sitecore JSS provides a lot of benefits in comparison to the “classic” Sitecore MVC/Webforms development approach in terms of both usage of the latest and greatest frontend frameworks, but also improving the development workflow. In this post I’ll describe steps and considerations of migrating an existing Sitecore solution to JSS, based on a real world project experience.