This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, February 3, 2021, 03: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/ 9.9.0 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
Gutenberg 9.9.0 RC is included as part of WordPress 5.7
There are several bugs and regressions in the 5.7 project board which need assignees.
Please label any 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.-fix PRs that need to be cherry-picked into WordPress 5.7 with the Backport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. to WP Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RC label.
Please ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @noisysocks if you spot a Gutenberg bug or 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. that needs to be included in WordPress 5.7 and it will be added to the project board.
WordPress 5.7 Beta
WordPress Beta 1 was released 2 February. Work has been done on updating npm packages
in Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to contain all of the functionality that is in Gutenberg 9.9.
February monthly priorities. Along with Key Project updates.
Update from @nosolosw
- TT1-blocks theme has been updated to follow this new format but hasn’t been published to the theme repo yet.
- We’ve been working towards shipping parts of theme.json to 5.7 so themes could control the editor in a more fine-grained way. While there was a lot of progress, it proved premature given two outstanding issues that are unresolved in the format: how to express different templates/nested contexts & support the new direction for sidebars (controls that are shown/hidden) Addressing these issues would be our next focus.
- There’s a longer and more detailed update in the overview issue.
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 Widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor.
Update from @noisysocks
- Saving widgets bugs in GB28379 and GB28210 has been merged. We have plenty of E2E tests now to prevent that from happening again.
- Next priority is getting blocks in Customize → Widgets working. Work happening in GB28618.
Update from @isabel_brison
On the Navigation block front, Pages list block PR is ready for final review. I have a couple of related thoughts I’d like to discuss:
- How to best to render dynamic blocks in the editor (comments welcome on the issue!)
- Should block markup change depending on its context? E.g. if it’s rendered inside a certain block?
Navigation Editor screen.
Full Site Editing
Update by @ntsekouras
- Work on FSE Outreach Program, hoping to complete a “how to use 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/” Learn WordPress course this week.
- Shipped the What’s next in Gutenberg post, shared a quick update to the Versions in WordPress doc for 5.6.1 & 5.7.
- Did some triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!
- Mobile team merged the audio block work.
- Work on porting the search block to mobile.
- We are investigating a share extension on iOS The operating system used on iPhones and iPads..
- Working to default more users to the Gutenberg editor in the mobile apps.
- Triaging. Testing patches on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and design triage.
- @gwwar Kerry and I held a triage session in the core-editor Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
- Working documentation for setting up a local WP dev environment + testing for Core.
- Plan to create a Workshop on Learn.
I’m just coming back after a hiatus for most of last year due to moving and an addition to the family, focusing on 5.7 bugs as I get up to speed on all the new things like FSE.
- Look into remaining bug issues with the cover block.
- Planning to add some more unit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. to the Focal Point Picker to make it less prone to breaking.
- Working on a visual regression test, part of a wider effort to guard essential pieces against regressions e.g. when refactoring.
Submit your FSE related questions by Feb 15th! For the full run down of how I’ll approach gathering answers and where you can submit your questions. For a direct link to submit questions via a form (questions welcomed as comments on the post too).
For context, this is part of the #fse-outreach-experiment effort.
I’d like to update this outreach page as it’s a few years old now and would love to crowdsource links to include.
Please fix this bug in wp 5.7 editor. WordPress asking for me to save the page on exit without making any changes.
Comment by @paaljoachim I have followed up and added additional info to the trac ticket Created for both bug reports and feature development on the bug tracker.. – Ticket is fixed.
Would it be possible to confirm if we’d like a Playlist block in the core block library? If not what might next steps look like?
This issue was brought up as part of a core-editor triage. The issue is low priority. If anyone wants to work on it they are welcome to do so. Comment by @paaljoachim I have added a tutorial to the issue on how to create a Playlist using the Classic block.
We ended the Core Editor meeting with the final question…
Question for @paaljoachim what do you think editor will look act like once FSE is done working. I’m asking as a theme developer. Sometimes, I really find it hard to visualize the final version of the editor.
Reply from @paaljoachim I have been looking at FSE for a while now. A new user would expect to change everything they see on the screen. Which means we need to make it clear which section one is working in.