<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><language>en</language><title>Blog posts by OptiBasics</title> <link>https://world.optimizely.com/blogs/optibasics/</link><description></description><ttl>60</ttl><generator>Optimizely World</generator><item> <title>How I Deployed My Optimizely Content JS SDK Next.js App on Vercel (Hello Opti World)</title>            <link>https://kpbasics.com/?p=8370</link>            <description>&amp;#x1f4cc; Scope: This post covers Optimizely CMS (SaaS) only, using the official content-js-sdk with Next.js 15 deployed to Vercel. This is a practitioner walkthrough — not official documentation. &amp;#x26a0;&amp;#xfe0f; No official Vercel deployment guide exists for the content-js-sdk at the time of writing. This is what I figured out building my first app — Hello [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8370</guid>            <pubDate>Tue, 21 Jul 2026 04:02:15 GMT</pubDate>           <category>Blog post</category></item><item> <title>Optimizely CMS SaaS – Chrome Extension to Stop Accidentally Editing Production</title>            <link>https://kpbasics.com/?p=8353</link>            <description>If you work with Optimizely CMS SaaS across multiple clients, you know the anxiety — multiple tabs, multiple environments, and one wrong edit away from breaking a live site. At Horizontal Digital, we manage several Optimizely CMS instances for different clients, each with production and test environments. The Optimizely UI looks identical across all of [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8353</guid>            <pubDate>Wed, 01 Jul 2026 13:18:25 GMT</pubDate>           <category>Blog post</category></item><item> <title>Optimizely SaaS CMS Contracts: Define Shared Structure Across Content Types</title>            <link>https://kpbasics.com/?p=8339</link>            <description>&amp;#x1f4cc; Scope: This post covers Optimizely CMS (SaaS) only — using the @optimizely/cms-sdk toolchain. CMS 13 (PaaS) handles shared structure differently via .NET interfaces. When you&amp;#8217;re building a multi-content-type site, you quickly run into a problem: Blog Articles, Press Releases, and News Pages all need category and tags — but without a shared structure, you [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8339</guid>            <pubDate>Wed, 01 Jul 2026 13:09:35 GMT</pubDate>           <category>Blog post</category></item><item> <title>Understanding Optimizely Graph: Caching, Webhooks &amp; Avoiding Stale Content (Optimizely SaaS CMS)</title>            <link>https://kpbasics.com/?p=8321</link>            <description>&amp;#x1f4cc; Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If you&amp;#8217;re on Optimizely CMS 12 (PaaS/DXP), the caching architecture and tooling are different. See the DXP ISR docs for that path. Your editor hit Publish. Five minutes later the page still shows the old [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8321</guid>            <pubDate>Tue, 23 Jun 2026 04:28:27 GMT</pubDate>           <category>Blog post</category></item><item> <title>Optimizely CMS (SaaS) MCP Basics</title>            <link>https://kpbasics.com/?p=8270</link>            <description>What just shipped Optimizely quietly dropped something significant: a hosted Model Context Protocol (MCP) server for CMS (SaaS). This means your AI-powered editor — Cursor, Claude Code, VS Code Copilot, or Claude Desktop — can now talk directly to your Optimizely instance. No API scripts, no copy-pasting responses into prompts, no dashboard tab-switching. You type [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8270</guid>            <pubDate>Tue, 09 Jun 2026 04:02:18 GMT</pubDate>           <category>Blog post</category></item><item> <title>Optimizely SaaS Visual Glossary</title>            <link>https://kpbasics.com/?p=8130</link>            <description>Recently I came across Optimizely SaaS CMS Glossary: https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/glossary and I thought it will be good to have a visual Glossary. As my mind absorbs information better with Visual. Yours too? Then this post is for you. Jump to a category Core Concepts The foundational ideas that explain what Optimizely CMS (SaaS) actually is. CMS [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8130</guid>            <pubDate>Thu, 28 May 2026 05:54:19 GMT</pubDate>           <category>Blog post</category></item><item> <title>Optimizely Opal Basics</title>            <link>https://kpbasics.com/?p=8092</link>            <description>A couple of weeks ago I had the chance to spend a day at the Optimizely Opal Partner Enablement Workshop hosted at the Horizontal Minneapolis office. It was a hands-on session focused on getting partners up to speed on Opal — Optimizely&amp;#8217;s AI orchestration layer — and walking through the building blocks you actually compose [&amp;#8230;]</description>            <guid>https://kpbasics.com/?p=8092</guid>            <pubDate>Fri, 22 May 2026 03:32:03 GMT</pubDate>           <category>Blog post</category></item></channel>
</rss>