What is the best way to organize work with assets?

Question

css

Hello, I have a question about organizing storage and working with assets (js, css, sprites).

There is a project on Yii, the code is all in the git repository, there are no problems with it. Assets are stored on a separate subdomain (static.***), where the sider client uploads all js, css and layouts via FTP. This situation has ceased to suit for the following reasons:
- there is a possibility of dropping the production,
- it is very busy to glue and compress assets,
- there is no team work, although sometimes you want to get into css yourself and fix something.
But there is a tangible plus:
+ you can always view layouts from anywhere (everyone works remotely) and point out to the layout designer on his mistakes.

I would like to remake this scheme, tell me, please, how would you do it? I wanted to make a separate repository, but something stops me.

Answer 1

Keep all code in one repository. And to make it easy to glue and compress, write a script to automate these operations + upload to the static.*** server.

Answer 2

Store in the static folder of the main repository, what's the problem? Naturally, it is necessary to glue automatically, and not by hand. For simple projects, the gluer is written in 10 minutes in bash.