The MBS documentation is not so bad, but it is like the original documentation of the libraries used: there is no real user manual. It is a very synthetic language reference, written not by a documentalist, but by a high-level developer.
Sometimes a few pages or a small booklet would already be very useful to know how to approach the library. When we discover it, but also several months or years later, when we need it again, but we don’t really remember how the library is structured (especially since each library is often completely different in the way it operates and understands the objective).
It would be tens of minutes or hours of savings each time. Once you have in mind the functioning of the library, and everything is clear in your mind, you just have to refer to the official documentation to get details on the functions, it’s happiness!
Of course, at $50 for a little booklet on MBScurl for example, everyone would complain. But the professionals would still buy it, I’ll buy it, because it’s worth the price. Christian is already saving us time with his plugin, all we need now is a real manual. This is a lot of time saved, less stress, better quality code. Writing technical documentation is a real profession that requires both strong technical skills and strong pedagogical skills, it is very rare and valuable.
When you are used to the good quality of Xojo documentation, it is difficult to switch to a third-party library documentation, not only because there is no real manual, but also because it is often a very different operating logic than Xojo.
Concerning the format, I like the basic web, simply with bootstrap for example. It is mobile and computer-readable, universal, easily updatable, you can use automatic translators and other third-party tools that can help, you can copy and paste, etc.
Translated with www.DeepL.com/Translator