It is possible to configure what css-files the editor, as well as the XForm editor loads and uses. This can be configured in two ways.

  1. As a property on the page.
    This property can be either a dynamic or a standard page property. The property needs to be named UIEditorCssPaths and in the form of a comma separated list of paths to the stylesheets. Setting this in page or dynamic properties will override the correlating setting in Web.config.
  2. As a setting in Web.config.
    If no property is set the fallback will be to use the setting uiEditorCssPaths in web.config. This setting is also in the form of a comma separated list of paths to the stylesheets. The web.config setting will be used if no property on the page is set to point out alternative stylesheets.

Sample of a comma-separated css-path list:

"~/Templates/Public/Styles/Glossy/Editor.css, ~/Templates/Public/Styles/Glossy/Editor2.css".


Sample excerpt of a web.config assigning alternative stylesheets:

CopyXML
<sites>
  <site description="Example Site" applicationId="/LM/W3SVC/1/Root/EPiServerSample">
    <siteSettings 
        pageRootId="1" 
        pageStartId="0" 
        uiEditorCssPaths="~/Templates/Public/Styles/Glossy/Editor.css" 
        />
  </site>
</sites>