[📝 Docs]: Blog Post: Announcement of GSOD Documentation Contribution & Progress

[kwennB]

What Docs changes are you proposing?

This is an announcement blog post for the community to share the JSON Schema documentation efforts so far.

Here is a table of contents draft.

Proposed title: Feedback during JSON Schema research/ docs audit

Table of Content

Introduction.

• The vision of the project,
• The goals of our project, and
• How the GSoD subproject fits into the overall vision.
• GSOD contributors and brief on who handles what in the project, although this may be shared in minor detail.

  Work completed (May-August)

• Documentation audit
• User journey
  • Discovery
  • Evaluation
  • Adoption & Learning
  • Implementation & Validation
  • Troubleshooting
  • Contributing and Advocacy
  • Feedback. (The feedback based on what we’ve covered so far;;)
  • Structure/Format (Section heading)
  • Navigation
  • Most defaulting Pages
  • Website fixes
  • Would also cover the good things the JSON documentation has and the opportunities for improvement.

    Future Plans

• Remaining tasks until project completion
• Long-term documentation maintenance strategy

  How you can contribute

• Meetings hours
• Good first issues
• Work-review

  Conclusion

• Call to Action
• Invite for community review and contributions
• How to get started (links to GitHub, communication channels, etc.)

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[benjagm]

Thanks for this issue @kwennB . In the feedback part I suggest focussing on the developer journeys (Miro) instead of the specific actions and link the related issue 2 issues for more details.

[benjagm]

IMHO one important call to action is to invite people to join the discussion of the GSoD issues in progress and provide feedback.

[kwennB]

Hi @benjagm, Could you take another look at the outline? It has been updated.