Hi Rob

Thanks for your detailed answer. The dynamic style generation works well, I had problems with the filter. After clearing the custom settings everywhere and a new begin, the filter works. Now I try to build a REGEX like "Nothing except it begins with MyStyle...". It's not important, but it would shorten the filter expression and is independent from new DNN-Styles and other skins.

Next step are the toolbars, the User with Content Editor Role should see only the necessary functions. Your answer a very good guidance for this step.

I divide your opinion to the GUI. A good and understandable GUI to build is a challenge.

A wish to the developer team:

For the users it would be useful, if the integrated assistance were more meaningful.

An example:
I click on the Question Mark by 'Style list generation mode'.
It appears 'Determines how the style list will be generated'.

I click on the Question Mark by 'Settings Type'.
It appears 'Select the type of setting to modify'.

This is what I can see without help/hint also. Usefull would be a short explanation about the options. I believe, this also the questions in the forum would reduce.

So far so good...

Thanks to the developer team for your work. The FCKeditor Provider for DNN is a large step toward a CMS for Content Editors.

Greetings and have a nice weekend!

bimper

 Rob (All),

Thanks for the thorough post about customizing the FCKEditor. I've been playing with it a lot lately to hone it for "fool-proof use." I was just researching and found this post. Thought I'd add to it with what I've been implementing.

A couple of things I have been doing that seem to help (and are slightly less setup) are to:

1.  Modify the FCKStyles.xml to be a defined list of semantic markup tags I want my users to use (h1-h4, a few others)
2. Modify the Web.config to to set StylesDefaultMode= to "static" so that it uses my cutom list of styles by default
3. Keep the CSSDefaultMode="dynamic" so that it uses the styles defined in my skin's CSS and applies these styles to my custom list of Styles (see #1).
4. Additionally, I modify the DefaultDNN Toolbarset to only include the buttons/actions that are intuitive and generate semantic markup (no inline styles to help the basic content admins away from killing design).