# If Django were created today, which batteries would you expect to be included in core?

**URL:** <https://forum.djangoproject.com/t/if-django-were-created-today-which-batteries-would-you-expect-to-be-included-in-core/34934>\
**Category:** Django Internals\
**Created:** [September 20, 2024, 8:59am UTC](https://forum.djangoproject.com/t/if-django-were-created-today-which-batteries-would-you-expect-to-be-included-in-core/34934 "2024-09-20T08:59:17Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Flimm](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/flimm/32/17468_2.png) [@Flimm](https://forum.djangoproject.com/u/Flimm)\
**Post date:** [October 8, 2024, 5:11pm UTC](https://forum.djangoproject.com/t/if-django-were-created-today-which-batteries-would-you-expect-to-be-included-in-core/34934/12 "2024-10-08T17:11:46Z")

</div>

- A clear **build step** for static assets that can be hooked into with custom code. It doesn’t need to do anything by default, but there should be one obvious place to run `esbuild` or whatever. Right now, I’m running build steps outside of Django’s framework, but I would prefer it if Django knew to call the build step in the right places. A lot of the Django extensions are too opinionated when it comes to compiling static assets, all I want is a hook for a build step and I’ll write its code myself. (If this feature already exists, I’ve somehow failed to discover it.)
- I would love more **strict Django templates** that don’t silently fail when variables are missing or when there are typos in variable names
- Anything to make **first-time deployments** easier

I also heartily agree with some of these other suggestions, including: whitenoise by default and background tasks.

---

_[View the full topic](https://forum.djangoproject.com/t/if-django-were-created-today-which-batteries-would-you-expect-to-be-included-in-core/34934)._