Until June 2007, if you wanted to see a few sites that were built with Django you had to wade through a list of about 200 links on a wiki page. The links were somewhat organised into categories, but no matter who you ask that's a boring job.
Djangosites.org was built as a showcase of what's out there in Django Land.
We hope it lets you easily see what's capable with the Django framework. Feel free to add your sites, post comments on other sites, and vote for your favorites.
Is that really Django?
I regularly get asked how I know that a website is running Django. There'a few key things that Django uses to give itself up, which whilst useful for me are probably things that overly security-conscious developers want to consider when deploying Django-powered websites. Most of these are either default options, or listed as examples in the documentation that people copy and paste verbatim.
- The presence of /admin/ that shows a Django login form.
- Form elements have names of id_xyz
- Login pages at /accounts/login/
- Redirects with no trailing slash - ie /accounts/login redirects to /accounts/login/ (but, importantly, /some404 will not redirect to /some404/
- No URLs ending in .php or .aspx.
This doesn't catch everything; there are some websites that are built in a way that hides all of the above. These cases need some intuition to figure out.
- Powered by Django (duh!!!) on Python
- Served by nginx and Gunicorn
- Pre-built Django components we used:
Any feedback or suggestions should be sent to djangosites at djangosites dot org.
Try here again soon.