In my last blog, I have explained how to setup ASP.Net Rendering SDK on developer machine and configure with your CM website. In this blog, I would explain the ASP.Net Rendering SDK OOTB solution design. If you open the OOTB solution file, you will get two projects. A) Platform B) RenderingHost

Sitecore introduced Sitecore JavaScript Services (JSS) to support headless with Sitecore 9.0. It’s a very good move for the headless and front-end technology where rich digital experience website can be easily using front end having analytics and personalization capabilities. In this case, Sitecore content getting severed by API named Layout Service in JSON format and client scripting technology like ReactJs, Vue Js consume this JSON and render/print the page.

Sitecore Dynamic placeholder is a great functionality for the content author. It provides the functionality to add/change the layout at runtime without knowing much about Sitecore and technology. Content author can add/change component at any point of time at the given place.

Sitecore JSS is very hot now a day because of its headless architecture. One of the cool features of Sitecore is Sitecore Form, where marketer can create the Sitecore Form as per requirement without having much Sitecore or technical knowledge.

Use this NPM command to install Sitecore JSS sdk globally. It would download Sitecore JSS package. You can verify that Sitecore JSS installed or not by following command.

Sitecore JSS is available in the market since around two years. It is a very well-known technology at least among the Sitecore and CMS domain/technology. People are using Sitecore JSS from long time now. During some discussion I found that still lots of people are not aware about some basic things about Sitecore JSS.