Thanks so much for writing up this article and including the GitHub issue I authored a few months ago. When I saw the title, I was hoping it would be mentioned as I’ve been keen to create some momentum behind this very necessary work. In talking with a variety of folks about Gutenberg documentation and, in my own experience, I’ve found too that there’s a gap when it comes to documentation. It seems to be born out of the tension between Gutenberg developers having institutional knowledge and folks who could work on documentation feeling like they don’t have the perceived expertise to help. To build on this conversation and topic, I wanted to share a few ways people can still get involved even if you don’t know dear Gutenberg inside and out. There are likely more ways so just see this as a starting point:

Create issues with specific questions that you are trying to do that is not documented.
Review documentation/go through the tutorials to share what can be improved and what’s missing in the form of new issues.
Start writing documentation in Github/Gutenberg repo and ask others to fill in details. Gutenberg developers aren’t necessarily documentation experts so anything that can be done to wed the two would be amazing.
Help with organizing the logistics of documentation.

This last option is what I did and a big way I like to help when I don’t have expertise! I also opened an issue just today about updating the FAQ for Gutenberg after noticing it was out of date while responding to a different issue: https://github.com/WordPress/gutenberg/issues/23763 I’m not a Gutenberg developer but still want to help move things forward and am really excited to see the work people like Marcus have done here around building out better resources for block tutorials. Hopefully, the above examples can help bridge that gap too for people to feel more empowered to help out with docs.

I’d love to hear from others about what can be done to make this easier as well. I’m @annezazu on WordPress.org slack and always welcome pings 🙂