Cable management for the Jamstack
summary
A concrete workflow for composing Jamstack pages from Contentful, Prismic, BigCommerce and Google Analytics via Uniform Canvas, serverless composition API and Next/Vue front ends. The system keeps only entry IDs in Canvas and uses chained enhancers enrich IDs into props to fetch, convert and trim CMS payloads, so a hero component needs only image and text props. Live preview updates on CMS saves, switching a CMS or commerce provider requires changing one enhancer rather than rebuilding the front end, avoiding a multi‑month replatform. uniform stores only pointers
AI-written summary · about
chapters (7)
- 0:00Start
- 2:05Monolithic Suites
- 3:10Composed Architectures
- 28:17Contentful Model Converter
- 32:46Audience Question
- 37:29The Mesh Sdk
- 39:58Digital Experience Platform
related talks
24mUniting the Team with JAMstack
12mCMS and JAMstack: A Tale of Innovation in Web Development
50mDo we really need this JAMstack thing? And what even is it?
34mHow to JAMstack in a dynamic era
31mA sneak peak into the future headless eCommerce
52mStatic eCommerce JAMstack
35mThe Rise of JAMStack
20mComposability: The New Architect in Town