I’ve recently volunteered to be the Gutenberg developer documentation team rep.
This is a proposal of next steps for a friendly Gutenberg developer documentation, useful for newcomers.
For more context about the current state about Gutenberg dev docs, and its challenges, read this: http://wayback.fauppsala.se:80/wayback/20200830165731/https://wptavern.com/wordpress-contributors-seek-sponsorship-for-improving-gutenberg-developer-docs.
The plan is to build on the existing documentation (http://wayback.fauppsala.se:80/wayback/20200830165731/https://developer.wordpress.org/block-editor/developers) to arrive at a better structured doc.
Here are some aspects that I thought the team could focus its discussions and reflections to get started.
Where are we at now?
It is essential to have an overview of existing documentation. Both the one present on http://wayback.fauppsala.se:80/wayback/20200830165731/https://developer.wordpress.org/block-editor/developers, on GitHub (if there is any), and also those in progress. This is to avoid dispersing our efforts, and to take advantage of the work already done by other contributors and volunteers.
What should be included?
In my view, one of the first step would be to agree on what should be included in the new documentation. There are currently many concepts (Core concepts, APIs, etc…) that can be useful for developers using the block editor. Some of them are already present in the current documentation. Others are in the codebase on the project’s GitHub repository.
A new structure?
The current structure of Gutenberg’s developer documentation is one of the aspects that makes it not friendly at all. For example, the home page of the documentation starts with the chapter “Creating Blocks”. A beginner is like thrown into the cauldron without knowing the prerequisites. Several contributors also address the question on GitHub here http://wayback.fauppsala.se:80/wayback/20200830165731/https://github.com/WordPress/gutenberg/issues/22151.
In this regard, I think we could learn from examples of documentation such as Gatsby.js http://wayback.fauppsala.se:80/wayback/20200830165731/https://www.gatsbyjs.org/docs (a quick start/tutorial, then a reference guide that discusses key concepts in a more or less defined order).
Cross-team collaboration
How do we want to collaborate with the different teams to make this happen? From here I see the core-editor team playing an important role, given their experience with the block editor development.
What’s next?
At this stage, we are only at the discussion stage, to see what is feasible and the best way to do it. If you are interested in helping with any of the steps, please feel free to comment. Also, if you have other points that you think are essential or need to be discussed in this plan, please feel free to mention them in your comments.
Season of Docs 2020
With the Season of Docs starting in a few weeks, I think this could be a great opportunity to move forward on that plan.
There are two projects in particular that could help:
- Project #6 with @kenshino: Improve Existing Development Documentation and Handbooks and
- Project #8 with @milana_cap: Extending Block Editor.
#block-editor, #documentation
What exciting news and a warm welcome to @tacitonic and @dmivelli.
@timohaver @cbringmann
Thanks for the warm welcome. I’m excited to be here and can’t wait to work with the team!
I owe my thanks to @kenshino, @estelaris, @cbringmann, @milana_cap, @timohaver, @bph, @sukafia, @softservenet and the entire Docs team. Congratulations to @dmivelli as well! Thrilled to work with the team!
This is amazing. Congrats team!
Oh, this is so cool! Welcome everyone. I look forward to the wonderful work that’s coming. 🙂