We need to choose the structure of the JSON for the GraPE documentation, which includes the Ensmallen and Embiggen submodules.

Currently, the JSON generated for the Ensmallen library likely includes a superset of the features we may want the JSON to contain, while the Embiggen one is to be properly developed.

For starters, I would propose to list the features that would make sense to have to generate the web pages.

One thing that should be taken into account when planning and engineering this website is the fact that the library is rapidly growing and we are using a lot of automation tools to do this. This is causing most tools to be outgrown, for instance, the Rust documentation website CRASHES because the library has too many methods.

Similarly, we are providing an ever-increasing amount of datasets, currently in the reaches of 20000: these are a lot of datasets, each one with its own report to be added to the website.