django-compressor VS django-guardian

In general, you can use almost any plain JS library by simply loading it in your view template. For forms specifically, you can write custom widgets and define dependencies to libraries via form assets. django-compressor might be worth a look if you go heavy on this.

Idk, it depends on how much you care about the page loading time. Even without the PurgeCSS filter, I would recommend the Django Compressor app. I use it on all my websites. It automatically merges your css/js files and minifies them (removes white spaces, comments, etc.). It also creates a unique name for the combined CSS so if you changed your CSS files, your users will always see the fresh version, not the cached by the browser one.

django_compressor - for merging and minimizing css and js assets

django-compressor with django-libsass for auto sass compilation

But isn't that what you have django-compressor for?

The external dependencies were downloaded into the static/ folder containing all frontend assets using yarn and a package.json. Other than that, yarn was not used. Next I ran a bash script that removed all files I did not need, keeping the javascript, css and font files that should be served. In html, these files where directly included. I knew that loading many files is bad, so I used django-compressor to combine them into one big file. Conveniently, this tool also provided me with a way to compile scss.

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

These pieces fit together very well and are sufficient for replacing most of the goodies Django provides. However, there's one piece missing. Django has a built-in permissions feature, but it's limited to model-level control, i.e., if a user or group has X access to model type Y. Many users have been using the popular django-guardian package to implement row-level permissions. It allows you to establish permissions between users/groups and objects, manages the underlying permission database tables, and provides APIs for configuring and checking such permissions.

https://github.com/django-guardian/django-guardian/issues?q=is%3Aopen+is%3Aissue+label%3ABug

Could use django-guardian for this instead: https://github.com/django-guardian/django-guardian

I was about to use django-guardian until I came across the following in the official documentation:

django-guardian for per object permissions