Django alternatives to Gulp

[Keyra]

Hello,

Iam currently moving an already existing project to django. So far, Gulp
has been used to organize static files and assets there. Although there
seems to exist solutions like django-gulp, I would like to switch to a
more "python/django way" in organizing my static files, but I am still
inexperienced how static files are best handled in Django.

Should I use compressor with precompilers? And which precompilers for
sass for example? Is django-sass-processor for example a precompiler
that can be used together with django compressor?

I'm still a little confused about how I'm going down the right and clean
road. For example, I find it strange that even in django *.scss files
are treated as static files (and stored in the appropriate folder).
Because basically they are not static files if they still need to be
compiled.

Thanks for suggestions,
keyra

[Chris Routh]

I would recommend moving to webpack and using https://github.com/owais/django-webpack-loader to manage loading of webpack files. This allows you to precompile your webpack resources and include only the compiled js/CSS and the webpack stats file. Django will use the webpack stats file to determine what js and CSS to serve and this method will support cache busting.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b1f0754b-ea65-986a-caed-0449bc3ad6c6%40posteo.de.
For more options, visit https://groups.google.com/d/optout.