SaaS CMS has officially launched! Learn more now.
SaaS CMS has officially launched! Learn more now.
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
Recently we have developed new tag system to make it more convenient for you when looking around for related topics. As you create new topic, don't forget to add tags by input several keywords in the input field. Currently we add tags with newer...
At my current client’s we are building a large platform serving several EPiServer multisite installations with common code. Consolidating how we work with EPiServer Find, we ran into a bit of trouble. My collegue Svante Seleborg did all of the hea...
How do you give editors a better support for creating a telephone links, that can be used for endusers to do activate phonecalls by clicking a telephone link. I have created a plugin for TinyMCE that can help with this.
How do you give editors a better support for creating a telephone links, that can be used for endusers to do activate phonecalls by clicking a telephone link. I have created a plugin for TinyMCE that can help with this.
For an old project many years ago I created a tool for generating web.config redirects for clients. Recently we enhanced it so that it's a lot better and we have also added auto generated postman redirect verification tests in. I thought the...
Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties. The default implementation is really naive: public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData) { return...
Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties. The default implementation is really naive: public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData) { return...
Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties. The default implementation is really naive: public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData) { return...