Despite the excellent initial intention, the article itself shows the reasons of the low adoption: if you actually need to kind of hack every new piece of docum

Despite the excellent initial intention, the article itself shows the reasons of the low adoption: if you actually need to kind of hack every new piece of documentation, this is overwhelming. I can have more than 30 external packages for each project. It would be too painful to handle all of them, and particularly frustrating for the ones I can't, and still need to browse from my browsers. This kind of projects could have a better adoption rate with standards for documentations.