Content Area property items allows to select Display Options. Display options let Editor specify how item should be renderred in the view mode. When adding content to a Content Area, we usually know which display option will be the best choice based on content type. For example our ButtonBlock will be best displayed as Narrow while Editorial block as Wide. That’s why I prepared a small javascript snippet to set Content Area default display options.

(more…)

Over the years, several articles have been written about the ColorPicker property editor. I also decided to look into this topic. I wanted to create something modern, simple and configurable. That’s why I used a simple HTML input color wrapped in a dijit widget.

(more…)

A while ago I implemented a HideTabs addon that allows to hide tabs and properties in edit mode.

I converted it to .NET Core version and now it can be used in CMS 12.

Nuget package can be downloaded from nuget.optimizely.com

The source code is available on github.

In this article I’d like to show a custom implementation of image property. There are already few blog posts and code snippets about improved image editor, but most of them focus on showing thumbnail for selected image. In my code I refactored image selection dialog and replaced content tree with media component. It can be useful for Editors, because media component has many features that can improve their work.

(more…)

In one of my previous articles I showed a small improvement for Editors. They could create a page shortcut using D&D from page tree. This time I’d like to show another feature related with D&D. I implemented functionality of populating local blocks properties from shared block instance. Editor can drop shared block on the local block to copy all properties.

(more…)

There are few ways for grouping properties in edit mode. You could place properties that should be grouped in a separate tabs. Another option is to define new block type that contains related properties and use the block on page. But when you don’t want to have too many tabs or block types you could try to use my custom implementation. In this article I will show functionality of grouping properties using header.

(more…)

Today I’d like to show you a new extension that allows to programmatically hide tabs and properties in edit mode. Using this feature, the editor won’t see the unused controls when working with content.

(more…)

When editing complex types like ContentArea or XHtmlString it would be good to have preview of all available property value versions. The Editor would be able to revert the property to older version or copy property from other language or even another page. In this article I will show an extension to All Properties mode that allows reverting property value to a specific version.

(more…)

By default Episerver use dijit checkbox when rendering boolean property. I wanted to add a possibility of defining labels for true and false values. That’s why I prepared a switch button property that displays configurable label for the selection. It can be useful to highlight the selected value.

(more…)

Not all properties are visible in the page template and can be edited using PropertyFor helper. Some of them have to be edited through All Properties mode. I thought that it would be useful for editors to have quick access to some properties in On Page Edit. I introduced a way of adding additional header properties.

(more…)