Developer workflow improvements + PR clean up

[choldgraf]

Description

@damianavila and I wanted to carve out a few specific improvements to the developer workflow to work on as a part of the NumFocus grant. This issue is a bit of an experiment at trying to do a mini "project" with some issues that are grouped by a particular theme/goal.

The goal of this work is to make it easier for people to quickly get oriented with developing the theme, making small contributions to either the documentation or the theme's SCSS/JS, and reduces some of the risk associated with shipping bugs and such. If there's anything really important that people think should be included as a part of this focused effort, feel free to make suggestions here!

Where we're keeping track of work

We're keeping track of the major work items in this project: https://github.com/orgs/pydata/projects/2/views/1

Timebox plan

We'll try to get as much done on this project before Wednesday the 19th and then re-assess whether we want to continue in this direction, or close out the project and move on to other things.

[drammock]

the projects link gives me a 404... is it private?

[choldgraf]

oh I bet it's because GitHub makes projects private by default, try again

[jorisvandenbossche]

Somewhat related to development workflow, shall we rename master to main? (the majority of projects I contribute to starts to use main)

[consideRatio]

2i2c team meeting notes about this issue

• Documentation improvement has landed! 🎉
• This issue is representing work in pydata/pydata-sphinx-theme and linked project contains more info on ongoing work. It is a somewhat moving target.
• Current work: document release process, reduce amount of current open PRs where two/three PRs needs to get merged to avoid conflicts.

[damianavila]

We have improved documentation in #538
We merged a lot of PRs since Jan 6 (when this issue was created): https://github.com/pydata/pydata-sphinx-theme/pulls?page=2&q=is%3Apr+is%3Aclosed+merged%3A%3E2022-01-06

And we have another issue with the ongoing work/plan: #610

Let's just close this one!