How Django helped us make a better conference website
summary
Replaces an aging monolith called zookeeper with a Django-based stack that reuses existing apps: Wagtail CMS for editorial pages, django-wiki integrated into site templates, and symposium for CFP and scheduling plus a new registration package for complex ticketing. Development setup drops from brittle custom scripts to pip/venv, organizers get fewer support tickets (missing dinner-code fixes eliminated), pages become modular and community-contributable, and remaining work focuses on decoupling symposium forks and making registration a reusable app.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 3:40Replacing Zookeeper
- 8:10Adopting the Django stack
- 10:42Key Django apps and tools
- 16:13Solving registration issues
- 18:03Project outcomes and lessons
- 21:37Q&A session
related talks
49m"State of Django" Panel
56mDjangoCon 2008 Panel: Django Success Stories
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
38mdjango-cms: Friends don't let friends use Drupal.
51mDjangoCon 2008 Keynote: Mark Ramm
26mA Fireside Chat
54mDjangoCon 2008 Panel: Django in Journalism
58mPanel Discussion: Two Decades of Django with Velda Kiara
