How markjustine28/capstone works
This repository combines a Django school-guidance backend with Flutter platform shells; the tree and excerpts do not expose the Flutter application code. The backend’s visible workflow is API/report handling over student, incident, counseling, and school-year records. API views and Django admin are shown using the central API models; report views reference their own models and serializers. The report subsystem’s exact behavior and URL dispatch are not established by the available excerpts, so those links are omitted. Maintenance commands are represented only where their model dependency is indexed.
Main entry points: models.py Guidance records · reports/views.py Report views · api/views.py API views · admin.py Django admin
Components 10
API and administration
- API views
myproject/api/views.py - Django admin
myproject/api/admin.py - API serializers
myproject/api/serializers.py - API routes
myproject/api/urls.py
Report handling
- Report views
myproject/reports/views.py - Report serializers
myproject/reports/serializers.py - Report records
myproject/reports/models.py
Domain records
- Guidance records
myproject/api/models.py - School-year rollover
myproject/api/management/commands/rollover_school_year.py - School-year repair
myproject/api/management/commands/fix_school_years.py
Connections 6
- API views → Guidance records: uses records
myproject/api/views.py - Django admin → Guidance records: administers
myproject/api/admin.py - Report views → Report records: uses records
myproject/reports/views.py - Report views → Report serializers: uses serializers
myproject/reports/views.py - School-year rollover → Guidance records: uses records
myproject/api/management/commands/rollover_school_year.py - School-year repair → Guidance records: uses records
myproject/api/management/commands/fix_school_years.py