Enhance contributor guide using tables or diagrams

[asteiker]

This is a broad issue and could see it being interwoven with others under #576. As part of the CSCCE Birdaro training, several "playbook" components were introduced and evaluated, and tabular or other visual presentations were emphasized as being valuable tools to describe a project's community model. https://earthaccess.readthedocs.io/en/latest/contributing/triaging/#issue-triaging-workflow is a great example of what we have already!

I could see additional tables or diagrams being useful for describing our:

• Communication platforms
  • Delineating use cases across GH Discussions, vs Zulip, vs Slack.
  • See https://coderefinery.github.io/manuals/chat/ for detailed "how-to", and https://openrefine.org/community for a more high-level table of ways to connect.
• Developer tools as described in Document our "community approach" #576 (CI/CD, how we use issue templates, etc.).
• Probably many other things!

[mfisher87]

I think this is great, and we should do it!

But one thing I don't like about tables/diagrams is they're hard to remember to maintain, and can be hard to maintain if we decouple the source for the diagram (e.g. a photoshop or illustrator document) from the repository. I'd like to use Mermaid or some other Git-friendly solution (Excalidraw can export to SVGs that act both as source and visualization) as much as possible to keep the source in our repository.