docs: Improve Monthly Challenge Team Documentation

[adiati98]

Motivation

As our monthly challenges are evolving, we need to update our documentation for the Monthly Challenge Team to accomodate the changes. It will be very helpful for new volunteers to onboard themselves when we have updated documentation.

Suggestions

Let's gradually improving the docs for Monthly Challenge Team as we go and when we know the structure for every challenge.

We can update the docs we have now (and rename the files accordingly). Or we can create a new file for each challenge, and archive the old one in a folder once the challenge is updated.

To Do

General Docs

• Create how to update monthly challenge page on the website docs.
• Update leader-docs.md.

Update VC Challenges (in no particular order)

• Hacktoberfest
• Month of Learning
• Get Job Ready
• Creative Community Challenge
• Blogging Challenge
• Preptember
• Healthy Habits for Happy Devs
• Build in Public
• Community Kindness
• Creating Audio/Visual content
• Pairing
• Month of Feedback
• Mid-Year Check-In
• New Year, New Goals (NEW!)

Contents for every challenge

Every monthly challenge will have following contents:

• What to prepare for the challenge — blog post, repo, VC members only site (like Hacktoberfest Initiative and Blogging challenge), etc.
• Wordings for async check-ins on Slack — this can be adjusted for every challenge. But we might want to document the adjustments as our record.

[adiati98]

@danieltott @BekahHW,
Me and/or @dominicduffin1 will update our monthly challenge documentation gradually.

Any thoughts on this?

I have examples of a PR and two draft PRs here.

[danieltott]

I think this is fine. If there is any specific stuff we did in previous years that we're not doing any more, it'd be good to archive that. But in general this all sounds good 👍🏼

[danieltott]

The other change I would make is make all of the facilitators-guide.md files README.md files so that they just show up when you land on the directory.