annezazu 9:18 pm on October 28, 2020
Tags: core-editor, core-editor-summary ( 44 )

Editor chat summary: 28 October, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor SlackSlack 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 2020-10-28 14:00 UTC and was moderated by @annezazu.

Announcements

Gutenberg 9.2.2 was released on October 26th.
WordPress 5.6 Beta 2 was released on October 27th! Please install on a test site, play around, try to break everything, report bugs, and all that good stuff:
WordPress 5.5.2 is coming to your WordPress site on October 29th.

Monthly Plan & Key Project Check-in

For context, here’s the overarching plan for October.

Widgets Screen Update shared by @andraganescu

The focus for the people previously working on this screen is now mostly on 5.6 efforts. However, there still is work around advancing various widgets project related issues. For example, @zieladam‘s PR about fixing concurrency related issues, something which became apparent while working on the widgets editor.

Reminder: the widgetWidget 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. core sync chat is suspended until 5.6 has been released!

Global Styles Update shared by @nosolosw

Global styles has advanced nicely this month with @jorgefilipecosta doing great work related to user-provided color palettes, etc. We’re now going to have a stronger focus on tighten things up to work great with the TwentyTwentyOne blockBlock 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 theme. Some of the items in the first wave of work will also be moved to the “future” iteration at this point.

Full Site Editing Update shared by @vindl

Full Site Editing – Navigation update:

Search feature for the navigation component has been merged. The next step is integrating it with the site editor.
It’s now possible to create new templates from the navigation sidebarSidebar 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. that correspond to default ones from template hierarchy.
We shipped the RTL support for the navigation component.
PR for creating template parts from multiple blocks selection has been merged.
There is a proposed framework PR for introducing a custom status for templates provided by themes (or plugins) as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. files, which haven’t been customized by the user yet.

In other news:

Demo templates have been removed in #26419.
Instead of experiment toggle we are looking to automatically enable FSE for themes that support it.

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. Remember: don’t just focus on code contributions!

@nosolosw

Mainly focused on fixing issues raised in BetaBeta 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. 1 and will continue to help with that, but will also come back at global styles work.

@aaroncampbell

Was trying to verify whether Single Column Functionality, which looks like it made it into 9.2, is going into WP 5.6. As a result, this small screen display issue was put in the 5.6 must-have project board to be triaged.

@annezazu

Wrangled some quicker doc updates: glossary terms to include more block based items, triage instructions to include tables for clarity & reasons for closing, and updated the Versions in WordPress doc for 5.6 (need to do the same for 5.5.2). Outside of that, helped clear out a bit of a backlog for unlabeled items, did some FSE testing/bugbug 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. reporting, and started gathering resources for the contributor working group effort!

@youknowriad

Starting to work on more FSE tasks: trying to streamline the flows to enable/disable FSE themes. Still working on documentation for 5.6 new APIs and dev notesdev 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 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.. Hoping to have time to chime in on this thread soon.

@mkaz

Has been working on improving e2e tests.

Open Floor

Should we bail on e2e tests after a single failure? Raised by @mkaz.

Marcus has been working on trying to improve tests and asked the group for thoughts on whether we should bail on e2e tests after a single failure as it’s not clear if there’s value in doing so. This is particularly the case for GitHubGitHub 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/ Actions to keep running all the tests after an error happens. After a quick discussion with people sharing their differing approaches to handling failures, @youknowriad summed up the root issue nicely: “I feel the issue is not that we run the whole suite on github but more that the tests actually fail…What we should do is actually take the time to fix the failures even if we’re not responsible for them”.

What should be included in the next “What’s Next” in GutenbergGutenberg 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/ post? Raised by @daisyolsen.

@nosolosw made sure to link to the previous update around Global Styles. @youknowriad mentioned both that writing Dev Notes should be mentioned for preparing for 5.6 and that he personally would like to see a greater focus on FSE related work.

Is the current plan to use PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 files instead of static HTML files for FSE? Raised by @johnstonphilip.

@youknowriad once more swooped in to share that there’s an exploration along those lines being done here.

#core-editor #core-editor-summary

annezazu 6:12 pm on October 27, 2020
Tags: core-editor, core-editor-agenda ( 34 )

Editor Chat Agenda: 28 October, 2020

Facilitator and notetaker @annezazu

This is the agenda for the weekly editor chat scheduled for 2020-10-28 14:00 UTC.

This meeting is held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

GutenbergGutenberg 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.2.2
WordPress 5.6 BetaBeta 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. 2
Monthly Plan for October 2020 and key project updates. For the updates, the discussion will focus on what is being done and help that is needed:
- Global Styles & Editor focused APIs
- WidgetWidget 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. Screen
- Full Site Editing
Task Coordination
Open Floor

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor #core-editor-agenda

Jorge Costa 5:29 pm on October 26, 2020
Tags: block-editor ( 22 ), chats ( 15 ), core-editor, core-editor-summary ( 44 ), gutenberg ( 205 ), meeting notes ( 97 )

Editor chat summary: Wednesday, 21 October 2020

This post summarizes the weekly editor chat meeting on Wednesday, 21 October 2020, 14:00 UTC held in Slack.

GutenbergGutenberg 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.2 and WordPress 5.6 BetaBeta 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. 1

@jorgefilipecosta announced Gutenberb 9.2 was released some hours before: https://make.wordpress.org/core/2020/10/21/whats-new-in-gutenberg-21-october/.

Regarding WordPress 5.6 Beta it was released on the previous day as planned: https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/.

Unfortunately the WidgetWidget 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. Blocks were not part of the WordPress release. More context is available at https://core.trac.wordpress.org/ticket/51506#comment:13.

