so be the first one to create a discussion :-)

---

Cheers, Philipp Becker, Peppertree Solutions

Thank you Philipp for your responses.

I understand that editor.css can provide the contextual styling for a portal now.  I am actually after a special css file that I can specify in the configuration of each *page* not simply each portal.  In fact, I would rather not have to specify page.css...  I would rather have the editor mirror the skinning feature that cascades style sheets locally for each page.

Perhaps you are not familiar with the DNN skinning architecture?  One file, editor.css, in the skin path does not emulate the architecture of a DNN skin where each page in the portal can use a different template within the skin.

Here's an example of a DNN skin folder with three templates:

skin.ascx
skin.css
home.ascx
home.css
detail.ascx
detail.css

The first one is the default.  The second one is called home and applies home.css after skin.css has been applied.  The third one is detail and applies detail.css after skin.css.

Trying to write the ascx so that all tags are unique between skin.ascx and home.ascx defeats the purpose of cascading skin.css and home.css.  The only way to furnish all tags in editor.css is to make them unique throughout the templates. 

I know the other editor providers do not provide a reasonable solution to skinning templates.  You have been the only one to respond with developer knowledge of your editor provider.  My belief is that if you approach this additional requested feature to support the DNN skinning architecture then you may solve a huge problem for the DNN community:  there is no WYSIWYG editor for DNN.  All our customers want to be able to edit their content as it looks on every page without having to pay us to do it.

Regards,
Guy