Andrew J.

> Point 1. has finally been fixed yesterday (#318 - #320). When searching for e.g. `show_empty_bins`, a search results pointing to https://docs.juliaplots.org/stable/generated/attributes_series/ is proposed. You can search for attributes but...

With the entry I wrote, I think it's a bit too complex to be included as part of a dictionary. The majority of attributes won't be as complex as `bins`,...

One way to recategorize them is the following: * [**Series attributes**](https://docs.juliaplots.org/stable/generated/attributes_series/) stay the same. On the API page, every entry contains a "Relevant attribute for the following series types:" list...

> On the other hand I don't see a reason why you couldn't generate the markdown in [#323 (comment)](https://github.com/JuliaPlots/PlotDocs.jl/issues/323#issuecomment-1345472075) from the current stucture when you change the descripion string in...

Does the information have to be written as part of a dictionary, or can I write the markdown directly? Using `##` and `###` headers would be good enough for organization.

One way is to keep the dictionary as-is, but create new pages with pure Markdown, replacing the `generated/attribute_series.md`, etc. That way `plotattr` functionality won't be broken. There'll be a disconnect...

[Example](https://github.com/Ininterrompue/PlotDocs.jl/blob/master/docs/src/Attributes/attributes_series.md) for series attributes. While creating this page, it was found that `match_dimensions` was not being generated in the table.

What would be the cleanest way to make sure there are sections for Subplot and Axis attributes, e.g. annotation, colorbar, etc. so that they show up on the dropdown menu,...

See [relevant PR](https://github.com/JuliaPlots/Plots.jl/pull/4604)