Skip to content

DOC: apply toc styling to remove nesting #28557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

story645
Copy link
Member

@story645 story645 commented Jul 12, 2024

PR summary

Use section-toc css class to strip out the page title/nesting for the toctrees where the page is already given by the section title.
Here's one example, but I think it makes the page look cleaner:

old new
image image

PR checklist

@story645
Copy link
Member Author

failures unrelated b/c this is pure docs

@story645 story645 added the Documentation: website layout/behavior/styling changes label Jul 15, 2024
@story645
Copy link
Member Author

story645 commented Jul 18, 2024

So, of course this PR has run away into some bigger content changes 🤦‍♀️:

  • upgrades to sphinx 7.4.0 branch (this may require updates to sphinx gallery)
  • added link to devel/index to landingpage contribute copy
  • changes section title: "new contributors"->"contributing guide"
    • am slightly ambivalent about this change, but am thinking maybe it'll be more read if it's not cast as only for newbies b/c it's purpose is more so to provide information on what can be contributed, where/how, and what resources are available for contributors
  • pulled some copy out of triage to anchor the new "issues" section.
  • tightened up the "submit bug" and "new issue" buttons cause I thought the stuff I cut was either redundant or applied to both.
  • inspired by new issues copy, unraveled the "new contributors should xyz" paragraph to instead add copy to each section on why someone should read it -> new contributors get guidance and experienced contributors can skim/skip to links.

Like I mentioned in this comment, I'm trying to avoid major restructure territory because I've got a rough plan (that yes, I figure will be up for discussion) for more clean up/polishing and this was supposed to be a "yay, new CSS style!" PR:

graph TD;
    A(is the issue) -->unresolvable-->C(explain why <br /> technically infeasible <br /> or not aligned with <br /> values/mission/scope/etc);
    A-->resolved--> B(explain why, <br /> link to docs, API, etc) ;
    A-->resolvable-->D(work w/ issue author <br /> on an implementable <br /> code/docs solution)
   A-->E(not sure)-->F(ask for more information) -->A;
Loading

@github-actions github-actions bot added the Documentation: devdocs files in doc/devel label Jul 18, 2024
Copy link
Member

@timhoffm timhoffm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Take or leave the comments. Can self-merge afterwards.

environment.yml Outdated
@@ -37,7 +37,7 @@ dependencies:
- packaging>=20
- pydata-sphinx-theme~=0.15.0
- pyyaml
- sphinx>=3.0.0,!=6.1.2
- sphinx>=7.4.0,!=6.1.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure we want to be that aggressive. On a technical side, it's ok. The only concern is that we break every dev envionment out there. When this is in, if somebody does a rebase onto master, their sphinx-build will fail because their dev env has an older version of sphinx and cannot handle :class: in .. toctree:. I'd slightly prefer to still go with the .. rst-class variant for now, and change some time in the future.

Sorry if my comment has made you believe I advocate for switching right now. But please decide yourself.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll change it back, I'm very : shrugs: about this, but what is our timeline for migrating given that we currently set our min to 3.0? Is it gonna depend more on the sphinx gallery min?

@story645 story645 force-pushed the landing-page branch 2 times, most recently from 15d2b30 to 9bef3f1 Compare July 18, 2024 15:38
@story645 story645 changed the title applying toc styling to remove nesting DOC: apply toc styling to remove nesting Jul 18, 2024
@story645 story645 mentioned this pull request Jul 18, 2024
11 tasks
change "new contributors" section title to "contributing guide"
add copy to anchor each section of devel/index
small doc cleanups based on above
@story645 story645 merged commit 0eb624d into matplotlib:main Jul 23, 2024
31 of 32 checks passed
@story645
Copy link
Member Author

self merged based on approval from @timhoffm #28557 (review)

@story645 story645 deleted the landing-page branch July 23, 2024 05:23
@QuLogic QuLogic added this to the v3.10.0 milestone Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation: devdocs files in doc/devel Documentation: website layout/behavior/styling changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants