This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, October 6 2021, 04:00 PM GMT+1. in Slack. Moderated by @paaljoachim.
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/ 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 releases
Gutenberg 11.7 RC Thanks to @zieladam for tackling the release.
What’s new in Gutenberg 11.6 release notes. Thanks to @ntsekouras for writing the notes and handling the release.
October 14th is the date when the decision for “Go, no go” for Full Site Editing to be included in WordPress 5.9 will be decided.
Preliminary Road to 5.9. A quick overview of the main areas and features currently underway for 5.9 in Gutenberg.
What’s next in Gutenberg
What’s next in Gutenberg: Mid-September 2021.
Key project updates
Based on the scope for Site Editing projects.
- No update currently mentioned. Check out the Full Site Editing label of current issues in the Gutenberg repo on Github GitHub is a website that offers online implementation of git repositories that can 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/.
Navigation 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. & Navigation Editor
Update – 2021-10-06
- Discussion is still continuing on the best way to ensure interoperability and compatibility between Nav block and Nav Editor.
- Looks like there will be a Hallway Hangout on Wednesday 13th October (TBC). Agenda will be posted to Make Blog (versus network, site).
- @talldan posted a nice summary of current state of things in Slack. There’s a lot of great energy in the team right now and we are looking to coalesce around a shared set of objectives.
- Top 5 embeds blocks directly available in the block picker, Retry feature, specific embed’s icon and label in placeholder and bottom sheets.
- Added a way to contact support from inside editor.
- Added automated tests for editor onboarding.
- Fixed an image block regression 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. causing the images to render with a fixed height and a 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. preventing the columns block from rendering in the editor in some occasions.
- Embed block improvements.
- GSS Font size, line height, colors.
Worked on Update Callers to handle when getBlockType return undefined (PR has been merged.)
- Helping with PR reviews and testing.
- Merged the last PR for optimizing
- Started working on remaining items in the individual block locking feature.
- Any issues with switching Gutenberg examples repo (https://github.com/WordPress/gutenberg-examples) default branch to trunk? It’ll be nice to have it consistent.
- This week’s Live Q & A is tomorrow at 16:00 UTC Going from classic to block-based theme building
- Next week, Helen, Mark and Riad discuss how to make it easier to build custom blocks
- On 10/28 LQA is with members of the BuddyPress Team discussion how to convert widgets to blocks.
Times and links are all available on Gutenbergtimes.com
- Can someone create a WP 5.9 Github project board to where we can focus on Full Site Editing and general 5.9 issues/PR’s? As it has earlier been very useful to have the project board to check for issues related to a release.
I can kick it off, sure. I was looking forward to the go/no-go demo next week so that we can have a more clear scope of the must-haves before creating it.
- The following PR needs some discussion: Use theme mods for templates and template parts
“I was referred to this PR, and it seems like it had a lot of traction in 5.8 but didn’t make it in time. It’s still there needing reviews and possibly a decision for 5.9 and it seems like something that shouldn’t be left too late, otherwise the same will happen again.
(I would review it myself, but I don’t really have the full knowledge required).”
It would be great if there was a recap summary which captures the current state of discussion. It seems pretty important for the utility of Template Parts. (Dave added a comment.)
- In Gutenberg 11.6 the ServerSideRender component was updated to display the existing content while the new response is fetched. There is bug with this change which I outlined here: https://github.com/WordPress/gutenberg/pull/28297#issuecomment-932723947. I thought it might be useful to bring it up again here in light of the recent Gutenberg 11.7 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). release (thanks @zieladam!).
Bug issue opened here: Bug in ServerSideRender where the block disappears during render.
- I would like to ask if anyone here had any concerns about adding a hook (or some other solution) to ServerSideRender which allows a plugin author to trigger something after a block has rendered.
I opened a Feature Request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. for this on Github here with a further explanation: https://github.com/WordPress/gutenberg/issues/35294
- I found this forum post asking if there is a separate Read More block for use in a Query 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.? Currently it seems the Read more is locked inside the Excerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.. There is also a Gutenberg issue for it here: Could we have Read more link as a stand alone block?