In Bloomreach Experience v12.3 we’ve introduced an easier way to handle SPAs (and headless development in general) – and we wanted to tell you exactly why we are so excited with this new feature. I’ll be going over this in 3 parts:
[Part 1] What is a Single Page Application and why do people like them so much?
A quick overview on the difference between SPAs and the traditional way to build a website. Along with a look at why SPAs are rising in popularity among developers and why SPAs and CMSs were historically a difficult pairing.
[Part 2] A CMS that works with SPAs like Angular and React – and makes both developers and marketers happy
The fun part! How Bloomreach architecture and new SPA++ support lets developers leverage SPAs while ensuring marketers keep all the modern editing tools they need. We’ll look at how Preview and other key editing features work.
[Part 3] Personalization and Hybrid Support for Single Page Applications
Bloomreach’s native server-side personalization and its content-based architecture makes it the perfect match for enterprise SPA use. We’ll dive in a bit deeper into content personalization and sharing content between an SPA and the traditionally built parts of your experience.
If you’re a developer looking for how Bloomreach handles SPAs differently, you might want to jump to Part 2, and check out the links on implementation and more below. If you’ve been hearing the term SPA and just want to know what in the world it is, start from the beginning.
Just want the code? Here are some helpful links:
