documentationgood first issuehelp wantedpriority
Description
Here's the TODO list... I'll add/change as appropriate:
Concept pages
- Colors, ColorGradients (how and when to use what, what kinds of things are supported, lots of examples, also point to external sources for predefined gradients. see: #139)
- Input data (vectors, matrices, functions, dataframes, tuples, custom objects... talk about all the ways to pass in data and how it gets passed through the pipeline)
- Arguments (vector vs matrix, preprocessing pipeline, magic args, etc)
- Subplots (different ways to build, layout types, linked axes)
- Backends (How to choose... which ones are good at different plot types, some prose about the quality/progress for each package, some side-by-side comparisons of plot examples)
- Fonts, PlotText, Annotations
- Guides (titles, axis labels/limits/ticks, legend/colorbar)
- Plot components (path vs line, markers, fills, styles, strokes, shapes, etc) (see #445 for additional ideas)
- Animations
- Recipes (some examples of how to plot custom objects, or to build predefined sequences. discuss both
PlotRecipeand_apply_recipeand when you would use either and why they are so much better than making a function that wraps a call toplot) - Design decisions (why did I make certain decisions, thoughts on speed, thoughts on different usage patterns, thoughts on why there are many ways to do the same thing, how MLPlots/ExamplePlots fit into the ecosystem)
- Goals for the future (Make Plots... ???... profit)
Examples
- Better/more complex examples covering more functionality
- Output other than PNG... for example GR could be SVG, Plotly should be HTML
Tutorials
- Reorganize
notebooksdirectory in ExamplePlots intotutorialsandscratch. (most of them will be scratch currently.) The idea is that these will be "true tutorials" and not just haphazard code. They should combine Plots with some real world workflows and have lots of comments/structure