This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, 30 June, 2021, 10:00 AM EDT in Slack. Moderated by @itsjusteileen.
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/ 11.0 Plugin 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
Gutenberg 11. RC 1 released on 30 June. The link includes release notes.
The first Release Candidate is available. A few quick things from this post:
- Theme and plugin authors should test and update their readme file.
For theme authors, @youknowriad has a post on updating your theme for content width to work with global styles and settings.
- For the ployglots out there, this release marks the Hard String Freeze for 5.8.
- Everyone is needed for final testing!
This might also be a good time to mention deprecated Block Editor API’s. See @youknowriad posts for more information.
View the complete WordPress 5.8 development cycle.
Key Project Updates
Full Site Editing
See the full 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 Editor dev note for a overview description of the new feature.
@mattchowning provided the update.
Enabled tests for the Cover Block
- Gallery block refactor
- Tooltips to help with Editor Onboarding
- Block inserter search
- Further Editor Onboarding improvements: a help section and a “new” badge for new blocks
- Adding new integration tests for mobile embed block
- Global Style Support for colors
@mkaz provided the update.
- Working on the overlay background colors for responsive menu and dropdowns is close
- fixing up the Navigation Editor screen and working on improving tests.
@nosolosw provided the update.
The current focus is polishing the theme.json experience by finding and fixing bugs that are back ported to the Betas/RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).. Two things left are:
- 5779 Extract strings provided via theme.json for translation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. in translate.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. This depends on a new wp-cli WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ release that includes this PR and then updating the meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. infrastructure.
- 53494 The global styles need to be enqueued in the footer for classic themes that opt-in into per-block asset loading.
The dev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for theme.json was published.
@Zeb is looking for review on his TOC Block PR after fixing the infinite-loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. bug 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. in the Table of Contents block PR.
Making a little progress on nav block menu item setup states, with a little summary here. Otherwise making PRs for a variety of small issues, in fact some of them just need your green checkmarks!
Mainly doing FSE Outreach Program wrangling in the form of shipping the theme.json call for testing post with two lovely collaborators (join in on the fun!) and a “How to Test FSE items for 5.8” post shipping today. I plan to turn my attention towards user docs starting at the end of this week through to the release to help out there alongside responding to feedback that comes in. I also want to spend more time in the land of GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ triaging.
- Updated documentation for ServerSideRender package.
- Added check to avoid applying layout configs twice with 5.8.
- Worked on adding busy state to the template creation modal. I would love some :eyes: on this PR.
- Pushed improved check for Image Block “switch to cover” action.
- Testing issues and helping out with PR reviews.
In preparation for the next months after 5.8, we are refining the Site Editing scope, closing issues that have been completed for the most part, and creating new overview issues with the upcoming work.
I am a one person mechanical end to end test runner for the block based widgets editor
What’s the status of FSE in 5.8?
@ironwiller Will there going to be a change at WP 5.8 and have an actual FSE or this one is an ongoing project till the end of the year or even beyond?
@mamaduka Template Mode is on for themes that provide theme.json` file or have special support flag.
@annezazu You can think of full site editing as a collection of features that brings the familiar experience of blocks to all parts of your site. Because it’s a collection of features, it means there’s the option to only release what’s stable and ready in a more gradual way rather than all at once! So… think of it less as an “on/off switch” approach for releasing FSE and more as a steady drip of features being released. In terms of what’s coming, check out this post or you can watch this recent video from another community member that goes over the major features planned. While some items related to FSE are going to be released, like Query Loop Block or Template Editing Mode for classic themes that opt in, this work will be ongoing and is expected to continue beyond this year (my best guess).
Embeds in iFrames Issue
Replace white screen on home page
Is there a means to refrain from seeing white screen on home page if a theme just has a theme.json in it? I’ve tested with TwentySomething themes and does not seem to happen, therefore wondering if there is a deprecation jig in place for TwentySomething themes only to gracefully fail. Query Monitor shows wp-content/plugins/gutenberg/lib/template-canvas.php being loaded as template on home page. This is with WP 5.8 RC1-51270 and Gutenberg 10.9.1 active. It looks like an issue needs to be created for this topic for general review.