When I work, the design and development departments are completely separate, but we (the design departments) are responsible for managing the CSS for our sites. As a rule, new CSS should be released to the production server much more often than the new site code. Because of this, we deploy CSS separately, and it lives outside the control of the source.
However, recently we have encountered several problems when the new CSS is not synchronized for releases on the site, and in general the process is a huge headache. I insisted on getting CSS under some kind of control over the source code, but I have trouble finding a good deployment method that makes everyone happy. Our biggest problem is managing the changes that affect the current parts of the site, where CSS changes must go live before the site changes, but not break anything on the existing site.
I will not go into the smallest details of the strange culture between designers and developers here, but I was wondering what experience others had in managing large volumes of CSS (50+ files, thousands and thousands of lines) that need to be constantly updated and issued regardless of releases site.
source
share