<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by opti dev</title><link href="http://world.optimizely.com" /><updated>2026-04-12T17:00:00.0000000Z</updated><id>https://world.optimizely.com/blogs/opti-dev/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Optimizely CMS 13 ES6 Editor Descriptors</title><link href="https://mark-hall.me/blog/optimizely-cms-13-es6-editor-descriptors/" /><id>&lt;h2 id=&quot;introduction&quot;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;With the release if Optimizely PaaS CMS 13, there is a &lt;a href=&quot;/link/88f4f6f6cfa74053a471ea090758a4c0.aspx&quot; target=&quot;_blank&quot;&gt;new way&lt;/a&gt; to create UI editor descriptors to allow to custom UI with managing a property. These have been one of the reasons partners can make the jobs of editors much easier by proving a custom experience when entering content. In the previous versions all the descriptors had to involve dojo. Optimizely provided a way to use react or other tools but you needed to create a dojo wrapper around the component. This post will provide and example vite.config.ts file and command to package your editor descriptors.&lt;/p&gt;</id><updated>2026-04-12T17:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Deploying to Linux in SaaS (Configured) Commerce</title><link href="https://mark-hall.me/blog/deploying-to-linux-in-saas-commerce/" /><id>&lt;p&gt;With Optimizely SaaS (Configured) Commere now suporting net8.0 extensions dll, you will need to make a small tweak to how you distribute you extensions dll.&lt;/p&gt;</id><updated>2026-04-10T17:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>lunchin Optimizely Cloud Extensions now supports CMS 13</title><link href="https://mark-hall.me/blog/cms-13-support-lunchin-optimizely-cloud-extension/" /><id>&lt;p&gt;lunchin.Optimizely.Cloud.Extensions version 2.0 has been released today which adds support for Optimizely CMS 13.&lt;/p&gt;</id><updated>2026-04-09T17:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Net8 Local Development Without Docker In Saas Commerce</title><link href="https://mark-hall.me/blog/net8-local-development-without-docker-in-saas-commerce/" /><id>&lt;h2 id=&quot;introduction&quot;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Now that Optimizely SaaS (Configured) Commerce has released &lt;a href=&quot;https://support.optimizely.com/hc/en-us/articles/38956988397197-August-2025-release&quot; target=&quot;_blank&quot;&gt;net 8 support&lt;/a&gt; and &lt;a href=&quot;https://support.optimizely.com/hc/en-us/articles/41857331372941--NOTICE-Configured-Commmerce-now-uses-Linux-based-environments&quot; target=&quot;_blank&quot;&gt;updated their infrastructure to run on linux&lt;/a&gt;, we are starting to move some of our clients to .net 8 and linux hosting. This means we will need to be able to run .net 8 version locally, which according to &lt;a href=&quot;https://docs.developers.optimizely.com/configured-commerce/docs/net8-local-development-environment&quot; target=&quot;_blank&quot;&gt;offical docs&lt;/a&gt; requires docker desktop. While I love docker for creating images for deployed services, I hate using it locally because it consumes alot of diskspace, memory, as well as docker desktop no longer being free. This post will guide you on you can run locally .net 8 without using docker.&lt;/p&gt;</id><updated>2026-04-08T05:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce</title><link href="https://mark-hall.me/blog/using-azure-devops-pipelines-in-saas-commerce/" /><id>&lt;h2 id=&quot;introduction&quot;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;When working with SAAS Commerce &lt;a href=&quot;https://docs.developers.optimizely.com/configured-commerce/docs/build-service-v2&quot; target=&quot;_blank&quot;&gt;build service v2&lt;/a&gt; your currently need to use a github repo with configured branches to start deployments. Any time a push is comitted to the configured branches the build service will start a deployment.&lt;/p&gt;</id><updated>2026-04-04T05:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Optimizely CMS 13 First Impressions</title><link href="https://mark-hall.me/blog/cms-13-first-impressions/" /><id>&lt;h2 id=&quot;introduction&quot;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;This week Optimizely released the long awaited CMS 13. I upgraded my Optimizely extensions package to CMS 13 and found some interesting things I needed to do to update my package. I will use this blog post to document some of those findings.&lt;/p&gt;</id><updated>2026-04-02T05:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Introducing lunchin Optimizely Cloud Extensions</title><link href="https://mark-hall.me/blog/introducing-lunchin-optimizely-cloud-extensions/" /><id>&lt;p&gt;Today I proud to announce the release of two new packages to the Optimizely NuGet feed.&lt;/p&gt;</id><updated>2025-10-04T05:00:00.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>