How hueppi92/kanmind works
KanMind is a Django backend for a separately maintained frontend. The visible runtime routes expose authentication, boards, and tasks; the main workflow is an API request routed to a domain view, validated/serialized, and persisted through Django models. The README describes the project as a foundation and says routes are still progressing; sampled URL configuration does register API includes, but the authentication, model, and route implementations were not all inspected, so uncertain internal links are omitted.
Main entry points: urls.py Root URL config · api/views.py Board handlers · api/views.py Task handlers · serializers.py Auth validation
Components 16
API routing
- Root URL config
KanMind/urls.py - Auth routes
KanMind/auth/api/urls.py - Board routes
KanMind/boards/api/urls.py - Task routes
KanMind/tasks/api/urls.py
Authentication
- Auth handlers
KanMind/auth/api/views.py - Auth validation
KanMind/auth/api/serializers.py - User accounts
KanMind/auth/models.py
Boards
- Board handlers
KanMind/boards/api/views.py - Board serialization
KanMind/boards/api/serializers.py - Board records
KanMind/boards/models.py
Tasks
- Task handlers
KanMind/tasks/api/views.py - Task serialization
KanMind/tasks/api/serializers.py - Task records
KanMind/tasks/models.py
Persistence
- Django settings
KanMind/settings.py - SQLite database
Other components
- KanMind frontend
Connections 10
- KanMind frontend → Root URL config: sends API requests
- Root URL config → Auth routes: includes routes
- Root URL config → Board routes: includes routes
- Root URL config → Task routes: includes routes
- Board handlers → Board records: queries and saves
- Board handlers → Board serialization: validates and serializes
- Task handlers → Task records: queries and saves
- Task handlers → Task serialization: validates and serializes
- Auth validation → User accounts: looks up and creates users
- Django settings → SQLite database: configures database