I've started to build a series of content classes for css so I can quickly parse and edit sections like basic layout, typography, colors and background images. I dump all of them into another content class that is just a container so when the css actually gets published it's still just one file.
The main problem may be that the person who is generating the CSS isn't also working in RD. I'd work at getting him more involved in the CMS process. That would actually help both of you. One, he'll understand better what you do and two, you'll hopefully have a bit more influence on how things are coded. I'm not sure there is a way to avoid what you are doing now. Even if you do separate the static out, how do you plan to upload the images to the site? Wouldn't you need to do that manually then outside of RD? What happens 3 years from now if you aren't on that project? Are you going to document that well enough that they will understand those files aren't in the asset manager? That would be my biggest concern. On Nov 18, 12:11 pm, NP <[email protected]> wrote: > I have always had an issue with RedDot and stylesheet handling. > Whenever CSS changes have to be made, i generally receive changes made > by front-end developers to static CSS files, which I then have to diff > with the files on the RedDot server. This is a miserable diff because > RedDot does all kinds of crazy things with white space, not to mention > that all the images have to be replaced with placeholders (or you can > put your images into the file system, but then they have to be > repeated on the CMS and publishing targets). > > On my next project I was planning on trying a new tactic: separate CMS > and static sites. The gist of it is that all style sheet references > would be full URLs referencing the static site, like: > > <link rel="stylesheet" type="text/css" href="http://static.mysite.com/ > mystyle.css" /> > > instead of re-creating all the style sheets in RedDot and inserting > placeholders for them. This way, when the front end work is done, the > changes get pushed to that static site and RedDot will start reading > those styles in immediately, eliminating the need for long and error- > prone updates. > > 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? -- 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=.
