ITEM Editor is a grid editor for Umbraco 7. If you like the built-in 'grid layout' in Umbraco, you will love ITEM Editor.
Why? Because it's fast, stable, easy to work with, extendable, portable and based on many years of experience. We have built grid editors for Umbraco since Umbraco 4 and they have been used to create more than 200.000 pages so far.
Angular-based apps are by nature very fast and responsive. ITEM Editor is no exception. But we also made it very fast to get a developer's work done: Create new controls, widgets and layouts in a few clicks and use the built-in service to automatically create basic views for you, ready to be enhanced with your own HTML and presentation logic. Our MVC extension extends @Html with all the render methods that you need.
Yes, we do take our own medicine. This page was, like all other pages on this website, built with ITEM Editor. The image shows what the page looks like in backoffice. The green plus adds content.
Turn any Umbraco data type into a control and use it in your widgets. Get the strongly typed value using property type converters. Inject JavaScript when you need it - you can even run it in the backoffice, if you like, to make those videos, maps and galleries in your widgets come alive for a true WYSIWYG experience. Use the same views to render content both in the backoffice and on the public site.
Have you ever wanted to change something in a grid configuration, but been hesitant to do so, because you just didn't know what would happen if you did? We've got your back. When a page is opened for editing, it's content is compared to the configuration entities. So if you have eg. added or removed a column, renamed a widget or changed a control setting, ITEM Editor will find out and update the page model accordingly. It will even show warnings to the editor, telling what's going on. When a public page is rendered, it will just fail silently if something is missing. No compromising error messages here.
So you created a lot of controls, widgets and layouts and now you want to use them on a new site? No problem. Just click 'Export' to get all entities as JSON. Then click 'Import' on the new site, paste the JSON and select which items to import. Finally, copy the views, scripts and stylesheets that you need for presentation. The configuration editor will even generate a report, telling you if any files are missing.
ITEM Editor does not depend on any specific grid framework. You can use it with any grid framework you like, or just write your own CSS. Bootstrap fan? Just add 'container' or 'container-fluid' classes to your layouts, 'row' to your rows and 'col-md-xx col-sm-xx' classes to your columns and you're done.
ITEM Editor comes with localization strings for the da-DK and en-GB cultures, but it's very easy to localize to any other culture. Just open localization.js, copy an existing culture section and use it as a template.
With a few lines of JavaScript, you can change editor permissions on-the-fly, based on the current page, current user and current editing context. You can for example disable all add, delete and move controls if the user type is 'writer' or hide/disable some of the layouts and widgets in the add dialogs based on the current document type.
Want to prevent all editors who use 'Danish' as backoffice language and have e-mail addresses ending with 'itemsystems.dk' from adding widgets to the second column in a four-column layout on the home page, but only if today is a Sunday and it's after 10am? Probably not. But if you do, it's a oneliner:
return (current.culture === 'da-DK'
&& current.user.email.endsWith('itemsystems.dk')
&& context.layout.alias === 'fourColumns'
&& context.column.alias === 'row1_col2'
&& current.nodeTypeAlias === 'homePage'
&& new Date().getDay() === 0
&& new Date().getHours() >= 10) ? 'disable' : 'show';An ITEM Editor license costs 199 EUR per top level domain. Your development and staging domains will be included in the license file as well.