Integrating Django and WordPress can be simple.
summary
Claim: keep WordPress as the editor and let Django serve the public site. Uses nginx + PHP-FPM, single MySQL database with WP tables left intact, and either the django-wordpress app or a hand‑rolled mapping created via inspectdb with manual FKs. Shortcodes get handled with lightweight regex hacks, comments use a simple model form, and full‑page caching speeds delivery. Result: working production site that keeps WP admin features but minimizes PHP surface area; watch for plugins, custom PHP, and auth sync complexity.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:40Django
- 1:00Client websites
- 1:53WordPress
- 2:43PHP
- 4:34Blog model
- 5:43Editing content
- 7:13Building features
- 8:51Where to keep WordPress
- 10:52Admin TinyMCE
- 12:03Keep it simple
- 14:28Dont touch WordPress
- 16:00Inspect DB
- 18:46Web vs Application
- 21:01Crazy Idea
- 26:40Nginx
related talks
27mMigrating legacy data to your Django project
29mAngular & WordPress: Practical guide to headless CMS
34mFace Your Fear: The Headless WordPress!
08mScaling WordPress with Next.js
56mUsing WordPress as a Modern Web Dev
31mUsing WordPress for an editorial team
30mWhy would a new developer choose Django?
37mAMA: The Future of WordPress