-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Refactor legend documentation #9458
Copy link
Copy link
Closed as not planned
Labels
Documentationstatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.Issues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github ActionMarked by the “Stale” Github Action
Metadata
Metadata
Assignees
Labels
Documentationstatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.Issues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github ActionMarked by the “Stale” Github Action
Type
Fields
Give feedbackNo fields configured for issues without a type.
@anntzer recently pointed out that we've got a lot of documentation on legends scattered throughout the website. Some has higher quality than others, some has mixed levels of user expertise, some are in unintuitive places. I'm putting a list that @anntzer collected below in case somebody wants to take a stab.
Tutorial:
quite advanced, probably can use some rewriting but OK.
Examples:
Looks somewhere between what this PR proposes and the legend guide. I think this PR is a nice piece of work but I would suggest trying not to spread the same information too thinly across many examples; perhaps the three "narrative" legend examples/tutorials could be merged into two?
Can probably be deleted and the relevant features split across other examples.
Can probably deleted, there's nothing special about legends in polar plots.
Should probably be unified.
Is really about event handling so can stand by itself.
Should probably be rewritten to use a single legend for the whole figure...
Is basically the default now... probably doesn't need to exist by itself.
Heh, why not.
Suggestions: