Introducing a new block editor handbook scrub

There is currently a large number of outstanding issues in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. repository with the [Type] Developer Documentation label. We think that it would help to bring the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor handbook more up-to-date and correct any errors and/or omissions that may exist if some of the backlog of issues were addressed.

Starting Thursday, March 30, 2023, at 13:00, we will begin holding a weekly meeting to review and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. developer documentation issues in the Gutenberg repository. These meetings will take place every Thursday at 13:00 UTC in the #core-editor room.

During these meetings we will:

  1. Review issues labeled with [Type] Developer Documentation starting with the oldest and moving forward.
  2. Decide on what ( if any ) action to take for the issue and if possible, assign it.

This is a great opportunity for anyone looking to contribute to the Gutenberg project or move their tickets forward. 

@welcher and @mburridge will facilitate the meetings but anyone who is interested in leading them is more than welcome.

We hope you will join us. What do you think? Any questions? Leave a comment below.

Thanks to @greenshady and @mburridge for reviewing this post

#block-editor-handbook, #core, #documentation, #gutenberg