Repository navigation
[Doc]: Great resource for matplotlib beginners #24288
Description
Documentation Link
https://matplotlib.org/stable/tutorials/introductory/quick_start.html
Problem
I found your quick start guide really good to understand the basic concepts, but I would have loved to have a practical follow up guide that put the concepts into practice.
Suggested improvement
I was pointed at this resource, and I think it would be a great addition to the quick start guide. It has answered a lot of the basic questions I had.
Activity
story645 commented on Oct 28, 2022
Our plot lifecycle tutorial aims to be a putting it into practice guide. What sort of changes could we make to it so that it would be more helpful?
ruthpozuelo commented on Oct 28, 2022
A few things differ from both tutorials.
The tutorial I mentioned, it starts easy and then builds up incrementally until you have all the main transformations you would need on a chart.
It not only does this the conventional way, but it also shows how to iterate and create functions.
Lastly, it shows many common examples of different charts increasing the difficulty and explains it all beautifully.
It explains everything I have been wondering about in just one tutorial. First I have seen that does all the basics in one.
Just wonderful , but please ignore it if you don’t think it is useful!
story645 commented on Oct 28, 2022
No I totally agree with you/think it's useful, I'm just trying to sort out which parts exactly are useful to figure out how to incorporate it into our existing tutorials or sort out what would make a good tutorial. We cover a lot of this in our examples, so I'm wondering if a tutorial that basically organizes some of them would make sense?
ruthpozuelo commented on Oct 28, 2022
I understand you question.
I am still going through the tutorial (a lot to cover in there) so when I am done, I can give you my perspective as a new user on what parts I found important and why?
Will take me a week or two before I can put something together, but if it is helpful, I can get back to you with that.
story645 commented on Oct 28, 2022
Yeah take the time you need, but your feedback would be much appreciated. Also short notice but we have the new contributor meeting next week and that might be a good place to discuss these sorts of documentation contributions. https://scientific-python.org/calendars/
ruthpozuelo commented on Nov 4, 2022
It is a bit late for me to attend the meeting, but will give feedback here instead.
stefmolin commented on Nov 12, 2022
Somehow I stumbled upon this issue, so imagine my surprise to see a link to my content 😀 (and such high praise for it as well – much appreciated @ruthpozuelo)!
@story645 - I'm happy to go over how (and why) I designed this content, which is part of a workshop I present at conferences on data visualization in Python.
story645 commented on Nov 13, 2022
@stefmolin that'd be great! Also, I'm gonna point to our last attempt at creating a getting started type tutorial 'cause that might provide some context/guidance/pitfalls of why status quo #19183
story645 commented on Nov 30, 2022
Hi @stefmolin & @ruthpozuelo, if you've got time can you all check out #24498 and see if those examples would be helpful?
github-actions commented on Jan 19, 2026
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
story645 commented on Jan 19, 2026
I'm closing this not b/c it's actually not planned, but b/c resolving this is part of a larger discussion around documentation modality (#26389) and the getting started guide. Basically I don't think this issue is actionable w/o us deciding on a direction for the docs, so I'm gonna close w/ the potential to reopen if the fallout of a discussion leads to an actionable next step here.