Skip to main content

Introducing Sitecore JavaScript Rendering SDK


Describes the benefits of Sitecore JavaScript Rendering SDK (JSS)

Sitecore JavaScript SDK (JSS) extends the dynamic, component-based Sitecore layout model to the front end. To understand the value of JSS, you must be familiar with the Sitecore workflow and the challenges it presents for integrating front-end frameworks.

The following video describes:

  • The value front-end frameworks add to client applications.

  • The challenges of integrating front-end frameworks with Sitecore and how JSS solves these challenges.

  • An introduction to key JSS modules: Placeholder and ComponentFactory.

  • An introduction to development workflows.

View the entire Master Sitecore Headless & JSS playlist on YouTube.

The Sitecore workflow

Sitecore is a platform for managing online content, experiences, and marketing workflows.

In Sitecore, content authors build pages in a WYSIWYG editor and the power to make decisions about content presentation remains with the content authors. For example, while developers can create a custom set of shopping cart UI components, it is the content author that arranges them on pages and populates them with content.


After assembling components, content authors can apply Sitecore-specific features, such as personalization, to individual components and preview the variations. The following illustration shows an example of how content authors might configure components.



To learn more about Sitecore terminology and concepts, refer to Content authoring concepts for developers new to Sitecore.

Integrating front-end frameworks

The challenge of using Sitecore data in JavaScript applications is that, unlike regular JavaScript apps, the content authors rather than the developers control the page composition.

Although front-end developers do not know the page composition when they develop the application, JSS supports JavaScript frameworks (and Jamstack architecture) as an implementation option for Sitecore-powered web apps, without sacrificing authoring features or removing layout composition control from content authors.