Django apps accrete docs debt fast — model fields change, views get refactored into viewsets, and settings sprawl. docs-keeper parses your Python with Tree-sitter and grounds every draft in the real code so the docs match what actually ships.
Documentation that tracks your models and views
docs-keeper follows your Django models, views, and serializers and rewrites the docs when migrations land.
What docs-keeper keeps in sync
Model reference
Field names, types, and relationships documented from the model definitions themselves.
API endpoints
DRF views, serializers, and URL routes turned into accurate endpoint docs.
Settings & env
Configuration docs updated when settings or environment variables change.
Management commands
Custom commands documented from their argument definitions.
Docs it writes for Django
README.mdAPI referenceModel referenceCHANGELOG.mdDeployment guide
Frequently asked
Does it read migrations?
docs-keeper reacts to merged PRs and reads the surrounding code context, so model and schema changes that ship in a PR are reflected in the drafted docs.
Does it support Django REST Framework?
Yes. Serializers, viewsets, and routers are all parsed as ordinary Python, so endpoint docs stay grounded in your actual classes.
Can I keep docs in Sphinx/MkDocs?
docs-keeper writes Markdown into the doc paths you configure, which works directly with MkDocs and with Sphinx via myst-parser.
Try docs-keeper on your Django repo
One public repo, 20 doc PRs per month, no credit card. See if drafts read like your team before committing to a paid plan.