Portal Engine
Version 3.x > Portal Engine > Building Non-WYSIWYG Interface For Editable Text Controls? View modes: 
User avatar
Member
Member
Dissenter - 10/22/2009 12:43:29 PM
   
Building Non-WYSIWYG Interface For Editable Text Controls?
Hello all!

We're running a Kentico 3.1a site that primarily features pages with 2 Editable Text Controls on each. For whatever reason - and the reason may have to do with being WYSIWYG and loading up the entire page every time - the Kentico content editor interface is slow - very slow. So slow, in fact, that a number of users are refusing to use it, writing HTML in Notepad or other editors and then pasting it in to the Editable Text control.

Obviously this isn't good. We want people to feel good about working in the system.

So we had an idea; what if we built a regular WebForm that would simply display 1 textarea for each editable text control? No WYSIWYG, no loading up all the design elements and all the repeater controls from the sidebar. Just text editing.

We're pretty sure it could work, and have been looking at the database to find out where we'd need to read & write data for each page from. But we're also kind of new to Kentico, so I decided to post here to see if anyone else has done this sort of thing and get some pointers about what to watch out for.

Has anyone else done this?