Improve contributor experience

[PLeVasseur]

Hey @plaindocs, this is the tracking issue I said I'd open for us to keep track of the contributions.

Can contain things like:

• make style guide contents clearer on how to write
• improving Sphinx usage
• improving extension as necessary for features
• improving CI / CD experience

Could you comment below? I can then assign this to you. Thanks again for the support!

[plaindocs]

Sure thing. Let's add #31 here already.

• Use RTD for pull request previews #31 get pull request previews working

[plaindocs]

Couple of suggestions here:

• use --debug by default on the pull request previews, so it's more clear what went wrong
• use typos-cli GHA
• lint rst

I'll take a look at the style guide when I get a minute

[PLeVasseur]

Both sound like good ideas!

[felix91gr]

The tasks here seem to be done. Should I close this issue? I was thinking that perhaps it could be made into a Tracking Issue for Contributor Ergonomics / Experience, but perhaps that role is better suited for a Project

[PLeVasseur]

@plaindocs -- have you got thoughts on this?

I think one good thing to do if treating this as a tracking issue would be to link issues that you've identified would be good for contributor experience here.

[felix91gr]

Oh, if we use it like that, then here are two things to add to that list:

• Regarding tag input in the New Guideline form
• Have a written explanation of how to fill the Guideline Form so everything is gucci #166

[plaindocs]

Hey folks, I'm back at the desk. I think a project is more suited than a tracking issue, but only if we're happy with overhead and commit to using it (as well as using them for other stuff). Overall I don't feel super strongly.

[PLeVasseur]

We created labels and filters for the kanban board, so let's use that now.

e.g. here's the Contributor Experience view.