How divineninja/django-crm works
This is a small Django project whose visible product is a question-and-campaign app: administrators manage campaign questions, choices, and dependencies, while a REST endpoint lists questions with serialized choices and conditions. The README provides no product-level detail. The poll URL declarations are present in the tree but were not sampled, so their specific route-to-view wiring is not asserted; the login integration is likewise omitted because its source is absent.
Main entry points: models.py Poll domain models · views.py Question listing · urls.py Project routes · serializers.py Question serialization
Components 9
Request routing
- Project routes
core/urls.py - Poll routes
polls/urls.py
Polls and content
- Question listing
polls/views.py - Question serialization
polls/serializers.py - Content administration
polls/admin.py - Poll domain models
polls/models.py
Persistence
- Database configuration
core/settings.py - SQLite database
db.sqlite3
Other components
- API client
Connections 8
- API client → Project routes: sends request
- Project routes → Poll routes: includes routes
- Question listing → Poll domain models: queries questions
- Question listing → Question serialization: uses serializer
- Question serialization → Poll domain models: reads conditions
- Content administration → Poll domain models: registers models
- Database configuration → SQLite database: configures database
- Poll domain models → SQLite database: persists records