Our company is a registered partner, and one of the biggest shortcomings of Kentico from my perspective as a designer and user is the way that the FCK editor handles styles for content. I would go so far as to say that it is YEARS behind other editors that I've seen. There are 2 signifcant problems with the current methodology:

1. That the styles available in the "Styles" dropdown in the FCK editor apply to ALL sites.

2. That you have use an XML file to populate the "Styles" dropdown menu of the FCK editor.

If you are hosting multiple sites (all for different companies) as we are, it basically renders the Styles menu useless. So the only real solution is to go back to using font tags to style text. Not good.

I would recommend the following functionality in future versions:

When setting up a new site in the Site Manager, give the user the ability to designate a stylesheet for the FCK editor that is specific to THAT SITE ONLY. The styles in this stylesheet would then populate the "Styles" dropdown menu within the editor.

And also get rid of the XML intermediary.

Or, another option: perhaps just have the editor read the styles from a specific tag within the styleseet that is specified when a site is set up. So if someone designates "ABC Company Styles" for the Site CSS Stylesheet, they could then add a specific tag within that stylesheet like the following:

/*#Start--Editor Styles#*/

.TextHeader {
color: #000000;
font-size: 1.2em;
}

.TextBlueBold {
color: #1e4567;
font-weight: bold;
}

.TextRedBold {
color: #881f1f;
font-weight: bold;
}

/*#End--Editor Styles#*/


So the editor would read the styles between the Start and End tags, and use those styles to populate the "Styles" dropdown menu in the FCK Editor.