@jorgefilipecosta referred that there is a must-have board that contains the issues that should be addressed before the next WordPress release https://github.com/WordPress/gutenberg/projects/48. Some of these issues are not yet assigned to anyone so it is a good opportunity for someone looking to contribute and have an impact on the next WordPress release.

Monthly plan updates

Full Site Editing – Navigation – @vindl

Pages selector dropdown has been removed in #25620. This functionality is now accessible through the navigation sidebarSidebar 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., similar to templates.
The initial version of Document Settings dropdown in site editor has been completed. It contains basic template info and a button to view all templates.
Work is in progress for adding new functionality to the navigation sidebar, most notably the search feature, template creation flow, and RTL support.
Hover interaction for template parts is on hold after latest round of design feedback and will have to be reworked or abandoned.
Old PR for converting blocks selection to template part has been picked up again and updated.

Full Site Editing – Navigation – @ntsekouras

The Add sticky support in Query blockBlock 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. (https://github.com/WordPress/gutenberg/pull/26279) a needs review.
Query block enhancements(loading and no results messages, focus Query on insertion)

Global Styles – @jorgefilipecosta

Proposed a PR to generate preset classes on the client-side https://github.com/WordPress/gutenberg/pull/26224.
Proposed a PR to use the block settings on the global styles block panel instead of the global ones https://github.com/WordPress/gutenberg/pull/26319.
Merged the pass of dynamic editor settings to the block editor on edit site screen.
Working on improving font size presets to allow other units besides pixels.

Widgets Screen – @zieladam

We are regrouping on #feature-widgets-block-editor to figure out what’s next – anyone interested in this project is welcome to join.
Widgets-related work had some positive effects such as widgets APIAPI 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 or bringing in support for batch requests in WordPress (props especially to @timothybjacobs and @Jonny Harris).

Task coordination

@jasmussen

Submitted the following PR’s:

https://github.com/WordPress/gutenberg/pull/26357 brings a wider vanilla style column.
https://github.com/WordPress/gutenberg/pull/26353 should make the mover arrow positioning more resilient.
https://github.com/WordPress/gutenberg/pull/25218 makes menus as wide as their contents.

@annezazu

Shipped the Block Editor Release Process for Major Releases with major props to our host @jorgefilipecosta and @tellthemachines, reported 13 Widgets Screen related issues to GitHubGitHub 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/, and lots of additional testing including with the latest for FSE.

@ajlende

Woking on a new image-related feature: duotone filterFilter 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. support #26361.
Some of the menu stuff is blocked by #26115 (which @ajlende is currently working on).
Cover block support is blocked by #25171.

@mapk

Query block
- Introducing placeholder screen.
- Creating a new post from block.
- Swap out patterns for block.
Widgets screen
- Going through feedback and helping with design related issues.

@youknowriad

Tried to help a bit with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. package updates and patches for 5.6.
Started working on documentation for the new APIs in 5.6.
Doing some prototyping related to FSE.
Helped a bit with e2e tests (please help there if you have time, we’re not on a great stop at the moment).

@zieladam

Now that we have batch requests endpoint, here’s @zieladam initial effort on supporting them Gutenberg: https://github.com/WordPress/gutenberg/pull/26164
Batch requests opened a pandora’s box of concurrency issues in core data. I lay them out one by one and explore potential solutions here: https://github.com/WordPress/gutenberg/issues/26325

@mcsf

Focused a lot on rethinking our Block Supports implementation, starting with 26111, then discussing details with @youknowriad and @nosolosw in 26192 and follow-up PRs
PR reviews in general

@ntsekouras

Add sticky support in Query block(https://github.com/WordPress/gutenberg/pull/26279) – needs review
Query block enhancements(loading and no results messages, focus Query on insertion)
Recognize and convert old or derivative block types to their canonical form(https://github.com/WordPress/gutenberg/pull/26147)
5.6 bugbug 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

@jorgefilipecosta

Proposed a PR to generate preset classes on the client-side https://github.com/WordPress/gutenberg/pull/26224.
Proposed a PR to use the block settings on the global styles block panel instead of the global ones https://github.com/WordPress/gutenberg/pull/26319.
Merged the pass of dynamic editor settings to the block editor on the edit site screen.
Iterated and merged the video text tracks functionality.
Iterated and merged the columns and group block templateLock control functionality.
Fixed a timezone issue that was considered critical and will be backported for older versions. Did an audit to the way we format dates on the frontend and suggested a general fix (we still have issues currently when we use formats with a complete timestamp like ‘c’ used for time HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. elements)
Did some PR reviews.

For the next week, will see how we can proceed regarding date-time, review the related PRs, etc. Will improve the font size presets (having global styles rely on pixel values for font sizes exclusively is not a good idea). See what can be done regarding identifying if a block instance matches a global style selector (for cases like headings). Will continue the iterations on the PR’s that are open and do some PR reviews.

@vcanales

PR for moving away from momentjs and into date-fns: https://github.com/WordPress/gutenberg/pull/25782 — Needs review, all input appreciated — Most tests passing, and @vcanales is currently testing and trying to fix this issue related to post schedule date mismatch, with the library swapped out.

@frankklein

Got two FSE bug fix PRs open:

Template part generation fix (i.e. do not use text domain): https://github.com/WordPress/gutenberg/pull/26275 already reviewed, and ready for merge.
Fix theme exports (these don’t work at all at the moment) https://github.com/WordPress/gutenberg/pull/26268

@nosolosw

His focus has been lately on various things that were important to land on 5.6. Plans to get back to FSE/GS work this week.

@bph

Testing daily builds of the plugin.zip (for now published on Gutenberg Times).

@karmatosed

Now options iterations are in 5.6, moving to beyond those for next releases. Also shepherding 5.6 and picking up some little pieces along way.

@itsjonq

Continued with G2 Components explorations, with a focus on supporting Design Tools (starting with Typography)
Building in features like CSS validation and smarter unit parsing (e.g. px, or vmax) to expand Gutenberg’s abilities to handle custom values (as Global Styles evolves)
Continued knowledge sharing of all sorts (G2, design, UIUI User interface, dev) via Zoom sessions

Open floor

Updating WordPress trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. editor more frequently

@clorith said:

Continuous Gutenberg releases in trunk.Currently, changes to the Gutenberg pluginPlugin 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 generally get merged to core a few days before beta-1 of a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. going out.
In that time period, months have likely to have passed, and the plugin would have had multiple releases (taking the 5.5 as an example, 9 releases of Gutenberg were bundled, the same rungs true of WP 5.4, 10 releases made it into 5.3). That’s a lot of changes, not all of them obvious, but having all of them land right before beta makes it harder to test their interaction purely in core, and separate between experimental plugin stuff, and what is actually planned for core.I would like to see a continuous integration between the two projects, I’ve outlined a proposed running timeline to get the discussion started around this:- Plugin has a new version releases
– The changes live in the plugin for 3 weeks
– After these 3 weeks the changes are merged to trunk
– Feedback on trunk/core can be provided on the features on how they work without all the other bells and whistles of the plugin.I chose the arbitrary number of 3 weeks, as that gives ample time to get plugin feedback from those using the plugin for testing, while also not keeping changes away from core for “too long”, and also doesn’t lead to excessive extra work for committers tasked with Gutenberg chores (ideally, I’d love a 2 week turnover, as I feel that gives ample time for plugin feedback, but this is what we’re here to discuss 🙂 )

@youknowriad said that our official plan is to actually merge after each release with trunk. The only blockerblocker A bug which is so severe that it blocks a release. is that we don’t have the resources to do so. And added that the part that can be automated is already automated: updating the packages and the e2e tests against core. The rest (PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 changes) can’t be automated.

Multi-line Code blocks regressionregression 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.

@getdave said:

There is a regression in the latest Gutenberg release on the Code block (and possibly also the Classic Block) where formatting is completely broken.
https://github.com/WordPress/gutenberg/issues/26301
It looks like this was introduced by changing from PlainText to the RichText component. All the link breaks are now returned as br tags which causes everything to render on a single line.
My personal website for example now shows all my code snippets in one unformatted long line which isn’t great (at all).
Not sure how complex this is to fix, but should we look to address it as a high(ish) priority?

@jorgefilipecosta said he thinks @ellatrix is already aware of this issue and looking into a solution.

Should we have an issue per PR?

@paaljoachim said:

It seems fairly easy today to create a PR and have someone review and have it merged without even someone from design or accessibilityAccessibility 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) have gone through the PR. The question that comes up… should all PRs have an associated issue?
As it seems an issue will have greater visibility and it is easier I believe for someone to add the correct labels to get it looked at.

@jorgefilipecosta and @youknowriad manifested their thoughts against the idea of forcing an issue per PR.

It seems the biggest issue is having PR’s without labels that don’t get the deserved attention, and we should all make sure our PR’s are properly labelled. In case you have PR’s open please verify if all of them include labels.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting-notes

Isabel Brison 6:20 am on October 21, 2020
Tags: core-editor, editor ( 162 ), gutenberg ( 205 ), gutenberg-new ( 77 )

What’s new in Gutenberg? (21 October)

9.2 was the final release to make it into 5.6 BetaBeta 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.! Featured goodies in this release are:

Support for video subtitles 🎉

Subtitles dropdown on video blockBlock 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.. Props to @jorgefilipecosta for the screenshot.

Ability to transform multiple selected blocks into a Columns block:

Transforming three images into a three-column columns block.

And background patterns in Cover blocks!

Adding background patterns to a Cover block. props to @retrofox for the gif.

9.2 🇭🇺

Features

Add video tracks functionality. (25861)
Transform multiple selected blocks to Columns block. (25829)
Cover: Add repeated background option. (26001)

Enhancements

Add dropdown button to view templates in sidebarSidebar 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.. (26132)
Gallery block: Use image caption as fallback for alt text. (26082)
Table block: Use hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. + APIAPI 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. v2. (26065)
Refactor document actions to handle template part titles. (26043)
Info panel layout improvement. (26017)
Remove non-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks from default editor content. (25844)
Add very basic template information dropdown. (25757)
Rename "Options" modal to "Preferences". (25683)
Add single column functionality to the Columns block. (24065)
Add more writing flow options: Reduced UIUI User interface, theme styles, spotlight. (22494)
Add option to make Post Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. a link. (25714)
Widgets Screen:
- Add legacy widgetWidget 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. inspector card component. (26142)
- Show the legacy widget name in list view. (26138)
- Add unsaved changes warning to widgets screen. (26081)
- Display Widget Area’s name and description in the sidebar. (25943)
- Widgets editor: Add basic options for extensibility. (25758)
- Disallow multiple instances of reference widgets. (26148)
- Embed widget type. (26093)
- Add widget type endpoint. (26042)
- Make edit-widgets package public. (26016)
- Uncollapse widget area when block is dragged over. (25992)
- Add meaningful labels for the Widgets screen ARIA landmarks. (25867)
- Load custom block assets. (25826)
- Test for storing raw htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. in widgets. (24886)

New APIs

Make block supports server-side explicit. (26192)
New hook: UseDebounce for speak function. (25948)
Make the custom spacing theme support flag and block support API stable. (25788)
Mark the line height support flag as stable. (25769)
Mark the font size support flag as stable. (25695)
Mark the color support flag as stable. (25694)
Add a button to allow resetting the ComboboxControl value. (25692)
Block API: Light block edit/save symmetry. (25644)
Block API: Stabilize light block hook. (25642)
Inner blocks: Try hook approach. (25633)
API: Stabilize localAutosave() as autosave( { local: True } ). (20149)

Experiments

Query Block:
- Add Custom Post Types support in Query block. (25903)
- Set focus on Query block on insertion. (26267)
- Add loading message to Query block while fetching results. (26199)
- Add no results placeholder in Query block. (25984)
Site Editor:
- Clear the active menu state when closing the sidebar. (25957)
- Add missing localization to the templates sidebar. (25897)
- Mount both wp_template and wp_template_part EntityProviders to avoid remounting. (25870)
- Navigation templates. (25739)
- Update Navigation Panel Toggle UI. (25622)
- Move page switcher to navigation panel. (25620)
- Add template switcher to navigation panel. (25615)
- Pass editor features dynamically. (25795)

Bug Fixes

Fix for current_parsed_blocks value when block has inner blocks. (26291)
Fix updating clientId mapping. (26290)
Fix typo in wrapper attributes. (26282)
Fix: Keep the ‘Insert from URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org’ entered value on ImagePlaceholder. (26262)
Fix align order in heading block. (26260)
Widgets screen: Add a filterFilter 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. function to registerCoreBlock. (26259)
Use ToolbarButtons instead of Buttons in the Legacy Widget block’s toolbar. (26258)
Widgets screen: Add "Browse all" option to the inserter. (26256)
Fix: Post schedule label showing wrong time if site and user timezones did not match. (26212)
Fix Site Title block’s heading levels appearance. (26202)
Writing flow: Fix in-between inserter for aligned blocks. (26197)
Fix Site Tagline block’s text alignment. (26191)
Fix separator and spacer blocks after api v2 refactoring. (26157)
Global Styles sidebar (blocks tab): Protect against not registered blocks. (26149)
Block templates: Recognize and convert old or derivative block types to their canonical form. (26147)
Fix editing Legacy Widgets doesn’t enable "Save" button. (26144)
Fix Cover width regressionregression 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.. (26143)
Fix tabbing in widgets not triggering auto-scrolling. (26139)
Cover block: Improve overlay opacity handling. (26133)
Fix icons type annotation. (26129)
FullscreenMode: Remove the is-fullscreen-mode CSSCSS Cascading Style Sheets. class from body on unmount. (26103)
Make sure Global Styles CPT includes a theme reference. (26061)
Restrict legacy widget block to only being a child of widget area. (26053)
Fix/wrong classes search block. (26052)
Fix drag and drop in empty widget area. (26051)
Fix unit tests by updating cover block fixtures. (26044)
Upgrade autoprefixer to fix fit-content in firefox. (26019)
Fix widget area title font. (26018)
Widgets screen: Fix WP Adminadmin (and super admin) Bar Widgets screen link. (26015)
Hide parent selector in widget area. (26011)
Document Actions: Fix unexpected label wrapping. (26004)
Fix template part theme identifier. (25995)
Show all widget areas on widget screen. (25977)
Fix block editor example in storybook. (25976)
Fix 9:16 aspect ratio styling. (25972)
Fix gallery caption not centered in the front-end issue. (25962)
Widgets screen: Add save keyboard shortcut. (25944)
Widgets screen: Remove default hover background in panel title. (25939)
Fix failing previews end-to-end test. (25938)
Fix input control drag and box control change. (25933)
Fix end-to-end tests related to template parts. (25923)
Fix insertion indicator margin. (25893)
Fix blue line indicator not showing at the end. (25849)
Fix incorrect attribute type specified in Search block. (25813)
Document Actions: Fix Block Editor Inserter Overlap with Document Titles. (25801)
Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 warning in widget utils REST controller. (25797)
Include edit-widgets php files in build. (25792)
Docs: Fix typo in GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. Workflow. (25779)
Widgets screen: Fix widget-area accessibilityAccessibility 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). (25732)
Widgets screen: Fix insertion point in widget areas. (25727)
Document Settings: Fix document title hover and select animations. (25719)
Define text color for warning message component. (25713)
RichText: Remove native props for web. (25700)
Use h3 in the legacy widget title. (25690)
Navigation block: Use unbounded query when requesting top level pages. (25689)
Document Actions: Fix document title misalignment with an open nav sidebar. (25630)
Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. error in wordpress/block-editor documentation usage example caused by applying args to setState call. (25492)
Cover Block: Show spinner while uploading. (25401)
Button block: Reduce chance of style conflicts. (24919)
Fix skipped shortcodeShortcode 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. transforms in raw handling. (22840)
Media links: Fix linking for images inserted from URL. (22195)
Refactor reusable block edit component using hooks (and fix interactions with multiple instances of the same reusable block). (21427)

Performance

Paragraph: Avoid selector to improve performance. (26150)
Remove transition on block selection indicator. (25974)
Widgets screen: Preload request to /sidebars. (25726)

Documentation

Bring the block-based theme tutorial up to date. (25830)
Add more CI status badges to README. (26090)
Getting started: MAMP: Add tip to fix WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/. (26057)
Update colors readme with additional definitions. (25954)
Document isMultiBlock param for block transforms. (25952)
Update CI status badge in README. (25907)
Adds missing Curly brace. (25748)
Add documentation for colors component. (25567)
InspectorAdvancedControls: Add README.md. (25566)
Add documentation for useResizeCanvas. (25558)
Add/block navigation component readme. (24882)
Update Block Based Themes Documentation. (25710)

Code Quality

Pass all extra attributes down in get_block_wrapper_attributes. (26280)
Editor: Refactor PostFormatPanel to use React hooks. (26273)
BlockListBlock: Reduce passed props. (26251)
Editor: Refactor PostFormat to use React hooks. (26238)
Latest posts: Use hooks + API v2. (26122)
Latest comments: API v2. (26113)
Categories block: Use API v2. (26112)
Rename ReusableBlocksButtons to ReusableBlocksMenuItems. (26099)
Reusable block: Use API v2. (26091)
Gallery block: Use hooks. (26088)
Pullquote block: Use hooks + API v2. (26068)
Components: Start adding types progressively. (26066)
File block: Use hooks + API v2. (26063)
HTML block: Use hooks and API v2. (26055)
Update all blocks to API v2. (26054)
editor: Remove two unused registry controls. (26048)
Tweak styles of the document actions area. (26038)
Site Editor: Navigation panel replace hardcoded menu strings with constants. (26026)
Move left sidebar state to redux. (26003)
Refactor Categories to function component. (25806)
Classic block: Use hooks. (25737)
Remove animation from mover buttons. (25728)
Move widget-area to edit-widgets. (25673)
InnerBlocks: Add select dependencies. (25672)
Refactor Buttons block native edit component to use hooks. (25636)
Data: Build the basic data controls into every store. (25362)
Block Editor: Use optional chaining and nullish coalescing instead of Lodash.get. (23632)
Refactor Latest Comments block to use function component. (23557)
WordCount: Add types. (22077)

Security

PostCSS Plugins Preset: Update vulnerable dependency. (26140)

Breaking Change

Add separate widgets endpoint. (25958)

Various

Stabilize batching endpoint as v1. (26295)
Make batch opt-in more expressive. (26292)
Remove experimental sidebars endpoint shim. (26288)
Warn about using core/batch-processing store. (26287)
Remove WP_REST_Widget_Utils_Controller class. (26274)
Minor iterations to grouping for preferences panel. (26198)
Allow transform to Columns from a single block. (26185)
Use batch processing in edit-widgets package. (26164)
Minor updates to wordpress/edit-widgets for easier Core integration. (26136)
TextareaControl: Use CSS-in-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. (26131)
Add template lock attribute to column and group. (26128)
Reusable blocks support for widgets editor. (26097)
Bump @actions/core from 1.0.0 to 1.2.6. (26087)
First pass at using the new sidebars and widget endpoints. (26086)
Don’t rely on the exact count of registered widgets. (26085)
Try: Make class and style tests less brittle. (26079)
Components: Remove size prop from Dashicon. (26067)
Adjust media-text attributes to default stacked on mobile to true. (26041)
Support batch requests in data layer. (26024)
Fallback for dropcap when experimentalFeatures is not present. (25979)
Social Links: Update Placeholder experience when first inserting Social Links. (25941)
Check that get_current_screen is callable. (25935)
Social Link: Rename mail to email. (25924)
Autocomplete: Use hooks. (25922)
Skip broken template-part end-to-end test until it can be fixed. (25918)
Heading block: Add wide and full width options. (25917)
Social Links: Avoid conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with themes ul text-indent. (25916)
Site editor: Store navigation panel’s active menu state in the store. (25906)
Version bump to 9.1.1. (25904)
Export and document LinkControl’s building blocks. (25901)
Prevent networknetwork (versus site, blog) requests related to ephemeral posts in the widgets editor. (25899)
FSE Navigation Sidebar: Move navigation sidebar in DOM hierarchy. (25884)
Template part selection component – fix keyboard controls. (25881)
FSE Document actions – wrap with heading. (25874)
Extract wordpress/reusable-blocks from wordpress/editor. (25859)
Unify help description text styling. (25852)
BaseControl: Use CSS-in-JS. (25842)
Iterations on options modal. (25837)
BlockSelectionClearer: Use hooks. (25824)
Update pull request documentation URLs. (25815)
Add a dark mode to the post title. (25796)
Automatically generate required preset classes. (25768)
Ensure focus of input when InputControl spinner arrows are pressed. (25753)
External Link: Use CSS-in-JS. (25751)
Update improve backward compatibility for deprecated settings. (25738)
Initialize the state before rendering widgets editor. (25736)
Add color palette edit functionality to global styles. (25711)
UnitControl: Enable keyboard access (via tab) to unit select by default. (25704)
Add EditorStyles CSS to the widgets editor. (25699)
Display before_widget/after_widget when rendering WP_Widget_Block. (25693)
Remove the right margin for the right-most list items in the lastest posts block. (25688)
Update and move some Query filters. (25674)
Remove duplicate key from tsconfig.base.jsonJSON 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.. (25664)
Try adding a ‘spotlight mode’ type effect when template part or child is selected. (25656)
Gallery: Add labels to img, figure and figcaption elements for accessibility. (25560)
Navigation component: Add back button click handler. (25556)
Hide the quick side inserter when the user is typing. (25548)
Add border to block "Edit as HTML" style. (25539)
Show PostFeaturedImage in editor. (25412)
Don’t allow duplicate selectors in styles. (25399)
Gallery: Add a margin declaration. (25291)
Page parent selector with ComboboxControl. (25267)
Add Align support to Separator block. (25147)
REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: Introduce batch controller. (25096)
Upgrade TypeScript to v4. (24892)
Use UnitControl instead of RangeControl for column width. (24711)
Add UI tests to unsupported block editor. (23729)
Add a description to the Site Title block. (23462)
Add storybook story for the FocusableIframe component. (22324)

Performance benchmark

Version	Loading Time	KeyPress Event (typing)
GutenbergGutenberg 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.2	5.1s	31.29ms
Gutenberg 9.1	5.3s	31.03ms

Kudos to all the contributors that helped with the release! 👏

#core-editor, #editor, #gutenberg, #gutenberg-new

Paal Joachim Romdahl 2:21 pm on October 20, 2020
Tags: core-editor, core-editor-agenda ( 34 )

Editor Chat Agenda: 21 October, 2020

Facilitator and notetaker @jorgefilipecosta.

This is the agenda for the weekly editor chat scheduled for 2020-10-2 1 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Gutenberg 9.2 (To be included with WP 5.6)
WordPress 5.6 Beta 1
5.6 Project board
Monthly Plan for October 2020 and key project updates. With focus on issues, what is being done and help that is needed.
- Global Styles.
- Widgets screen.
- CustomizerCustomizer 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. screen.
- Full Site Editing.
Task Coordination
Open Floor

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the discussion:

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor, #core-editor-agenda

Paal Joachim Romdahl 7:46 pm on October 13, 2020
Tags: core-editor, core-editor-agenda ( 34 )

Editor Chat Agenda: 14 October, 2020

Facilitator and notetaker @andraganescu.

This is the agenda for the weekly editor chat scheduled for 2020-10-14 14:00 UTC.

Gutenberg 9.1 (Released 30 September)
5.6 Project board
Monthly Plan for October 2020 and key project updates. With focus on issues, what is being done and help that is needed.
- Global Styles.
- Widgets screen.
- CustomizerCustomizer 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. screen.
- Full Site Editing.
Task Coordination
Open Floor

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the discussion:

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor, #core-editor-agenda

David Smith 8:55 am on October 5, 2020
Tags: core-editor, core-editor-agenda ( 34 ), meeting ( 39 )

Editor Chat Agenda: 7th October, 2020

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2020-10-07 14:00 UTC.

A reminder of the (intentionally) delayed GutenbergGutenberg 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.2 release.
WordPress 5.6 BetaBeta 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. 1 preparation.
Monthly Plan for October 2020 and key project updates:
- Widgets screen.
- Global Styles.
- CustomizerCustomizer 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. screen.
- Full Site Editing.
Task Coordination.
Open Floor.

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor, #core-editor-agenda, #meeting

annezazu 8:33 pm on October 1, 2020
Tags: core ( 282 ), core-editor, gutenberg-next ( 12 ), themereview ( 8 )

What’s next in Gutenberg? (October)

This is a monthly update containing the high-level items that GutenbergGutenberg 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/ contributors are focusing on for October. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development related posts and a new Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps.

5.6 BetaBeta 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. 1 Preparation

With October 20th marking the cut off for WordPress 5.6 Beta 1, there’s going to be a shift in approach this month to focus on what can or cannot be ready for 5.6 since, after the Beta 1, there’s not a way to merge additional features. As part of this preparation, a decision was made by the people working on the Navigation and the editor tech lead for 5.6 to exclude the Navigation Screen from 5.6. Outside of this decision, this focus mainly impacts projects like the Widgets Screen and various editor focused APIs as they will each need to reach a certain threshold in order to be included. Expect there to be lots of effort here to fine tune and make decisions in preparation for an exciting 5.6 release!

Delaying 9.2 Release:

As mentioned in the latest core editor meeting, since Beta 1 for WordPress 5.6 is due on October 20, it’s likely that the next Gutenberg release will be delayed by one week in order to match the dates and include as many features as possible. This means that Oct 19th will likely be the RC for 9.2 and the stable release will be done on Oct 21 since the packages can be incorporated into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. before Beta 1.

Follow along:

Outside of following individual features and their progress, you can follow where things stand on this WordPress 5.6 Must Haves project board.

Global Styles & Editor focused APIs

Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. While great progress was made in September, the editor focused APIs are still in experimental status and a decision will need to be made about what can be included in 5.6. It’s anticipated that the theme.jsonJSON 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. APIs might not be ready for 5.6 but the block.json one might be instead. Outside of decisions around 5.6, some of this work in the month ahead will include the following:

Adding support for themes to control the editor in a global context, and in a per blockBlock 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. context.
Expand the global styles sidebarSidebar 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. with new options and improve its UIUI User interface.
Expand the typography controls and allow users to pick a custom font family and font-weight, and allow themes to configure which font families are available.
Add functionality that allows users to use the global styles sidebar to control the editor’s behavior like which color palette is active.

Follow along:

You can follow the progress for this overall system in this overview issue. For more recent and immediate next steps, you can follow this issue describing the current state of work.

WidgetWidget 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. Screen

With the new Widget screen moved out of experimental status last month in Gutenberg 8.9, lots of work has gone towards addressing the feedback that’s come in as people have begun exploring this new screen. Right now, inclusion in 5.6 depends on the state of the Widget Screen before Beta 1 on October 20th. In an effort to successfully have this feature included in 5.6, efforts that were previously put towards the Navigation Screen are now being redirected here. As a result, expect that this area of work will be a big focus and decision point for the month ahead.

Along with handling any additional feedback that comes in, the following are specific items that will be worked on:

Deciding a path forward for how best to handle customizerCustomizer 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. & the widget screen interaction.
Creating updated designs for an improved user experience.
Exploring how third party widgets can be integrated.
Ensuring only superadmins can store HTML using the new APIAPI 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. endpoint.
Addressing a11yAccessibility 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) feedback around improving the navigation tool.

