It really depends on how your environment is setup, for example at my last place we didn't roll out a full Development/QA/Staging environment until 9 months after the project went live. Having your css/js in RedDot makes development easier because you can use the Draft variants to publish draft css/js to the appropriate servers. In our case we had alot of sub domains on for every section of the site practically, we also used fully qualified URLs when RedDot published files. It pretty much makes things a one click deploy or one click publish all, you don't have to remember what directories to check out.
On Nov 11, 4:56 am, "Bobby Jack" <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm working with a RedDot project that I picked up about a year ago. The > project always had management of not only HTML but CSS, javascript, and PHP > files. However, I'm strongly considering removing such files from RedDot, so > they can be maintained as actual files with all the accompanying benefits > (powerful UNIX toolset, decent text editor, revision history, etc.) > > I'm curious as to what standard practices are out there on how to manage > such files, for example: > > 1. Do you store CSS, PHP, etc. in RedDot or in a proper source control > system (cvs, svn, etc.)? > > 2. If you use a SCS, do you also store certain images in it (e.g. background > images referenced from your CSS)? > > 3. Are there any benefits in storing such files in RedDot? Is it possible to > make any kind of useful interface for updating, say, CSS? > > Many thanks for your time, > > - Bobby --~--~---------~--~----~------------~-------~--~----~ 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] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
