The ClientEditingClass is the path to our upcoming javascript file, from the Name value we added in our nfig. Notice how we assign the name IconPicker to the UIHint attribute. You will have to change your namespace according to how you have your project setup. Public override void ModifyMetadata(ExtendedMetadata metadata, IEnumerable attributes)Д¬lientEditingClass = 'nansen/IconPicker/widget' Д«ase.ModifyMetadata(metadata, attributes) Public class IconPickerEditorDescriptor : EditorDescriptor This registers the new widget with EPiServer and makes it easy to implement as a property on pages with the use of an UIHint.Д¬reate a file called IconPickerEditorDescriptor.cs and add the following: using The next thing we want is to create an Editor Descriptor. That way it's easy to see what you have added yourself and what you might have installed through Nuget etc. I like to namespace it so I know that all our custom scripts are within the same directory. The finished widget nfigДЇirst of all, we need to setup nfig with a path to where we will host our new widget It will, in the end, be a simple string property that we'll use to generate the correct classes to a span element that shows the icon in the frontend.

In this post we will be creating a widget for easily selecting an icon from the amazing Font Awesome library. For the most part, you don't even need to do everything through dojo, as you will see. You can start small, and still make incredibly useful widgets. But do not fret, as you most often don't need to be a black belt in the EPiServer dojo at all. It might seem like a big hurdle to dust off skills you probably didn't even pick up circa 2012, when Dojo was at its height.

Font picker js