Some feedback that we get with CMS is that the HTML editing control is not up to the UI expectations / richness that users are now accustom to after using the modern editors like FrontPage. Another complaint is that it cannot easily generate XHTML compliant tags which can cause issues in government and other verticals where accessibility is key.
I first addressed this by developing my own custom placeholder control to share with the CMS community - this was then picked up and owned by Artemis who published it here on GotDotNet.
Whilst this control got some great feedback - what we really need is a rich CMS editing control that has premier levels of support and features such as cross browser support, skinning, localisation, full table editing and a rich api for programmatic control. Also important is that it has a roadmap for continual advancement.
The good news on the horizon is that Arpan, Stefan and I have been working with a commercial organisation to address this and we are now very close to having an exciting announcement. Our intention is for the legal stuff to be completed and the news to go public on June 1 - but if you are at TechNet then I suggest you attend Arpans sessions as I believe he is aiming to give an early update / glimpse. And if you are worried about the $$$ then don't - I promise you will like the price .
Previous Topic
.