This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held 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, on Wednesday, July 29, 2020, 14:00 UTC.
WordPress 5.5 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). 1
The first release candidate for WordPress 5.5 is now available. This is an important milestone in the community’s progress toward the final release of WordPress.
Thank you to all of the contributors who tested the 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
Project Board For WordPress 5.5
The remaining issues are located in the Project board.
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/ 8.6
Gutenberg 8.6 was relased on 22nd July.
What is next in Gutenberg for July.
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.
block variations. (https://github.com/WordPress/gutenberg/pull/24090)
Working on core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. media block editor proposal
Design work continues for the new editor sidebar
Testing in FSE. Moving to a new machine and will need to give @paaljoachim, @mkaz, and @Noah Allen dev environment tutorial a run on setting up from scratch for testing Gutenberg.
- Merged the last remaining PRs for Block Patterns and tested across Core default themes.
- Been helping with testing and feedback on various a11y 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)-related issues
- WP5.5: Review fix/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. PRs, review/help with dev notes 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
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.
- Review many PRs or comment in issues
- Try to improve Docker performance on macOS (24001)
- Support some other contributors at an individual level
I’m working on a flow for creating a template from scratch – Currently, I’m exploring “designing” a layout via document-level grid. I’m also planning a jam session or two next week.
- Focused on in-toolbar link editing (#24021)
- Investigating the way forward for the widgets editor
- Working on fixing e2e tests on the AutosaveMonitor fix in #23962
- Continuing with Design Tools Efforts (in general)
- Focus lately has been advancing
@wordpress/components in the spirit of the new “G2” designs. Approaching it systematically from foundations (much needed IMO) rather than applying tweaks on top.
- Got a PR merged that moves the reusable block’s “Convert to regular blocks” button to the block toolbar! https://github.com/WordPress/gutenberg/pull/24066
- A few days ago I created a PR to implement an `itemWrapper` prop for `InnerBlocks` that allows child blocks to each be wrapped with a given element. It’s a rather significant change and there may be better ways of implementing it, so any technical feedback and ideas are much appreciated! https://github.com/WordPress/gutenberg/pull/24232
- I’m working on adding labels to the editor icon buttons (10524 and 15311). I’ve done an initial PR to add an option to show labels, but it only affects the post editor for now. I think we’re going to need this functionality in the site editor too, and am wondering what would be the best way of having a setting that works across both editors. Thoughts welcome!
Patterns and WordPress 5.5
@joyously asked about the pattern, are they part of GB or part of WP? The reason is that the images are stored on .org, and the text goes through .org translations. @youknowriad clarified that Patterns live in Core codebase and the images are hosted in wp.org like the block examples.
Cherry picking from Gutenberg 8.7 for WordPress 5.5
@jeffpaul asked are there 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. fixes and performance improvements that are planned to be cherry-picked from Gutenberg 8.7 to merge into WordPress 5.5? To prepare WordPress 5.5 Field Guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. @youknowriad mentioned that the potential addition fixes might not be worth mentioning.
Documentation “Keeping up with gutenberg” Index
@annezazu shared about a new page in the core handbook called “Keeping up with Gutenberg”. It’s an index of Gutenberg related posts from various Make blogs to make it easier to follow development. Feedback is very welcome to improve it. Props to @bph and @williampatton who led these efforts. @swissspidy raised if there is a way we can somehow automate that list of posts? as currently its manually curated and seems tedious to maintain.
Galleries as composed image block
@andraganescu raised @Zeb added
https://github.com/WordPress/gutenberg/pull/24232 and @noisysocks raised the PR for discussion here as it affects some implementations that count on InnerBlocks including the blocks in navigation feature and the implementation of galleries as composed image blocks
Some discussion around wrapper for the inner block but no decision. Further discussion to continue on the PR for introducing prop to specify the wrapper
Missing post update action
@paaljoachim highlighted the issue of missing “Update post” action when there’s an autosave.
#meeting-notes, #core-editor, #editor, #gutenberg