Updating the Documentation to ease finding features

[tabedzki]

Hello!

I love using Plotnine and the power that it has. Sometimes, I feel like I don't truly know can be done with it and in those instances, I feel that the documentation can get in the way, especially when coming from a search engine.

For example, when searching for "caption" or "subtitle" feature, I was looking at the API reference and saw that it wasn't on the page itself, but there were labels, and found the labs tool thinking it would be useful. I've used the labs command for a while but you when go to the reference page it basically shows nothing useful and you have to go to the source to even see what might be some commands. I've learned from experience that you can update things like color, y, linetype with experience but the lack of possible commands/arguments on the doc pages for a specific command is something that holds back plotnine.

I've tried getting people to use the plotnine package since I really like the grammar of graphics approach but the lack of content on the documentation page (especially when coming from a Google search) is hindering adoption, at least within my local community.

Is there an automated way to list the possible arguments instead of trying to guess what the valid kwargs** might be for a given function?

Also, I have a vague memory of there being a tutorial/gallery of the different themes all plotted so a user can easily come to the website and see what each one looks like. I can't seem to find it. Is that something we can also implement?

[tabedzki]

See #711 for an example of how sometimes the documentation can be difficult to use to find what you are looking for.