Editor Enhancement Toolkit

  0 rating
2/16/2017 2:11:58 AM
7/25/2017 11:06:25 AM
Provider: Eric Stafford


The Editor Enhancement Toolkit is a module that's purpose is to improve the Content Author's editing experience.  

Disguise Architectural Mistakes

Using the rules engine, we can target items based on the conditions like the ones found in “Item Hierarchy,” “Item Attributes,” “Item Information,” “Security,” etc., then choose an action to achieve the desired result.

  • Display Field Name As– Have a field that is not named accurately in some of the areas it is used? This could cause a lot of confusion. Use the conditions to target that item, on the action, enter the original field name, and give it a new name*.
  • Display Section Name As– This action functions the same as the “Display Field Name As” action.
  • Hide Field/Hide Section– Sometimes it’s unavoidable due to tight deadlines, changing requirements, and/or bloated templates filled with a lot of fields or sections that often go unused in certain areas of the site. These actions will help reduce the bloat; just set up the rule conditions to target those unnecessary fields and sections and when the conditions are met, the action fires, hides those areas defined, and hopefully reduces the content author’s confusion and anxiety moving forward.
  • Set Field Name’s Short Description– This action gives you the option to modify the short description if needed.
  • Set the Source for Field– I am aware that on certain list fields you can use Sitecore queries and specify multiple datasources, but I thought why not provide another option?  Example: A developer is developing a multi-site implementation of Sitecore and they’re following the principles of Helix to the best of their ability. In the ‘Foundation’ templates, the dev decides that they want to reuse a template that contains an image field across all the sites. Normally the source field should point to the site’s image folder unless the images are used globally. In this instance, the images are site specific. The dev decides to be lazy and points the source to the root media library item. Good news; this action allows you to change the source depending on the conditions you define. Now if this template is used on Site A, it will pull from the Site A image folder that you defined on the action.
  • Map File**– This action comes in handy when bulk changes are needed. Using XML, fill in the nodes with the correct data. The directory that this file is placed into is customizable in a config setting. After the editing is complete, place the file in the defined location and then enter the filename in the action.

Create a "Virtual Section"

The virtual section doesn’t exist in Sitecore; it’s defined in the XML.** Currently its only function is to act as a container for an author’s “most favorite” of the “Standard Fields.”  Leaving the “Standard Fields” located in the “View” ribbon is unchecked allows the Virtual Section to appear under the ”Quick Info” section.  The fields that are defined in the XML are removed from their normal locations and appear in this new section. If the “Standard Fields” checkbox is checked, the fields will move back to their original location and the Virtual Section will no longer be visible.


Release notes

Read more Back
Code examples

Solution screenshots(0)


Reviews (0)

Sort by: Date Most votes
  • Profile Avatar

    Level: 0

    x0 x0 x0




    Was this helpful?


Comments (0)

Sort by: Date  Most votes

Leave a Comment

Comment must be field in
Post comment

Write a review

Title can't be empty
Review can't be empty
Post review


Title Description Download Action

Add File