Document our "community approach"

[mfisher87]

We have a lot of things going at once to help build and sustain our community. It's really hard to see all of them holistically. I think we should create a documentation page where folks who want to learn from our community approach can take a holistic look at all the things we're doing, many of which may be hidden to folks without specific knowledge.

• Hack days
• CI & CDelivery
• CI & CDigiorno (it's not delivery, it's deployment 🙄) for docs
• Documentation previews in PRs
• Issue labels, emphasizing "good first issue"
• ... and many more

Maybe future:

• devcontainer documentation editing UX
• PR / issue templates (Create issue templates / forms #281)
• Experience reports (Encourage experience reports #575)

Having such a page will also help us remember what we're supposed to be doing and keep doing those things, as well as identifying opportunities for simplification or enhancing our approach by viewing it from "afar".

In terms of documentation structure, I suggest "User Guide > Community overview"?

[Sherwin-14]

@mfisher87 Hey I think this is similar to the one we just did. Any specific opinions on this?

[mfisher87]

Hey, @Sherwin-14 thanks for your interest in this one! I think this ticket needs some more info. Specifically, we've had recent discussions about building a "community playbook" along the lines of this stellar example by Parsl's community manager @sophie-bui! We may even make that into its own webpage separate from our docs, we're not quite sure yet.

@asteiker any thoughts on portions of this work that may be startable now, or do we need to give it all more thought? Maybe we can set up a breakout room in a hack day (today? 🤷) to discuss?