Or see the list of project sponsors.
I think to make it a tradition – creating a ready to use project skeletons.
Here is one which uses Coo:
Here is how it's rendered documentation looks like.
Read this doc to learn more about the pros and cons of this documentation system:
Here I want to highlight only a few moments.
The system has a huge potential for improvement. There are some GitHub issues to work on. I've already sent my pull-request to add support of ASDF package inferred systems:
The two coolest features are:
Right now Coo is good for documenting small libraries which don't need for abstract chapters of documentation, but I see how it can be extended to render handwritten docs along with generated from docstrings!