Thanks for the suggestions! I'll share what our plans are at the moment.
We believe that the RadEditor settings are not something that you change on daily basis, even more - once you set it up, it stays like this until the next CMS comes :) At least this is what our experience shows. For example, the RadEditor on telerik.com's backend is not changed since the first launch of the web site. Even after web sites rework in form of new themes, the CSS is the only thing that is modified, but often designers tend to change the .css files themselves, they do not touch the editor.
So in general, there are two main editor instances - one for the content creation and one for the comments. Why not provide the people a way to quickly change them? Then of course, someone may want a specific instance of the RadEditor to behave differently, so we need a way to create a configuration and assign in to any instance. This is a rare case compared to the to main editor instances (content creation and comments), so this can be advanced setting. Every custom configuration could have its own name so the assigning of the instance to the configuration is easy.
Based on this assumptions, the attachment shows what we are planning to have in the first version of the feature. We also assume that the configurations will be done by technical people - the content creator won't be able to set styles in the Paragraph dropdown since he lacks in web design skills. As for the Bold/Italic/Etc buttons, they are required for absolutely every editor. What do you think?
I am moving the discussion in the UX forum.
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items