Optimizely’s new PowerShell script, Scaffold‑OcpOpalTool.ps1, automates the entire OCP Opal Tool setup—installing Node, Git, Yarn, the OCP CLI, configuring credentials, and generating a full TypeScript scaffold with ESLint, an API client, lifecycle handlers, a health‑check, and boilerplate files—cutting setup time from hours to minutes. The script and a walkthrough video are available in the blog’s description.
TLDR: Optimizely released **Scaffold‑OcpOpalTool.ps1**, a PowerShell script that auto‑sets up a full OCP Opal Tool project—installing Node, Git, Yarn, the OCP CLI, configuring credentials, and generating a complete TypeScript scaffold with ESLint, API client, lifecycle handlers, health‑check, and boilerplate files—cutting setup time from hours to minutes. The script is available via the blog’s video description.
Discover our latest tutorials on architecting AI with Optimizely CMS, a Tailwind CSS strategy for Visual Builder grids, memory‑efficient catalog traversal in Commerce, and a practical guide to AEO/GEO for creating content that’s both human‑friendly and AI‑ready.
Optimizely CMS 12 now gives developers two AI pathways: a custom integration via a provider‑agnostic service layer and event hooks, or Opal, the native AI engine that speeds up editor productivity and reduces maintenance. A hybrid strategy—using Opal for rapid content and campaign work while keeping custom services for domain‑specific logic and compliance—is the recommended enterprise pattern. Developers should also design AI‑ready content models, keep AI calls off the rendering path, secure API keys, and treat prompts as versioned, testable code.
Optimizely now introduces a Tailwind CSS strategy for rendering Visual Builder grids, simplifying layout management in the SaaS CMS. By using utility‑first classes, developers can quickly build responsive, consistent grid structures without writing custom CSS. This approach streamlines styling within Visual Builder, making grid design faster and more maintainable.
Memory‑efficient catalog traversal is introduced to handle large Optimizely Commerce catalogs without exhausting memory. Part 1 explains how to build a service that streams product data, enabling scheduled jobs like PIM syncs or bulk updates to process thousands of items safely. Developers can now replace the naive “load all into RAM” approach with a scalable, memory‑friendly pipeline.
AEO/GEO is a new approach for creating content that’s both human‑friendly and AI‑ready. Optimizely developers should design pages so that search queries can be answered by AI tools, making information understandable, citable, and easily parsed by machines. The guide explains how to structure content to meet these dual‑audience requirements.
Introducing “Virtual Text,” a free, open‑source Optimizely CMS plugin that lets you create, edit, and serve root‑level text files (robots.txt, ads.txt, security.txt, etc.) directly from the CMS, eliminating file‑system edits and deployments. It supports multi‑site/hostname configurations, Azure Table/Blob storage, automated non‑production indexing blocks, and integrates with CMS permissions so editors can manage these files without gaining broader admin rights.
Optimizely developers now have a free, open‑source “Virtual Text” plugin that lets you create, edit, and serve root‑level text files (robots.txt, ads.txt, security.txt, etc.) directly from the CMS, eliminating the need for file‑system edits or deployments. The package supports multi‑site/hostname configurations, Azure Table/Blob storage, and includes a RobotsTxt extension that automatically blocks indexing in non‑production environments. It also integrates with Optimizely permissions, so editors can manage these files without gaining broader CMS admin rights.
This release upgrades the RSS Feed Integration library to v3.0.0‑beta with full Optimizely CMS 13 support, requiring a scheduled job re‑run to regenerate XML files. Additionally, CmsContentScaffolding.Optimizely v1.8.5 adds a refreshed unit‑testing helper that automates content scaffolding, cutting test‑setup boilerplate, along with small bug fixes and usability tweaks—simply add the NuGet package to streamline your Optimizely testing workflow.
The RSS Feed Integration library has been upgraded to **v3.0.0‑beta**, adding full support for Optimizely CMS 13. The update changes the feed‑storage path (SiteDefinition → Application no Id) so you must re‑run the scheduled job once after upgrading to regenerate the XML files. Use this beta to validate RSS behavior ahead of the final CMS 13 release.
Optimizely’s CmsContentScaffolding.Optimizely v1.8.5 drops a refreshed unit‑testing helper that automates content scaffolding for the CMS, cutting down test‑setup boilerplate. The release focuses on small bug fixes and usability tweaks that make it easier for developers to spin up test content. Add the package via NuGet to streamline your Optimizely testing workflow.