Thank you for opening your first PR into Matplotlib!

If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks.

You can also join us on gitter for real-time discussion.

For details on testing, writing docs, and our review process, please see the developer guide.
Please let us know if (and how) you use AI, it will help us give you better feedback on your PR.

We strive to be a welcoming and open project. Please follow our Code of Conduct.

Thanks for the PR, but tutorials don't have thumbnails b/c of the way the index page is written for tutorials. The solution for tutorials is to use the sphinx minigallery directive to grab the tutorial files, which may include a reorg of the tutorials landing page.

Thank you for the clarification!

I understand that tutorials use a different mechanism and that the correct
solution is to use the sphinx minigallery directive instead of
sphinx_gallery_thumbnail_number.

I will look into the tutorials landing page and explore how the
minigallery directive can be used to properly generate thumbnails.

Please let me know if there are specific files or examples I should start with.

Thank you for the guidance! I have removed the thumbnail variable from the Python script and successfully added the minigallery directive to the tutorial's index.rst landing page as requested.

This PR yields a page that looks exactly like the current tutorial landing page https://matplotlib.org/devdocs/tutorials/index.html

But also I don't think this is the right approach. I think if we were gonna add thumbnails to tutorials, the page should be restructured to use the minigallery directive to show thumbnails under each header.

Hi @story645, thank you so much for the review and the architectural direction!

I completely agree that restructuring the page to use the minigallery directive under each specific header will make the tutorial landing page much more visually useful. I will pivot my approach, restructure the index.rst file as you suggested, and push an updated commit shortly.

restructure the index.rst file

What is your plan here? Your comments concern me a bit b/c they're mirroring mine but not really engaging w/ the contents.

Thanks for pointing that out — that’s helpful.

Here’s what I’m thinking for the page:

• I’ll split the tutorials into sections based on how they’re already grouped (like more introductory vs more specific topics), instead of keeping everything in one list.
• Under each section, I’ll add a .. minigallery:: so each group shows its own thumbnails.
• I’ll keep the existing toctree (probably hidden) so navigation doesn’t break, but the visible page will be driven by these section-wise galleries.

So the idea is not just adding thumbnails, but actually changing how the page is structured.

I’ll try this locally and push an update so we can see how it looks.

putting to draft until the docs build well enough to show the proposal - also please update the PR title to what this PR is doing now.

I think this needs some feedback from other maintainers too, but I think using the sphinx gallery machinery is an improvement over hardcoding the html:
https://output.circle-artifacts.com/output/job/d6c63851-f51d-42ef-ab79-3b17f7f68e21/artifacts/0/doc/build/html/tutorials/index.html

Thanks for the approval and the suggestion!

I’ve looked into the ordering and updated the minigallery to better match the original tutorial order while keeping the changes minimal.

Let me know if you’d prefer a different approach.

@story645 Thanks for the feedback!

I’ve updated the implementation to preserve the intended ordering, and all checks are now passing. The docs build also looks correct on my end.

Please let me know if any further changes are needed.