Join the Widgets Screen weekly meeting:

In light of the decision mentioned above, the previous meeting on the Navigation Screen project will now focus on Widgets. As a reminder, the meeting happens in #core every Wednesday at 7AM UTC. These meetings will be focused on triaging issues in GitHubGitHub 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/ with the [Feature] Widget Screen label and discussing any big structural issues.

Help with testing:

As part of the vision for the Widgets Screen to ease adoption for everyone, modernize the experience outside of just site editing, and upgrade what’s possible by enabling third party extensibility, feedback is still needed to help this become a reality. If you haven’t had a chance to yet, please follow this call for testing and share any bugs or enhancements on GitHub. Thank you to everyone who has given feedback already and helped move this work forward!

Follow along:

You can follow the progress of this work on this project board and by joining the weekly chat in #core every Wednesday at 7AM UTC.

Full Site Editing

As with the prior months, work on this major focus for phase 2 is ongoing and is expected to continue iterating over the coming months. Currently, 5 out of the 6 milestones for site editing are marked as In Progress with overview tracking issues created for each milestone to better plan next steps. With that said, work this month will continue to focus on finishing up Milestone 1 – Site Editing Infrastructure and UI and Milestone 2 – Site Editor Navigation. As in prior months, it’s expected that this work will continue into the months ahead:

