Wagtail Unboxed episode 01 5:19
What Wagtail actually is
We install Wagtail, create a project, and get a real CMS admin running — then stop, because episode 2 opens up every single file it generated.
What this episode covers
First, the question nobody answers clearly: what is Wagtail? It is not an alternative to Django, it runs on Django. We compare it to plain Django, to the Django admin and to WordPress, and say where each one actually wins.
Also covered: why you should never name a Django project “site”, because Python already has a module with that name; and why we pin both Wagtail and Django, since Wagtail 7.4 declares a minimum of Django 5.2 with no upper limit, so an unpinned install will not match what is on screen.
No database to install. SQLite ships inside Python, and Postgres arrives in episode 13.
Chapters
- 0:00 What you'll have by the end
- 0:20 Wagtail vs Django vs WordPress
- 0:40 But Django already has an admin?
- 1:02 The one-sentence version
- 1:14 A folder and a virtualenv
- 1:35 Installing Wagtail
- 1:53 Why pin Django too?
- 2:14 Creating the project
- 2:20 Those two arguments
- 2:41 Never name your project “site”
- 3:04 migrate — 184 migrations before you write any code
- 3:21 No database server
- 3:40 createsuperuser
- 3:52 Running it
- 3:59 The two addresses
- 4:15 One page already exists
- 4:36 git and the episode tag
- 4:50 Next episode
Versions on screen
Wagtail 7.4.3 · Django 6.1.1 · Python 3.12. Recorded on Windows; macOS and Linux commands are in the repository for every episode.