Fwiw.. We have taken to hosting css files in a central location and hardcoding the link back to them. We do manage a unique css file as a content class in cms but it's purpose is just for extra styles unique to a site.
Otherwise a screen css file as a content class linked to an anchor, or in v9 a container to help with mozilla rendering and set to show link only, works ok. Chris Nixon 4792364930 -----Original Message----- From: Ingo Hillebrand <[email protected]> Sent: Wednesday, November 18, 2009 5:21 PM To: [email protected] <[email protected]> Subject: Re: RedDot and CSS: A better way > Anyway, I wanted to get some feedback from the community before I give > it a try since it seems a little too good to be true and I feel like I > might be missing something. Anyone have any thoughts? i still have doubts concerning your solution with static css files. In most of our projects are multi lingual, so you have to build a seperate css file for every language - if i understood your approach. Corrections in the css file is everytime a little bit annoying, but this task is done by our frontend-developers - not the reddot-administrator. Greetings, Ingo -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=.
