I've been spending a lot of time recently basically as a physics research assistant in my spare time (which is 24/7). I've worked as a programmer before, so I have experience with other languages, but not Maple.
However, even though I literally have the whole day every day to spend trying to figure things out it seems like the documentation is quite lacking sometimes and there are things I simply cannot find without the very useful help from this community here at MaplePrimes (small example further below).
I've been thinking a lot about improving the documentation. I've always been the person on my teams pushing people to have better documentation and being better at communication.
Now, Maple isn't open source, so I can't just contribute to a repository or something. I would like to make a repository of my own that sort of mirrors parts of the documentation but is written in a way that to me feels more didactical, and with a lot of examples and edge cases that I am finding in practice.
There are so many things that happen that are unexplainable to me. My documentation wouldn't be an encyclopedic reference like the official documentation obviously, but it would rather try to explain certain things better and show cool examples.
Is there any appetite from anyone in the community here (especially the more experienced people) to help me (essentially by answering a ton of my questions as they come up, and then maybe reviewing my write-ups as I push to Github, and even maybe having an actual call to answer a question I might have)? I think this would be a helpful contribution for future users of Maple.
Just to give a small example from the last two hours of a section in the documentation that I found to not be didactical enough.
In the documentation about the Maple preprocessor, there are essentially no examples. On updating the include path, there is the following snippet
The include path can be specified on the command line that invokes Maple by using the -I option or it can be modified by calling kernelopts(includepath). Multiple paths can be specified within a single string separated by commas or semicolons or alternatively a list of paths can be entered. When using kernelopts(includepath), do not prefix the include path with -I. The maximum number of include path entries is 25.
What exactly does "calling kernelopts(includepath)" mean? I tried kernelopts(includepath) := "my/path/here". Didn't work. Perhaps I have a lack of imagination but I only found out it is kernelopts(includepath = "my/path/here") from a post here in this community.