Group document settings in the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes..
Move templates and page navigation into the main W sidebar.
Design Explorations for a new sidebar showing template navigation.
Allow browsing all templates and parts.
Incorporate “Add New Page” Flow into “Add Template”.
Implementation is underway to build missing functionality for the query block as part of milestone 5.
Design explorations for Custom Post Type and taxonomies filtering for the Query block as part of milestone 5.
Enhancements to Post blocks (like Post Featured Image) to support more display options.

We’re watching the Theme Experiments repo as well to see how themers are attempting to build block-based themes. Please continue to share there and know we appreciate it!

Follow along:

You can follow the progress of this project on this project board. To help break down this work more, a new overview issue with key milestones for site editing was also created. For each major milestone, there are related issues for each milestone that are recommended to follow if you want a more granular look at each next step (example from Site Editor Navigation).

As a reminder, if you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Areas to be aware of:

Block & PluginPlugin 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 Developers:

There’s a new experimental light box wrapper API that allows for a new way to define blocks in order for the markup in the editor to match the front end. While documentation is planned, it hasn’t been written yet. In the meantime though, you can check out the current PRs as this is now ready to be used by plugins: creating edit/save symmetry and stabilizing the API.

Theme Developers:

@joen did a wonderful show & tell session including in progress work on a Full Site Editing theme.

