About point 2 - contributor guides and reaching out to prospective writers,
CTA is a systemic way to show what documentation contributions there are and how to join. The link has issue ticket opened.
Triage by subject matter specialism
However, CTA is not effective to meeting demand for technical reviewers for articles that are outdated. We could find list of subject matter experts from previous contributions, various working groups and dev mailing list. We just need to reach out to them for volunteering technical reviews (without long-term commitment for maintaining docs) based on topics. Reviewers in Quick Docs are already doing this. We just need to scale up by subject matter specialism in respective working group.
- what are top 10 most asked questions in Ask Fedora in last 12 months? (installation guides)
- what are top 10 viewed pages/search keywords? (No 1 viewed page is EPEL)
Our messaging needs to be tailored to existing contributors. So CommsBlog or Discourse may be a better medium to reach right people.
Collaboration with Join SIG
Instead of overcrowding the Docs home page with banner (space constraint and potential objection to the idea of CTA banner), we could team up with Join SIG to onboard prospective members who are interested in various Docs contributions - UX, technical writing and workflow specialist. I dipped my toes into Join SIG already.
https://pagure.io/fedora-join/Welcome-to-Fedora/issues
Contributor guides
We have some guides. If anyone volunteers to improve them, I appreciate it. Imperfect guides have been an opportunity for me to tweak and improve the guides, and practice Git workflow. I’m happy to answer any questions from users and prospective contributors.