More than 48 contributors participated in this 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/ releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. It marks the addition of the very expected Group 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. (sometimes referred to as container or section block). It’s a minimal version at the moment and improvements about the flows to add inner blocks, group/ungroup blocks are expected in follow-up releases.

The bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes from this release will be backported to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in order to ship in the upcoming WordPress 5.2 release.

This release includes a lot of improvements to existing blocks and flows.

5.5 🇨🇿

Features

• Add a new Group block.
• Add vertical alignment support to the Media & Text block.
• Add the image fill option to the Media & Text block.

Enhancements

• Improvements to the Image Block flows.
• Automatically add `mailto:` to email addresses when linking.
• Add visual handles for side resizers for various blocks.
• Improve the performance of the annotations by avoiding excessive memoization.
• Announce the color accessibility issues to screen readers.
• Add enum block attributes validation to browser block parser.
• Use a consistent grey background in the ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. block.
• Improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) of video block select poster image.
• Respect prefers-reduced-motion for fixed backgrounds in Cover block.
• Prevent ArrowLeft key press in multi-line selection from prematurely triggering multi-selection.

Bug Fixes

• Avoid keeping the RichText value in cache indefinitely.
• Fix the post title input borders in the code editor.
• Fix the block restrictions to insert, replace or move blocks.
• Select gallery images on focus.
• Fix removing gallery images on delete/backspace key press.
• Fix small visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in the block autocompete popover.
• Fix the data module resolver resolution status.
• Avoid saving metaboxes when previewing changes.
• Fix selecting the separator block.
• Fix displaying the color palette tooltips on hover.
• Fix Firefox/NVDA bug not announcing the toggle settings button.
• Fix arrow navigation in paragraph blocks with backgrounds.
• Fix the columns block click to select.
• Fix post dirtiness after fetching reusable blocks.
• Fix the hover and focus styles for buttons with the isBusy prop.
• Remove the box shadow from the side inserter button.
• Changing the region navigation shortcuts to avoid conflicts.
• Fix space insertion in the Button block in Firefox.
• Prevent the link popover from animating constantly as we type.
• Fix the warning triggered by clearing the height of the spacer block.
• Fix undo behavior after fresh post loading.

Documentation

• Add design documentation to the Modal component.
• Clarify the CSS naming coding guidelines.
• Add InspectorControls usage example.
• Tweaks and typos: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13.

Various

• Bootstrap the design of the new widgets screen (non functional yet).
• Reorganization of the block-library code base:
  • Use a babel 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 to load block.json files.
  • Introduce block.json metadata for all client side blocks.
  • Move the edit functions and the icons to separate files.
  • Move the transforms and save functions to separate files.
• Add forwardRef support to the PlainText component.
• Support Button Block Appender in the InnerBlocks component.
• Unset the focal point attributes from the Cover block if not needed.
• Consistently return promises from the data module action calls.
• Remove obsolete CSS currentColor usage.
• Improve the e2e test CLI arguments and docs.
• Improve the e2e test login stability on MacOS.
• Remove is-plain-obj package dependency.
• Remove invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. urls and ids from media test fixtures.
• Remove the deprecated Gutenberg plugin functions slated for 5.4 and 5.5.
• remove or rename undocumented RichText package functions and constants.
• Adjust paragraph block spacing to use standardised variables.
• Allow spaces in file paths for package build process.
• Update pre-commit to check modified files only.
• Improve the performance of the webpack build configuration.
• Update dependencies with known vulnerabilities.
• Fix typo in variable names.

Mobile

• Accessibility improvements to the Button component.
• Enhance the unsupported block type.
• Fix image upload progress not being displayed consistently.
• Support copy/pasting images.
• Add the list block.
• Visual refinements for the native nextpage block.
• Fix importing the column block.
• Remove DOM logic from the list block toolbar.
• Put the caret at the end of the text field after merging blocks.
• Fix caret position after inline paste.

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience, but is adequate for spotting variations in performance.

Version	Loading Time	KeyPress event (typing)
Gutenberg 5.5.0	6.4s	71.1ms
Gutenberg 5.4.0	6.5s	78.5ms
Gutenberg 4.8 (WordPress 5.1)	8.6s	154.1ms
Gutenberg 4.7 (WordPress 5.0)	11.2s	191.44ms

---

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg, #gutenberg-new