The framework emphasizes reusability and "pluggability" of components, less code, low coupling, rapid development, and the principle of don't repeat yourself.

Django also provides an optional administrative create, read, update and delete interface that is generated dynamically through introspection and configured via admin models.

[15] Django was created in the autumn of 2003, when the web programmers at the Lawrence Journal-World newspaper, Adrian Holovaty and Simon Willison, began using Python to build applications.

[19] Despite having its own nomenclature, such as naming the callable objects generating the HTTP responses "views",[7] the core Django framework can be seen as an MVC architecture.

While the Django philosophy implies loose coupling,[24] the template filters and tags assume one engine implementation, and both the auth and admin bundled applications require the use of the internal ORM.

Django can be run in conjunction with Apache, Nginx using WSGI, Gunicorn, or Cherokee using flup (a Python module).

[31] There is a fork named django-nonrel, which supports NoSQL databases, such as MongoDB and Google App Engine's Datastore.

2013 DjangoCon was held in Chicago at the Hyatt Regency Hotel and the post-conference Sprints were hosted at Digital Bootcamp, computer training center.

[73][74][75] Programmers have ported Django's template engine design from Python to other languages, providing decent cross-platform support.