Django

TaskBoard Capstone

Wire the full application end to end

TaskBoard Capstone

Wire everything you built into a checklist you can demo locally:

  1. Models: Project, Task, Tag with migrations committed
  2. Auth: login required on task views; queryset scoped to owner
  3. URLs: namespaced tasks: routes for list, detail, create, update
  4. Templates: base layout, messages, CSRF on all POST forms
  5. Admin: inlines and list filters for support staff
  6. Tests: at least login redirect and one create flow
  7. Settings: .env for secrets; DEBUG=False profile documented
  8. Static: collectstatic documented for deploy

Try it locally

python manage.py test
python manage.py runserver
# Log in, create a project in admin, add tasks via UI

Next: Expose TaskBoard over JSON in the Django REST Framework section—same domain, API clients, and mobile apps.

Django — Knowledge Check

Check your understanding of this section. Results are not saved—refresh the page to start over.

1. Django follows which pattern?
2. In TaskBoard, a ForeignKey from Task to Project means:
3. get_object_or_404 is preferred over objects.get() because:
4. CSRF protection in Django forms requires:
5. select_related is used to:
6. @login_required ensures:
7. makemigrations and migrate: