T

2

8

What's the preferred or best method for integrating compass with susy or blueprint into a django project?

Tantamount answered 5/5, 2011 at 15:20 Comment(0)

I

8

Your best bet is to use django-css, a fork of django-compressor which also does css compilation of SASS. Once you have that plugged in, you can use compass, susy and blueprint as normal, and they will be compiled by django whenever it detects an updated version of the source files.

EDIT: If you are deploying on a pure python host such as ep.io, you will want to research how easily these build into cleverCSS (Pure python SASS&SCSS compiler)

EDIT 2:

This info has dated. django-compressor is now the best option as it has the preprocessing facilities built in, and it will be able to bundle up the files for you too ;)

Incarnadine answered 6/5, 2011 at 6:18 Comment(1)

@patrick This is incorrect, CleverCSS is a pure-python alternative to SASS, not an alternate compiler for it. – Audsley 31/8, 2013 at 15:5

R

28

We've chosen to avoid automatic runtime sass/compass compilation, and instead simply use "compass --watch" in development and commit both Sass and the generated CSS to the repository. Then there is no special machinery at all required in your Django project; you just handle the CSS files as you normally would.

This has several advantages for us:

Removes an entire additional chunk of moving parts from our deployment and production server infrastructure: no need to have a full Ruby stack, plus Sass, Compass, and any other required gems on our production servers. Making production servers simpler is A Very Good Thing. Also, no issues deploying to pure-Python hosting.
No mysterious subtle display inconsistencies between one developer and another, or between development and production, because of minor differences in something like a Compass plugin gem version. Everyone sees the same CSS. Differences between developers' Compass environments are caught quickly, because they show up right away as unexpected changes in the pre-commit diff of the generated CSS.

The disadvantage, of course, is committing generated code to the repo, which is generally frowned upon. We haven't seen any actual problems as a result of this, though. Nobody is tempted to edit the generated CSS directly; we all know that we use Compass. The advantages definitely outweigh the disadvantages, for us - we've never had the slightest temptation to switch to an integrated approach like django-css.

Rugging answered 9/5, 2011 at 16:14 Comment(2)

This is great as the designer/front-end-dev as well. I have complete control of the css-generation process without needing to touch the server. I do my thing, commit it, and it will just work. – Flyspeck 9/5, 2011 at 16:20

Extended answer on the Compass blog: compass-style.org/blog/2011/05/09/compass-django – Flyspeck 10/5, 2011 at 0:39

I

8

Your best bet is to use django-css, a fork of django-compressor which also does css compilation of SASS. Once you have that plugged in, you can use compass, susy and blueprint as normal, and they will be compiled by django whenever it detects an updated version of the source files.

EDIT: If you are deploying on a pure python host such as ep.io, you will want to research how easily these build into cleverCSS (Pure python SASS&SCSS compiler)

EDIT 2:

This info has dated. django-compressor is now the best option as it has the preprocessing facilities built in, and it will be able to bundle up the files for you too ;)

Incarnadine answered 6/5, 2011 at 6:18 Comment(1)

@patrick This is incorrect, CleverCSS is a pure-python alternative to SASS, not an alternate compiler for it. – Audsley 31/8, 2013 at 15:5

EDIT 2:

EDIT 2:

Recommended topics

Hot tags