One design idea was that css (and templates) need to be under version control. That is why we kept the css (and templates) separate from the content-editing.
When your designers can use mercurial, then there is another way:
place your site under mercurial version control
clone your site on the server and install the site as usual
go to the zotonic status site (just use the ip address or a non-configured dns name)
log on (use the password in the zotonic priv/config file
Now you will see an "update" button behind your site. When you click this button then a hg pull -u of your site is performed. This will publish the new css (and other parts).
One design idea was that css (and templates) need to be under version control. That is why we kept the css (and templates) separate from the content-editing.
When your designers can use mercurial, then there is another way:
priv/configfileNow you will see an "update" button behind your site. When you click this button then a
hg pull -uof your site is performed. This will publish the new css (and other parts).