The widgets preview is very useful for a) quickly checking if widgets are rendered correctly and b) to give new developers an idea what form components we have available.
This should be extended to most other components as well. The widgetpreview view should be changed to be named "componentpreview" and contain five tabs. Each tab contains examples of different components. I suggest we use one tile (not expandable) per component class. One tile can contain multiple examples of the same component with different options. And each tile should have a two-column layout: In the first column we show the component examples and in the second we display the docstring of the components init method. That way we can also easily see which components are still missing good docstrings.
Here is the list of tabs and which modules should go into which tab:
The widgets preview is very useful for a) quickly checking if widgets are rendered correctly and b) to give new developers an idea what form components we have available.
This should be extended to most other components as well. The widgetpreview view should be changed to be named "componentpreview" and contain five tabs. Each tab contains examples of different components. I suggest we use one tile (not expandable) per component class. One tile can contain multiple examples of the same component with different options. And each tile should have a two-column layout: In the first column we show the component examples and in the second we display the docstring of the components init method. That way we can also easily see which components are still missing good docstrings.
Here is the list of tabs and which modules should go into which tab: