Reference page click-to-reveal class methods

[JetStarBlues]

Actual Behaviour

Currently, the only way to find out about the existence of class methods from the Reference page is by clicking on the class article. For example, the only way to become aware of the setUniform method is by clicking on the p5.Shader article.

This works fine if you are already familiar with what a class does. However, it is not so great for discovering functionality you are unaware of.

Expected Behaviour

In addition to the current style (of nesting method links in class articles), I think modifying the way these classes are listed on the Reference page would go a long way in discover-ability.
Specifically, I propose using a click-to-reveal interface on the class entries. On click, the entry would expand to show nested methods. On next click, the entry would collapse. And so on. In this way, the Reference page is not cluttered, but now class methods are immediately visible (without clicking through to the associated class article).

For example:

default state

• p5.Image ᐯ

toggled state

• p5.Image ᐱ
  • loadPixels()
  • updatePixels()
  • get()
  • ...

[Rahulm2310]

@JetStarBlues Can you please include how it is going to increase the accessibility of the reference.

[JetStarBlues]

Accessibility
The current organization of class methods makes the assumption that 1) a user is familiar with concept of classes and that 2) they will know what the base class is of an object they are working with, and 3) they will know to look in the documentation of the class to find associated methods.

As a personal example, when I was trying to figure out how to work with shaders in p5, I started out using the loadShader() function. In the example provided, the method setUniform is used. Looking at the reference page, I did not see an entry for the function, and I thus assumed it was undocumented. However later, through an unrelated Google search, I came across setUniform's documentation page. It was then that I realized that the documentation is nested under p5.Shader. With this proposal, class methods such as this one would be readily listed in the Reference page.