CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/django-best-practices

Django patterns -- custom user model, project structure, models, views, URL routing, select_related/prefetch_related, signals vs save(), middleware, settings splitting, custom managers, management commands

92

1.63x
Quality

87%

Does it follow best practices?

Impact

100%

1.63x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-2/

Event Booking System

Problem/Feature Description

Build an event booking system with Django. Event organizers create events, and attendees can browse and book spots. The events listing page shows upcoming events with organizer names and remaining capacity. Each event has a detail page with full description and a booking form.

Requirements:

  1. Users can register as either organizers or attendees
  2. Organizers create events with a title, description, location, date/time, and capacity
  3. Events have a status: upcoming, ongoing, completed, or cancelled
  4. Attendees can book a spot at an event (one booking per user per event)
  5. The events listing page at /events/ shows upcoming events sorted by date, displaying organizer name and spots remaining
  6. Each event has a detail page at /events/<slug>/ showing all details and list of attendees
  7. A user's dashboard at /dashboard/ shows their bookings with event details and organizer names
  8. Organizers can cancel events from the dashboard

Output Specification

Produce Python source files in a eventsite/ directory:

  • Settings configuration
  • URL configuration
  • App files for each feature area with models, views, urls, forms, admin
  • Templates directory structure
  • manage.py

Do not run migrations or start the server.

evals

tile.json