Most heard feedback we get about our DRF APIs is about documentation. For us API devs the dilemma is how to write the docs, where to publish, keep in sync, test

Most heard feedback we get about our DRF APIs is about documentation. For us API devs the dilemma is how to write the docs, where to publish, keep in sync, test and so on. Now with 3.6, there's only one place and it's with the code. Granted, this won't solve our dilemma completely (we still need to write the docs). Automatic JS client should come in handy as well. I've been toying an idea about automatic integration tests that could exercise the API externally and keep an eye out for schema changes. DRF is an important product in Django realm. If you haven't already, take a look at their funding options: https://fund.django-rest-framework.org/topics/funding/ https://fund.django-rest-framework.org/topics/funding/