Hello !
@Michael : All understood. It's actually very good to know that it isn't under active development, because at least it removes any temptation to write down feature requests or suggestions. I am totally fine with just taking it for what it is and see if it works for me.
As for Grasshopper ... well, my workflow is way too MOI-centric to consider anything else at this time, as I find that the way you implemented the 2D drafting tools is just better and faster than any other app out there, from specialized CAD software to more illustration oriented vector imaging software :D But I'll certainly give Rhino/GH another go as a companion app perhaps if I ended up not being able to do something with "Elephant".
Also understood about the help/docs.
@Frenchy Pilou : I see, so indeed this is a bit of a "fan effort" then, that explains it. It sure is a rough around the edges with the way it is organized as it seems to be quite a maze of links, but it looks like there is some valuable information in there nonetheless so I'll dive in.
FWIW my confusion came from the use of the term "Library". In software development (like in Python for instance) a library means a set of special functions that comes as an optional package. For instance in Python one would load a specialized math library in order to use some math functions that are not in the language by default. So calling the documentation a "library" is confusing, as it makes it look like it is a repository of custom functions. In general I would recommend to avoid the temptation of using "false friend" translations, but instead looking up the definition of each word, even though it may seem like the same as in French.
One suggestion on the structure if I may : IMHO this documentation site would be much more readable if it was organized linearly, as opposed to being a maze of interconnected links of multiple depths. Here's an example of something similar relating to UE4 blueprints :
https://romeroblueprints.blogspot.com/p/table-of-contents.html
If you download any of the Compendiums you'll see that everything is organized linearly like a regular book (which is precisely what makes it PDF-friendly).
Put differently : for a website to be as clear as possible one wants to avoid having too many depth levels. Ideally there should be only one level really - that is to say, a main menu pointing to all the pages. As soon as the user needs to go into one or two more hierarchical levels to reach information it gets very annoying and confusing.
