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, November 03, 2021, 14:00 UTC.
General Updates
Updates on the key projects
Mobile
@mattchowning
Shipped
- Added Media File and Attachment Page options to the native Image 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. Link To menu
Improvements and Fixes
- Added more integration tests for embed blocks
- Added a Fixed Height context to improve inner block handling of fixed heights
In Progress
- Final tweaks to the Embed block so we can stamp this first iteration on that block as complete
- GSS Font size, line height, colors.
Global Styles
@youknowriad
- we’ve been working on the API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoints to prepare things for Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. merge.
- The next steps for us are going to be to work on the Core Patches for both Global Styles and FSE (block themes) infrastructure.
Styling
@jorgefilipecosta
- We also continued the interactions of the design of the styling UI User interface
- For example we just merged a PR that shows multiple color palettes core, theme and user (if a user one exists).
- The new user color palette editor also passed by some iterations and should be ready.
Task Coordination
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.
@oandregal
- During the past week, I’ve been focused on reviews to move 5.9 tasks forward, 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 a couple of bigger things:
- Migrate theme.json v1 to v2. Existing themes with theme.json JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. v1 still work as expected, but we’re preparing things to land in 5.9, which means cutting a new version for theme.json.
- The PR to show colors from different sources uncovered a dormant bug that did not have any effect until now and that we’re fixing here. The fix is to stop retrofitting the filtered settings from the
block_editor_settings into theme.json and instead use the theme supports directly. This may affect plugins that used the block_editor_settings to change theme support values, and they should be updated to use the after_theme_setup filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. instead. - For next week, I plan to keep helping with reviews, bug fixes, and porting code to WordPress core.
@santosguillamot
We have made some progress on the Post Comments blocks. All the info can be found in its tracking issue and its GitHub project. This was the progress made during the last couple of weeks:
Please note that this won’t be included in WordPress 5.9. There is still important functionality missing and it hasn’t been tested properly. For now, we will keep working on the aspects left in the Comment 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. block and start working on the blocks related to the Comments pagination.
@mkaz
@jorgefilipecosta
- I have been involved in review the global style endpoints and made some PR’s that make the UI closer to the mockups
- For the next week the main objective is 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. the global styles/theme.json infrastructure into core
@kjellr
I’m primarily on the default theme, but I’d like to highlight two more global issues I’ve been testing that I think could use more feedback and ideas:
- Post/page editor text bumps up against the screen by default. This seems like a 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., and it effects a large portion of themes.
- Layout settings break content for users who migrate to a block theme.
Open Floor
@overclokk
- Proposal to Remove block-templates and block-templates-parts directories for FSE.
Read complete transcript
#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary
