The Django Admin¶
What we are learning¶
- What the admin site is for.
- How to create an admin user and log in.
- How to register a model.
- How to customize the list page.
Why this matters¶
The admin is your fastest inspection tool. When a view looks wrong later, you check the admin first to see whether the data or the code is at fault.
A simple explanation before code¶
Django ships with a staff-only site at /admin/. Your models do not appear there until you register them. Registration is one line; customization is a small class that says which columns, filters, and search box to show.
Important terms: superuser, registration, ModelAdmin, list_display.
Step-by-step example¶
1. Create an admin user (10 min)¶
Pick a username and password you will remember for class. Log in at http://127.0.0.1:8000/admin/. You will see Users and Groups but no Tasks yet.
2. Register the model (15 min)¶
Open tasks/tasks/admin.py. Replace its content with:
# inside tasks/admin.py (replaces the placeholder)
from django.contrib import admin
from .models import Task
@admin.register(Task)
class TaskAdmin(admin.ModelAdmin):
list_display = ("name", "priority", "done", "created_at")
list_filter = ("priority", "done")
search_fields = ("name",)
fields = ("name", "description", "priority", "done")
Refresh /admin/. Tasks now appears. list_display picks the columns. list_filter adds the right-hand filters. search_fields adds the search box. fields controls the edit form order.
3. Use it (15 min)¶
Add two tasks through the admin, then use search and the priority filter. Notice __str__ from Ch1 is what each row is called. This is the same data your shell created.
Note: an earlier lesson wrote the filter as |lowercase. The correct Django filter is |lower. Use |lower in templates.
Let's build it: follow-along practical (10 min)¶
Each learner adds one task in the admin, finds it with search, and toggles done on the edit form.
What the code is doing¶
@admin.register(Task) connects the model to the admin. TaskAdmin does not change the database; it only changes how staff browse rows. fields omits created_at/updated_at because those are automatic.
Common mistakes and fixes¶
- Model missing from admin — forgot to save
admin.pyor used the wrong app file. Restartrunserverand refresh. createsuperuserpassword rejected — Django validates length and common passwords; choose a longer one for class.- Edits in admin not visible on site — the site still shows dummy data until Ch3 swaps in the ORM. That is expected right now.
Try it yourself¶
Guided: add a list_filter entry and prove it filters. Independent: add search_fields for description and test it, then revert if search gets noisy.
Check your understanding¶
- What URL serves the admin?
- What command creates a superuser?
- What line makes a model appear in the admin?
- What do
list_display,list_filter, andsearch_fieldseach do?
Summary¶
Admin is for staff, not visitors. Register once, customize the list page, and use it to verify data through the rest of the course.
Next lesson¶
We query this same data inside views and show it in templates.