Chapter 3 of 12
A Django project is made of apps — modular components that each handle one area of your site. A blog might have a 'posts' app, a 'comments' app, and an 'accounts' app. This modularity keeps code organised and reusable.
python manage.py startapp courses
# App structure:
# courses/
# __init__.py
# admin.py ← register models for the admin panel
# apps.py ← app configuration
# models.py ← database models
# views.py ← request handlers
# urls.py ← URL patterns (you create this file)
# tests.py ← tests# myproject/settings.py — add to INSTALLED_APPS
INSTALLED_APPS = [
"django.contrib.admin",
"django.contrib.auth",
# ... other built-in apps ...
"courses.apps.CoursesConfig", # or just "courses"
]TIP
One concern per app. A good Django app does one thing well. 'courses' handles courses. 'users' handles user profiles. 'payments' handles billing. This separation means you can test and reason about each area independently — and theoretically reuse apps across projects.