2010/1/14 David Breitkreutz <david.breitkreutz@...>:
> Since Kupu is configured to not be themed by Deliverance (rightly so), any CSS introduced to theme a Plone site by Deliverance isn't accessible/visible when editing some content.  This is understandable as Kupu's page isn't get themed at all and hence any links to CSS files aren't coming along for the ride either.  So, the end result of this is that users are editing content in a WYSIWYG editor and being presented with default stylings from Plone and the resultant output (depending on your Deliverance theme) probably differs greatly.  Hence, confused users!
>
> Now, my solution was to customise the "emptypageresources" template within Plone and insert the link to my Deliverance CSS file like so:
>
> <link href="site.css" type="text/css" rel="StyleSheet"
>      tal:attributes="href string:${context/@@plone_portal_state/navigation_root_url}/static/theme/site.css;" />
>
> Now, the Kupu page has the link correctly and the styles are functional.
>
> This feels to be a very common use case, but I can't seem to find any other suggestions on a workaround/solution.  Are there any better solutions to this?    I'd have to think that this is likely to be a widespread issue, though.  It's definitely not something that should happen if we can have the WYSIWYG editor actually be WYSIWYG.

The best solution is to add your static css to Plone's portal_css.
Then you benefit from the css merging and minifying we have in
Resource Registries.

Laurence