Most importantly, Jamstack allows us to utilize API-based CMS services, like Prismic, which are called “headless” because they separate the CMS from the front-end code. This separation enables developers to implement optimized technologies, rather than being committed to the CMS’ front-end approach. Headless CMSs allow you to deploy your site around the world on a CDN, which means that users will load your content more quickly than most traditional WordPress sites. Meanwhile, because the CMS is a service, it allows companies like Prismic to do the work of implementing innovations like shifting from being simply a “headless CMS” to delivering a “headless website builder.” When developers use Prismic, they’re able to create Slices, or reusable website sections, that give content teams a custom website builder experience.