Django's primary goal is to ease the creation of complex, database-driven websites. The framework emphasizes reusability and "pluggability" of components, less code, low coupling, rapid development, and the principle of don't repeat yourself. Python is used throughout, even for settings, files, and data models. Django also provides an optional administrative create, read, update and delete interface that is generated dynamically through introspection and configured via admin models.
Django's configuration system allows third party code to be plugged into a regular project, provided that it follows the reusable app conventions. More than 2500 packages are available to extend the framework's original behavior, providing solutions to issues the original tool didn't tackle: registration, search, API provision and consumption, CMS, etc.
This extensibility is, however, mitigated by internal components' dependencies. While the Django philosophy implies loose coupling, the template filters and tags assume one engine implementation, and both the auth and admin bundled applications require the use of the internal ORM. None of these filters or bundled apps are mandatory to run a Django project, but reusable apps tend to depend on them, encouraging developers to keep using the official stack in order to benefit fully from the apps ecosystem.
Django may also be run in conjunction with Jython on any Java EE application server such as GlassFish or JBoss. In this case django-jython must be installed in order to provide JDBC drivers for database connectivity, which also can provide functionality to compile Django in to a .war suitable for deployment.
The Django team will occasionally designate certain releases to be "long-term support" (LTS) releases. LTS releases will get security and data loss fixes applied for a guaranteed period of time, typically 3+ years, regardless of the pace of releases afterwards.
There is a semiannual conference for Django developers and users, named "DjangoCon", that has been held since September 2008. DjangoCon is held annually in Europe, in May or June; while another is held in the United States in August or September, in various cities. The 2012 DjangoCon took place in Washington, D.C., from 3 to 8 September. 2013 DjangoCon was held in Chicago at the Hyatt Regency Hotel and the post-conference Sprints were hosted at Digital Bootcamp, computer training center. The 2014 DjangoCon US returned to Portland, OR from 30 August to 6 September. The 2015 DjangoCon US was held in Austin, TX from 6 to 11 September at the AT&T Executive Center. The 2016 DjangoCon US was held in Philadelphia, PA at The Wharton School of the University of Pennsylvania from 17 to 22 July. The 2017 DjangoCon US was held in Spokane, WA; in 2018 DjangoCon US was held in San Diego, CA. DjangoCon US 2019 was held again in San Diego, CA from Sept 22–27.
Django mini-conferences are usually held every year as part of the Australian Python Conference 'PyCon AU'. Previously, these mini-conferences have been held in:
Django has spawned user groups and meetups around the world, the most notable group is the Django Girls organization, which began in Poland but now has had events in 91 countries.
Ports to other languages
Programmers have ported Django's template engine design from Python to other languages, providing decent cross-platform support. Some of these options are more direct ports; others, though inspired by Django and retaining its concepts, take the liberty to deviate from Django's design:
Django as a framework is capable of building a complete CMS, however there are dedicated CMS project which are built upon and extend the Django framework. Below is list of a few of the more popular Django-based CMSs:
^"django/LICENSE". GitHub. Retrieved 8 September 2020.
^"FAQ: General - Django documentation - Django". Retrieved 30 April 2016.
^ ab"FAQ: General - Django documentation - Django". Retrieved 30 April 2016.
^ abAdrian Holovaty, Jacob Kaplan-Moss; et al. The Django Book. Archived from the original on 2 September 2016. Retrieved 3 September 2013. Django follows this MVC pattern closely enough that it can be called an MVC framework
^"Design Philosophies". Django. Retrieved 18 March 2018.
^"What Powers Instagram: Hundreds of Instances, Dozens of Technologies". Instagram Engineering.
^"Python". Mozilla Developer Network. Archived from the original on 8 February 2012. Retrieved 30 April 2016.
^Robenolt, Matt. "Scaling Django to 8 Billion Page Views". blog.disqus.com.
^"DjangoSuccessStoryBitbucket – Django". Archived from the original on 20 April 2016. Retrieved 30 April 2016.
^"The anti-Facebook: one in four American neighborhoods are now using this private social network". The Verge. Retrieved 16 June 2016.
^Demi, Luke (15 August 2021). "Reining in the thundering herd ⛈ Getting to 80% CPU utilization with Django". Clubhouse Blog. Retrieved 16 August 2021.
^"What is the history of the Django web framework? Why has it been described as "developed in a newsroom"?". Retrieved 18 October 2019.
^"Introducing Django". The Django Book. Retrieved 29 July 2018.
^"Announcing the Django Software Foundation - Weblog - Django". Retrieved 30 April 2016.
^"Security in Django". Django Project. Retrieved 25 March 2013.
^Socol, James (2012). "Best Basic Security Practices (Especially with Django)". Retrieved 25 March 2013.
^"What is a reusable app? — django-reusable-app-docs 0.1.0 documentation". Retrieved 30 April 2016.