Summary all our non-trivial initiatives

[camerons]

We don't have a good way to show the active status of each of the initiatives we are working on. (There are about 10 initiatives running in parallel, and another 10 to 20 initiatives in the pipeline waiting for an interested party to take them on.)

This would be very useful when onboarding new volunteers who are wondering how they can help.

I suggest that we set up a directory structure where each initiative can have its own "elevator pitch" front page.

It should:

• Be short, easy to maintain and easy to skim read - say two paragraphs.
• Explain what the initiative in a sentence or two.
• Include a status, which we periodically updated. We probably should make a call out to all projects every 3 months to update their status.
• Mention something about schedule.
• Included last time this page was updated.
• Include a point of contact (a real person who you can reach out to).
• Include communication channels, such as slack of email list.
• Potentially point to the home page of the initiative.

[camerons]

A starting point for what we are working on. I'm sure to have missed some projects. I've just included a suggested point of contact, not all people involved in the initiative.

• Information Architecture Guide (Lana)
  • Google Season of Docs (Lana, Jared, Morgan)
• Draft base template, to help with creating new templates (Viragi, Lana, Cameron)
• Improvements to our core doc type templates (All, more work needed)
• Guide for building a Style Guide (Alyssa)
• Initial results from the Glossary pilot. (Cameron, Ankita, Naini)
• Set up of the incubation repository (Morgan)
• Hugo site migration (Bryan, )
• Improved rigor in git contributor tooling, git hooks etc. - (Morgan, )
• Slack bots (Aidan, )
• Standard github doc pages to lift our project health scores (Alyssa)
• Maturing of our community processes (Cameron, Erin, others)
• Draft persona definitions (Aaron)
• Chronologue example project (Erin, Felicity)
• Knocking over bugs (Aidan, Aaron)
• Aggregating Code of Conducts together (Alyssa)
• Tech Writer Patterns, Anti-patterns and Tasks (Cameron)
  • Roadmap of tasks
• Presenting at events
• Proposal selection process, Prioritization guidelines, Opencollective account to receive money (Cameron, Erin, multiple others)
• Welcome committee setup (Aidan)
• Describe onboarding process (Derek, Alyssa, Morgan, Felicity)

[camerons]

@barbaricyawps has started material for a jump page: https://docs.google.com/document/d/1rDTngrVNaGVA05aUL7owcZH0Q6sd8SjX5MiKZNZ3PWg/edit#

[bwklein]

List Page for Working Groups: https://thegooddocsproject.dev/working-group/
Example Working Group Details Page: https://thegooddocsproject.dev/working-group/doctools-easy-button/

@camerons do these pages and new 'working-group' content section/type meet the needs of this request?

If they do, then should we close this issue and make a new set for all the outstanding groups, or leave this open until all relevant groups are represented in the site?

[camerons]

Thanks @bwklein , yes I think the working groups page addresses the needs of this task for the moment. (There are still a couple of edge projects which are not listed, but we can add them later as interest picks up.)