Dj-beat-drop is more about making minimal changes to the official Django templates. It mainly involves standardizing to a config directory for configuration code and optionally using an `env` file and `uv` for package management.
By keeping things minimal, the chances of it getting accepted as an official Django project seem better. It would need to be renamed, of course, to something like django-installer or django-cli.
I would certainly make improvements to the script to optimize the serialization of the QuerySet to only output the needed fields. It's hard to write an article that would capture every use case and optimization required.
This is an excellent point; I should have addressed safety in my article. I'll point out that in my use case, I'm using `safe` on data I create and not any user-generated data.
You should never use `safe` on user data unless you use something like bleach (https://github.com/mozilla/bleach) to sanitize the data. Even then, you should use caution.
Thank you for pointing this out, I forgot about this template filter. This unfortunately still wouldn't properly all the data types mentioned in my article (e.g. QuerySets).
By keeping things minimal, the chances of it getting accepted as an official Django project seem better. It would need to be renamed, of course, to something like django-installer or django-cli.