Additionally, any theme authors experimenting with Full Site Editing should check out the post from @aristath on a New JSON structure for FSE theme.json files.

Ways to Get Involved:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. In particular for this month, focusing efforts around testing the Widgets Screen would be very helpful and high impact.

If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

Core Editor weekly @ 14:00 UTC in #core-editor focused on all things Gutenberg.
Widget Sync weekly @ 07:00 UTC in #core focused on triaging and discussing Widget Screen work.
Block Based Themes meeting twice monthly at Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

#core-editor #gutenberg-next

annezazu 6:54 pm on October 1, 2020
Tags: core-editor, core-editor-summary ( 44 ), gutenberg ( 205 )

Editor chat summary: 30 September, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor SlackSlack 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, September 30, 2020, 08:00 AM MDT and was moderated by @annezazu.

GutenbergGutenberg 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.1

Gutenberg 9.1.0 was released today. Update your sites and stay tuned for a “What’s New” post for the release. As @youknowriad mentioned in slack, “193 commits and 77 contributors for just a single release”. Thanks to everyone who helped!

Monthly Plan

Key Project Check-in

Here’s the overarching plan for September. From there, people involved in the WidgetWidget 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., Global Styles, and Editor focused APIs gave more granular updates:

Widgets screen from @mapk:

Legacy Widget blockBlock 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. UIUI User interface has been updated to reflect 3rd party widgets as block variations.
The UI around widgets inside each widget area has been updated with labels and borders.
3rd party widgets can be found in the Inserter now and added similarly to blocks.

