WordPress 5.9 Editor Update – 26 October

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. https://wordpress.org/gutenberg/ 11.9 (the last pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party release which will make its way into WP 5.9) will be cut on November 3 which is in 9 days!

The merge to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for this release will be tricky. I’m seeking volunteers to assist with the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. Let me know if you can help.

@mamaduka has ran an audit of our __experimental APIs. Please give it a look over.

I asked around to identity what the “must have” enhancements are for this release and have added them to the WordPress 5.9 Must-Haves project board. Please regularly check in with this project board. There are a bunch of bugs in the board, too, and you should also pay attention to them, but they’re slightly less important because bugs can be addressed after the feature freeze.

Here’s a overview of the “must have” enhancements:

• Template editor (owner: @kevin940726)
  • Series of bugs and shortcomings faced during 5.9 go/no go prep #35662 (unassigned!)
  • Site Editing block placeholders #35501 (unassigned!)
  • Site Editor: not possible to change site icon #29126 (unassigned!)
  • FSE: Finalizing the name and menu item placement #29630 (@kellychoffman @kevin940726
  • Improving multi-entity saving UI method. #31456 (@bernhard-reiter)
  • Template part editor: adjust height to contents #35512 (@kevin940726)
  • Ensure the Customizer is available for plugins or theme options when using a FSE theme #35874 (@clorith)
• Styling (owner: @youknowriad)
  • Global Styles: Form elements #29167 (unassigned!)
  • Add Button Hover Color options on Button Block #4543 (unassigned!)
  • Start a Global Styles endpoint and use it in the site editor #35801 (@youknowriad)
  • Typography block support: add typography support and defaults #34064 (@ramonopoly)
• Patterns (owner: @ntsekouras)
• Navigation 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. (owner: @talldanwp)
  • Navigation: Add an API to retrieve content-only inner blocks #30674 (unassigned!)
  • Migrate buttons & navigation to flex layout #34872 (@isabel_brison)
  • Blocks that link: Provide a split label/URL control and placeholder state #30170 (@get_dave)
  • Navigation Block: save data to a custom post type #34612 (@talldanwp)
  • Navigation block – preserve navigation block data on theme switching #35750 (@get_dave)
• Twenty Twenty-two (owner: @kjellr)
  • [Block Themes] Consider an FSE-compatible approach to starter content #35680 (unassigned!)
  • Discussion: Including images in FSE HTML templates #31815 (unassigned!)
  • Flex Layout: Allow control over flex-wrap #35525 (unassigned!)
  • i18n: Add pattern block #33217 (@scruffian)
  • [Post Comments Block] Displays “Comments are closed” messages on pages, even when comments have never been open #35732 (@jffng)

🤙

#core-editor #5-9