Uniform Docs

Uniform Docs

›JAMstack for Sitecore

JAMstack for Sitecore

  • Overview
  • Supported Versions
  • FAQ

Getting Started

  • Sitecore Installation
  • MVC Starter Kit
  • JSS Starter Kit
  • Deploying Sites

JAMstack for Sitecore

With standard Sitecore, a Sitecore content delivery (CD) server is responsible for building pages at runtime. Page building is among the most expensive operations that a Sitecore server can perform. This requires a significant infrastructure be in place in order to ensure requests from all visitors can be handled.


Page building with standard Sitecore

sequenceDiagram Sitecore CM->>Sitecore CD: Publish site Visitor->>Sitecore CD: Request Sitecore CD->>Sitecore CD: Resolve item Sitecore CD->>Sitecore CD: Build page Sitecore CD-->>Visitor: Response


JAMstack is an approach to building websites that addresses the challenges that Sitecore developers face when building fast, scalable, and secure sites. This approach involves:

  1. Statically rendering the entire Sitecore site at build-time
  2. Deploying the resulting files to any delivery platform you want, including Netlify, AWS and Azure
  3. Letting the browser control dynamic functionality


Page building with Uniform

sequenceDiagram Sitecore CM->>Sitecore CD: Publish site Sitecore CD->>Uniform: Publish event Uniform->>Uniform: Pre-render site Uniform->>CDN: Pre-rendered site files Visitor->>CDN: Request CDN-->>Visitor: Response


On top of that, Uniform makes origin-less tracking and personalization possible. Marketing users assign personalization in Sitecore the usual way.

Instead of personalization running on the origin (i.e. Sitecore CD server), execution runs on the edge (if your CDN supports it) or on the client. This replaces the performance hit of going back to the origin with the performance, scalability and security benefits of a CDN.


Edge-based personalization

With edge-based personalization, the personalization rules are converted into a format that the CDN can understand. When a visitor requests a page that contains personalization, those rules are executed on the edge.

sequenceDiagram Browser->>CDN: Request CDN->>CDN: Execute personalization CDN-->>Browser: Response


Client-side personalization

With client-side personalization, the personalization rules are converted into a format that can run on the client. When a visitor requests a page that contains personalization, those rules are sent to the browser, which executes them.

sequenceDiagram Browser->>CDN: Request CDN-->>Browser: Response Browser->>Browser: Execute personalization
Last updated on 4/21/2020
Supported Versions →
Copyright © 2020 Uniform