Global Styles & Editor focused APIs from @youknowriad and @jorgefilipecosta:

Improvements made for the APIs for Block Authors (block.jsonJSON 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.) and theme authors (theme.json) to control the editor. Unfortunately, we might not be able to ship all of this on 5.6. theme.json APIs might come later.
Functionalities were merged for Global Styles that allow the editor to be controlled from theme.json infrastructure e.g: colors, font sizes , gradients etc. This also opens the option of settings depending on the block, e.g: different colors for a paragraph and a heading.
There is currently a PR for Global Styles that allows users to edit the color palette using the global styles sidebarSidebar 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.. This is the first time that user control of editor settings is being allowed. This work exposed some limitations currently in place that are being solved with different PR’s.

October Preview

With the month winding down, I gave a preview of the “What’s Next” post for October:

Navigation Screen & Block work is being put on pause in order to focus on the Widget Screen to increase the chances of inclusion in 5.6. There will be a full announcement post about this (why the decision was made, what factors were considered, etc) on Make Core! In the meantime, a call for testing post for the Widget Screen was shared.
Preparation for 5.6 will be a big focus with BetaBeta 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. 1 coming up on October 20th and that acting as a cut off point for features being added. You can see the 5.6 “Must Haves” in this project board.
Work will continue with Global Styles, Editor APIs, and Full Site Editing in a similar cadence as the previous few months.

