As we dive into the block 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.-based widgets screen, foundational work is required to support using the Gutenberg 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/ editor outside the Post Editor context. This release falls into this category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. of releases where it’s more about building the foundations and making the Gutenberg modules more flexible to support these new use-cases.
It introduces a new
@wordpress/block-editor module allowing building block editors outside the post editor context and even outside the WordPress Admin (and super admin) context. This has some costs on the performance of the keypress events while working on very long posts that we hope to alleviate in the upcoming releases.
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.2.0||11.7 seconds||57.8 ms|
|Gutenberg 5.1.0||11.4 seconds||22.25 ms|
|Gutenberg 4.8 (WordPress 5.1)||15.1 seconds||126 ms|
|Gutenberg 4.7 (WordPress 5.0)||16 seconds||185.2 ms|
👏 Kudos to all the contributors. Thank you.