This post summarizes the weekly editor chat meeting on Wednesday, 4 March 2020, 14:00 UTC held in Slack.
WordPress 5.4 Upcoming Release
WordPress 5.4 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 is out, more details can be checked on the release page.
The list of editor PR’s cherry picked can be checked on #20593 and #20613.
The team published all the 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. editor 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, 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.. In total, the team ended up publishing a total of 10 posts with block editor dev notes https://make.wordpress.org/core/2020/03/03/wordpress-5-4-field-guide/ covering 32 PR’s that needed a 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..
@jorgefilipecosta gave a big thank you to everyone that helped the big effort on writting the editor dev notes.
@jorgefilipecosta ended the topic by sharing the following information:
For the next RC currently, we have three issues that should be fixed. Two of the issues have a PR that needs review. Another one does not have a PR yet. The status of these tasks can be checked on https://github.com/WordPress/gutenberg/projects/39
Weekly Priorities
The Post with the priorities for March is published.
@gziolo shared the following summary of the priorities:
- Block Content Areas
- Global Styles
- Block Patterns
- Tightening up
Task Coordination
@karmatosed referred that for Feedback from design just note in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor channel or in 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/.
Is experimenting with new iconography to explore the G2 iterations: https://github.com/WordPress/gutenberg/pull/20464.
- Have put up for review https://github.com/WordPress/gutenberg/pull/20530 that includes a global style sidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. in edit-site, using preferences from user, theme, and core.
- Prepared a raw demo theme for testing purposes at https://github.com/WordPress/theme-experiments/pull/22.
- Next up is expanding the system to other areas (scoped styles, custom fonts & colors, style variations, etc).
- Reorganized the project board for FSE to prioritize “Needs Design” issues.
- Knock out a shortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. PR for this real quick: https://github.com/WordPress/gutenberg/issues/11079
- Started development for the new block editor features 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..
- Code reviews, testing, etc.
Is continuing to work through the components and adding storybook stories to any that are missing: https://github.com/WordPress/gutenberg/issues/17973#issuecomment-591093951
Referred that if anyone has experience with the story shot integration, he has some questions in the Disabled PR: https://github.com/WordPress/gutenberg/pull/20514.
Is experimenting with WebGL blocks right now and working around the constraints. Is trying to get people’s thoughts/opinions on a Gutenberg 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. he has related to rendering in the background and providing a single requestAnimationFrame render 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. for multiple blocks https://github.com/WordPress/gutenberg/issues/20483.
Open floor
Custom text color format
@paaljoachim brought to the discussion the fact that the text color may or may not be a main format.
@jorgefilipecosta clarified that the fact that the text color appears on the main formats when a color is selected and disappears from the main formats if no color is selected is not 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.. It was an implemented behavior to avoid too many main formats but at the same time give relevance to the format if color is chosen. We may discuss this behavior in an issue and it may make sense to change.
Fullscreen mode enabled by default
@paaljoachim raised the fact that now fullscreen mode is enabled by default, and referred he is very skeptical about this change as it can bring much confusion to users.
@gziolo referred that:
- Fullscreen mode is a feature that already existed.
- Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. also uses fullscreen.
- The feature will only affect new users as the current setting the users had is persisted in the local storage.
- The feature is still being discussed and it may end up being reverted during the RC phase.
#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting, #meeting-notes
