@Jamessocoljames 
@b0rkJulia Evans We put a huge emphasis on docs from day 1. Our policy has always been that new code can’t be merged unless it includes docs — we’ve held up major features because the docs weren’t done/good. That’s a virtuous cycle: good docs attract contributors who value good docs. So yeah it’s super intentional, and always nice to hear from someone that it seems to be working :)
@jacobjacobian @Jamessocoljames @b0rkJulia Evans I can, without reservation, say that the reason I started using Django 20 years ago, eventually joined the core team, and everything that flows from that, is significantly due to the fact that Django’s documentation, even in the 0.91 days, was *excellent*.
I have a PhD in CS - so I theoretically knew stuff, but couldn’t actually do things like “build a web site”. I bounced off PHP because the docs at the time were incoherent. I bounced off Rails and CherryPy because while the tutorial got a TODO app going, the next steps were unclear.
I don’t think you can understate the influence you and 
@adrianAdrian Holovaty’s focus on good docs in Django had on the Python ecosystem.
If you have a fediverse account, you can quote this note from your own instance. Search https://cloudisland.nz/users/freakboy3742/statuses/115947575018635122 on your instance and quote it. (Note that quoting is not supported in Mastodon.)