The term "headless CMS" refers to platform architecture where content management is decoupled from content delivery (i.e. presentation logic). In this scenario, the presentation layer retrieves data from the CMS using an API endpoint. This is made possible by the presentation layer being content-agnostic, so the markup it generates is "hydrated" with data from the API.
Sitecore's "Hybrid Headless"
In other headless CMSs, the decoupling is limited to content only, such as Text and Images. In this case, Content Authors can update content fields, but how the different content fields are laid out on the page is specified in code. Updating layout requires code changes.
What's special about Sitecore's headless architecture is that Content Authors retain both content and layout management.
- Getting Started
- Sitecore Essentials (FREE eLearning) - Sitecore JSS Fundamentals
- Sitecore Headless Services for JSS Workshop
- JSS with Blazer YouTube playlist
- Integrating a Client Framework with JSS YouTube playlist
- Headless and JSS YouTube playlist
- Headless Services Architecture
- JSS Architecture
- Walkthrough: Using the Sitecore Container Template for JSS Next.js Projects
- JSS Developer Trial
- JSS Developer Trial - Connected Demo guide
- JSS Source Code
- JSS Sample Code
- JSS and Headless Services Downloads
Sitecore Headless Development is based on a rendering host front end and a Sitecore instance back end. This decoupling of logic domains makes a Sitecore solution easy to develop, maintain, scale, and upgrade.