Delaying 9.2 Release

Finally, @youknowriad mentioned that since Beta 1 for WordPress 5.6 is due on October 20, it’s likely that the next Gutenberg release will be delayed by one week in order to match the dates and include as much features as possible. This would mean Oct 19th will be the RC for 9.2 and the stable release will be on Oct 21 since the packages can be incorporated into Core before Beta 1.

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. Remember: don’t just focus on code contributions!

@karmatosed

Continuing to work on Options settings and helping with the 5.6 release.

@ntsekouras

PR for showing preview of WordPress embed in editor.
PR for showing PostFeaturedImage in editor.
PR to add an option to make Post Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. a link.
PR to update and move some filters in the Query block.

@itsjonq

Continue to working on and exploring various aspects of Design Tools through the G2 Components project. Some aspects include:

Improved coding experience with inline documentation.
Optimizing performance to enable the creation of complex tools (e.g. 10+ box shadow settings).
Exploring drag-based controls (and gesture handling).
Refining existing systems (such as Context, State Management, Styling)
Much of this has been written about on the G2 Components blogblog (versus network, site):
https://g2components.wordpress.com/
Finally, hosting a Zoom tomorrow (at 2PM EST). It’s a casual thing and you’re welcome to join if you’re interested. If you can’t make it, no worries as it will be recorded.

