Architecture overview

Current version: 19.x

The Sitecore JavaScript Rendering SDK (JSS) is part of the headless development suite of Sitecore products, created to enable modern development workflows to produce applications and systems that follow the Jamstack architecture.

Tip

Watch the following video to understand Jamstack.

Sitecore integration and data flow

Applications created with JSS consume Sitecore content and personalization delivered by Sitecore Headless Services or Sitecore Experience Edge for XM, as well as other Sitecore and third-party APIs that provide RESTful or GraphQL API endpoints.

Sitecore Integration and Data Flow

The applications can be server-side rendered using an out-of-process Node.js rendering engine, provided by Headless Services, or a Sitecore-independent rendering host for a truly headless architecture. For more information, refer to the documentation for Server-side rendering JSS applications.

Using manifest definitions, the JSS CLI, App configuration, and the Import service can develop and deploy their applications to Sitecore.

JSS components overview

JSS comprises of:

  • Core SDK functionality for retrieving Sitecore data from various Sitecore services and APIs to facilitate working with Sitecore data and layout in JavaScript.

  • SDKs that facilitate building JavaScript applications with some of the most popular JavaScript frameworks. They help render Sitecore dynamic placeholders, providing components and helpers for rendering Sitecore fields, while the layout and field values remain editable by authors.

  • Sample applications for every supported JavaScript framework to help developers scaffold an application set up for getting and showing Sitecore data.

  • Developer tooling and utilities. See Features and capabilities of JSS.

Essential use cases supported by JSS applications

JSS supports the following core categories of architecturally significant use cases:

See also Features and capabilities of JSS.

Do you have some feedback for us?

If you have suggestions for improving this article,