$ the-wire · showcase
Django's docs move to pydata-sphinx-theme, with deploys pre-staged
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
2 people shipped this
Django's documentation build swaps its unmaintained djangodocs theme for pydata-sphinx-theme, and djangoproject.com has already landed the dependency and build changes so the dev docs site does not break on the day it merges.
Fixed #37138 -- Changed docs to use lightly customized pydata-sphinx-theme. django/django
The djangodocs theme, which inherits from Sphinx's basic theme, is replaced by pydata-sphinx-theme with light customization: the split top/left navigation collapses into a single left sidebar, and docstitle moves from navbar_start into navbar_center so long development version numbers stop wrapping in the header.
Two commits: preparation for Django's docs theme changes django/djangoproject.com
Natalia Bidart's two-commit prep in djangoproject.com lands the supporting changes ahead of the docs theme switch, keeping the site's dev docs build green in the window before the Django PR merges.
Added pydata-sphinx-theme to the docs build dependencies. django/djangoproject.com
The offline HTML zip is built with the Django checkout's own theme, so pydata-sphinx-theme was added to the docs build dependencies ahead of that switch; without it the dev docs build would fail the moment the new theme lands.
Built the docs JSON output with Sphinx's basic theme. django/djangoproject.com
The JSON docs build now runs on Sphinx's basic theme rather than loading the checkout's HTML theme: the website renders that output with its own templates, so loading the theme only made the build fail when it wasn't installed and let theme hooks alter permalink symbols, link text, and table markup in the HTML the site serves. Output stays unchanged for current branches.
Refs #37271, #37272 -- Doc'd remaining DEP 20 changes for users and releasers. django/django
The remaining DEP 20 changes are documented for both users and releasers: from Django 2028 onward, the Python version support policy changes, every feature release gets three years of support, and releases move to calendar versions, written up in the Python version FAQ, the upgrade guide, and the release how-to.
