200% agree. I hand’t thought about a blog, but I did propose moving some content out of the website out of the documentation so that we have pymc.io (website about the project, blog, governance, about us…) and docs.pymc.io documentation for pymc library in html format.
I recently created an ArviZ project website: ArviZ project (please don’t advertize it yet though, we want to pair it with the new logo we got funds for with GSoD).
I would love to have the home website be a super cool website with no relation to sphinx, but I think that would mean hiring someone. In the meantime, we could set up something like that and use ablog like we do in pymc examples so that it is very easy to create and we can write blogposts directly as notebooks if we want to, otherwise use markdown or rst.