Before the migration of grunt, we first made sprites from the less files (f.e. main.less → main-sprite.less) and then compiled the less-files to css (see history of fabfile.py).
The first task seems not to be done by grunt. So if a change is made to the original-file (main.less), it will not appear on production systems, because the sprites are not updated. (the problem will not occur in the dev-environment, because the less (without sprites!) is compiled via JS in the browser) Hopefully, there is a good grunt-package for that…
Before the migration of grunt, we first made sprites from the less files (f.e. main.less → main-sprite.less) and then compiled the less-files to css (see history of fabfile.py).
The first task seems not to be done by grunt. So if a change is made to the original-file (main.less), it will not appear on production systems, because the sprites are not updated. (the problem will not occur in the dev-environment, because the less (without sprites!) is compiled via JS in the browser) Hopefully, there is a good grunt-package for that…