@aristath

Columns can now accept non-percent values for width. This will help FSE themes achieve more layouts .
Focused on global-styles and how FSE themes can leverage them.
Trying to improve FSE performance.
Continuing work on splitting block-styles and only load assets for rendered blocks

@annezazu

Working on finalizing What’s Next for October, nearly have something ready to share for the core editor release process for a major WordPress release (major props to @jorgefilipecosta and @isabel_brison for working on this with me), various triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. efforts, and finally some light testing!

@vindl

Will be reviewing the PRs for exposing templates in site editor’s navigation sidebar as well as some updates to base navigation components: Search Control in Menu Titles & Add Back Button click handler.

@nrqsnchz

Worked on design proposals for Video Block: Subtitles #7673
Made a design proposal for Video Block: alternate sources such as ogv and webm file formats #9457
Started working this week on Allow users to customize keyboard shortcuts #3218

@addiestavlo

Continuing work towards allowing hovered template parts to have their titles shown in the site editor headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.’s document actions component as well as working to enable a spotlight mode type effect when editing template parts.

@jeremyyip

Merged a PR to fix document title misalignment in the topbar of the site editor
Merged a PR to fix a caching issue for apiFetch
Raised a draft PR to polish the select and hover animations for document actions in the topbar of the site editor
Reviewing a PR to display template part label in edit site topbar on hover

@mapk

Query block patterns/layouts.
Query block flows with @mariohamann
Widgets screen reviews and testing

@youknowriad

Working on stabilizing the support flags for (colors, font sizes.)
Iterating on the ComboboxControl component and hoping we can remove all the perPage: -1 api requests
I’ll continue on some of these, I’m hoping to get back to the Custom CSSCSS Cascading Style Sheets. per block PR and block support flags support server side

@David Szabo

Experimenting with the Navigation sidebar. Working on adding templates to the Navigation in this PR which includes whole rework of the navigation and a new feature which allows us to edit templates that only exist as theme files. Other than the PR mentioned above, I’m fixing this and that related to Navigation sidebar and reviewing others’ PRs!

@jorgefilipecosta

Reviewed multiple PRs that were opened.
Continued the conversations on font related PR’s.
Worked on expanding theme.json editor controls.
Worked on user configurable color palettes.
Next week I will continue iterations on the PR’s that are open. I will submit parallel PR’s to address the current limitations the user configurable settings exposed.

Open Floor

Should we create a Twenty Twenty-One GithubGitHub 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/ project board containing issues that can help improve the upcoming new default theme? Raised by @paaljoachim.

After a brief discussion about the current repository for Twenty Twenty One, it was decided not to separate out a project board as there are people working across both core editor and the theme project who can help get any issues handled.

Request to provide feedback/discuss the Gutenberg developer documentation proposal . Raised by @justinahinon.

Justin posted this about a month ago and would like feedback on this before work begins. Thanks to this conversation, a flurry of people shared they would be game to help with different pieces including:

@youknowriad in being a part of discussions around how best to get the “organization” of items right since there are multiple target audiences for the developer docs.
@omarreiss brought the proposal to #core-js for a discussion in a future meeting on October 6th.
@aristath & @mariohamann both mentioned being up for helping from a theme author point of view.

Anyone interested in helping with this work, please feel free to comment on the post directly or pingPing 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.” Justin!

Request for a PR review for DateTimePicker with react-datepicker component. Raised by @retrofox.

For context, as @retrofox mentioned, “we started to look into the implementation just to highlight some events in the calendar, and why not add an events tooltip for every day. It’s tied to when the user wants to schedule a post.” However, after some progress, switching to a reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/.-component dependency was considered for the DatePicker component. The reasons for this switch are detailed in the PR.

At this point, it would be very helpful to get feedback along with any possible issues that haven’t yet been considered in this approach. If you are able to help out here, please do so!

#core-editor-summary, #gutenberg

Riad Benguella 8:54 am on October 1, 2020
Tags: core-editor, editor ( 162 ), gutenberg ( 205 ), gutenberg-new ( 77 )

What’s new in Gutenberg? (30 September)

GutenbergGutenberg 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.1 is out with almost 200 commits and 77 contributors! The main focuses for this release are iterations on the main projects for WordPress 5.6: the Widgets Screen and BlockBlock 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. APIAPI 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..

Important progress has been made on the Global styles project with the possibility to use the theme.jsonJSON 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. config file to control the block editor features and presets (color palette, font sizes, enabling/disabling features).

Also, the release includes some nice little improvements to the UIUI User interface and several blocks. Among these changes, the block patterns are now organized per categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. in the block inserter to help navigate the list of available patterns.