When building a headless site on Optimizely SaaS CMS, one of the earliest and most critical design milestones your team will face is defining your content model . Unlike traditional monolithic setups where visual layout often dictates data...

  Part 3 of the Parallel Development series. The branch-scoped push script from Part 1 works. Run it on a feature branch where you've touched a handful of independent content types and it does exactly what it promises — pushes only your changes,...

📌 A note before you read: The approach described in this article is not a replacement for Optimizely’s recommended out-of-the-box component registration pattern — which is clean, explicit, and exactly right for most projects. This is written for...

When Optimizely shipped the JavaScript SDK and CLI for CMS SaaS, they gave developers something pretty cool — a code-first workflow for content modeling. Define your content types in .tsx files, run npx @optimizely/cms-cli@latest push , and your...

  Picture this frustratingly common scenario in headless, code-first development with Optimizely SaaS CMS: You’ve defined a brilliant new element, block, or page type in your React codebase. You trigger your local push command. The console works i...