Thanks Ben, you are completely right:
Basically, the generated doc is the website. And besides the weird feeling of
packaging a website, it comes with all the problems that you pointed me to
(bundling jquery, licenses).
So, even though I had gotten `mkdocs-simple-hooks` to build meanwhile,
HTML documentation generated with mkdocs will unfortunately suffer from the
same kinds of issues around bundled and pre-minified JavaScript and CSS
identified for Sphinx and Doxygen in [1] and in the “packaging” mailing list
thread linked from that bug. (Yes, I know there are a lot of packages
py3status looks like a nice i3status provider, which is why I have looked into
taking the orphaned package.
Alas, the package needs an update from 3.34 (as packaged) to 3.44 (as current).
In between these versions, the doc build chain changed from sphinx to mkdocs.
Upstream uses the plugin
