November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
Follow bloggers on Optimizely World to get the latest from people who know all about the Optimizely platform! You will find blog posts from the entire Optimizely community, as well as from the Optimizely development teams.
Start blogging - create your own blog (requires log in)
Manage your blog posts on Optimizely World (requires log in)
Rules for blogging on Optimizely World
Introduction to Optimizely .NET 5 Series Welcome everyone to a series of posts about the upcoming releases of .Net 5 compatible commerce and content clouds. Getting started with upgrade-assistant Starting a new project Working with docker and...
Testing an Optimizely CMS or Commerce site requires both traditional web testing skills as well as an extra set of CMS-specific approaches to ensure your implementation is doing what it does best – delivering great digital experiences that connect...
With the fifth installment of the " Into Foundation-Spa-React " series, the focus shifts from the backend and high-level frontend implementation towards one of the key capabilities the SPA offers to enable you to not only provide content from with...
Background Inline JavaScript is discouraged to use nowadays due to security concerns and optimization requirements. In fact, inline script is a huge problem if a strict Content Security Policy header has to be applied. However, Episerver...
There’s a lot happening in the community at Optimizely. The Optimizely community continues to grow and our community slack now counts over 2800 members, with new professionals joining daily. The Optimizely MVPs (a group of 70+ technical c...
Yesterday Optimizely announced the addition of 11 new Most Valuable Professions - OMVPs! Congrats and welcome!
Content Manager is finally updated, and it's now possible to create and publish content without going through a bunch of meaningless steps.
Forms 4.30.1 has a bug that can unexpectedly delete form submission data if retention policy is set and the bug has only been fixed in 4.30.3. If you have already deployed a solution using Forms 4.30.1 or 4.30.2, you should upgrade Forms to 4.30.3...