Editor chat summary: 14 April, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-04-14 14:00 UTC in Slack. Moderated by @andraganescu.

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/ 10.4 release.

  • @youknowriad shared that the release post will be coming shortly (later today or tomorrow). It’s a release with a lot of work related to FSE, FSE Blocks, editor/frontend parity and many other updates.

Full Site Editing Scope for WP5.8

The post was shared during the chat and attention directed towards the outline of the 5.8 plans for FSE, and @annezazu shared that there is a new call for testing available. Also we now have a board with WordPress 5.8 FSE Must Haves.

Monthly Priorities & Key Project Updates

Global Styles

@nosolosw shared in his 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/ tracking issue:

Landed:

  • Parts of 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. with elements PR:29891
  • preparations to make changes easier PR:30801 PR:30610
  • i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. process: make it not depend on a particular path PR:30604
  • add mechanism to migrate from a v0 schema to the latest PR:30600
  • clean-ups PR:30605 PR:30612
  • border radius for the button 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. PR:30194
  • font size & font family for the button block PR:30394
  • colors for the verse block PR:27736
  • border radius for the search block PR:30227

Ongoing

Mobile team updates

@chipsnyder shared the following updates:

Landed

  • Generic embed block behind the DEV flag, actual functionality in progress
  • Interim dual-license license in place (PR:30383)
  • Error notice improvements (PR:30383)
  • Various fixes 

In Progress:

  • Dual licensing Gutenberg: planning to merge PR with interim license this week
  • Global Style Support (PR:29969)
  • Reusable blocks
  • Search block
  • Adding search to the block inserter
  • Embed block
  • Simplification of media insertion flow
  • Slash inserter (PR:29772)

Block based widgets and navigation editors

@andraganescu shared some updates:

For the Block based 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. Editor the main focus these days is improving the performance of the block editor in the 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. and moving our attention to testing the level of back compat existing and achievable.

Navigation block

@andraganescu, @joen and @mkaz shared updates:

  • Progress continues, responsive menus expected this week
  • One notable merge since last is converting Page List block to menu items
  • Justification controls added to vertical
  • Working through extensibility for allowing additional block types in Social and Navigation blocks
  • preparing for patterns. Notably, looking at submenu colorssmall glitchesremoving menu item padding when there’s no background. The last one should open up a great deal of nice minimalist patterns.
  • ongoing discussion about  the block’s markup and the work on adding a Links List block

Update on the post schedule component

@retrofox shared an update about a couple of enhancements in the post-schedule component. Now, it shows calendar events with a small blue bullet. Events are scheduled and published posts.

Task Coordination

@ntsekouras

  • Landed patterns suggestion for transforming simple selected blocks (no InnerBlocks) (PR:30469)
  • Add active block variation information in Block Parent Selector (PR:30731)

@youknowriad

I’m iterating on the “template mode” of the post editor. (Creating and editing block templates in the post editor)

@joen

In addition to the navigation block, I had these two, one is a work in progress, the other could use your eyes:

@mamaduka

I mainly worked on enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. issues:

@annezazu

Working on all things FSE Outreach Program — responding to feedback for the fourth call for testing/opening lots of issues, held a hallway hangout about FSE, still testing FSE everyday, and am going to ship a fifth call for testing today with a summary post of the fourth call for testing to follow later this week.

Open Floor

Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at Yoast

@poena announced that last week there was a contributor day at Yoast with user testing and code contributions to FSE. A large amount of feedback issues were open and some that are already being solved.

Issues and PRs needing eyes and contributions

  • Discussion: documentation handbook plans for site editing and beyond: Issue:30637
  • FSE: Finalizing the name and menu item placement Issue: 29630
  • Post and site editor title placement: Issue:27093
  • Shared block editor settings PR, which requires some updates to the existing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 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. and could use some eyes for sanity checks and reviews PR: 1118

Status of the existing Block Template 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.

@itsjusteileen asked about the future of the Block Template API in the context of FSE developments and noted that the code examples in the handbook don’t work anymore. It doesn’t appear that the block template API will go away and we should have some issues open if the documentation is outdated or the API broken.

Feedback needed on several widgets/blocks discussions

  • a discussion about allowing users to insert a Classic Block in a 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. on the Widgets (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.) screen
  • a discussion about reconstructing Widgets Screen to use the Customize API. This is a fancy way to say that we should or could remove the standalone editor as the new block based widgets editor lands in a future WP release.
  • a question: assuming the block based widgets editor is an opt out feature what is the preferred way to opt out

Design process for the widgets updates

@Anthony Nolan brought up a question around where can one find the process that led up to the current state in the block based widgets editor project, and was guided towards going through closed issues such as this one or this one, which cover updating the customizer or look at the open project to see how the stand alone widgets editor progresses.

#core-editor, #core-editor-summary, #gutenberg

Editor chat summary: 7 April, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-04-7 14:00 UTC in Slack. Moderated by @annezazu.

Announcements

Monthly Priorities & Key Project Updates

Full Site Editing from @youknowriad

  • Making the margins the same between frontend and backend (no opinionated margins provided by the 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. editor by default).
  • Working on adding a way to use block templates in classic themes as well which should provide a nice transition point.

Global Styles from @nosolosw

Shipped:

  • Block Supports: added a gutenberg_block_has_support helper function and support for padding in dynamic blocks 30322, border for search block #30227.
  • Fixes: title in the save panel of the site editor 30521, fix for themes without 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. support but with experimental link color support 30452.

Ongoing

  • Block supports: border for button block #30194, add border color/style/width properties #30124, spacing #30333 #30371.
  • Theme.json: Update format #29891, there’s now a draft PR at #30541, conversation about whether and how to expand the use of CSSCSS Cascading Style Sheets. Custom Properties #29714

Navigation Block from @mkaz and @andraganescu

Updates and improvements keep chugging along! The dependency on responsive nav will likely get merged today, and then the responsive PR can move forward. A new update attempts to fix the HTML produced by the block. This is blocked by the lack of advancement in the discussions opened by @talldanwp (Issue30007 and Issue30006). Any help moving those points forward would be greatly appreciated! Plenty of other refinements and updates continue too, for example the placeholder state was updated. The best way to follow along is by labels 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/ PRs or this tracking issue.

Navigation Editor from @andraganescu

The Block based Navigation editor is advancing with a host of PRs aimed at polishing various functionality (PR30374PR30403PR30524 PR30340) and some that could use a review and testing (PR30446PR30440PR30349).

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. Editor from @andraganescu

Block based Widget Editor work is focused on tidying up blocks in 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. for better 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) and various bugs.

Mobile Gutenberg from @mattchowning

Landed

  • Block transforms
  • Removing ability to switch to the Classic editor when editing a post
  • Significantly the number of blocks that are tested on native by CI on each PR (relevant PR)

New In Progress

  • Slash inserter

Still In Progress

  • Dual licensing Gutenberg: planning to merge the PR with interim license this week
  • Global Style Support
  • Reusable blocks
  • Search block
  • Adding search to the block inserter
  • Embed block
  • Simplification of media insertion flow

Task Coordination

@mkaz

@ntsekouras

@mamaduka

  • Still working on the “Most used tags” feature.
  • Fixed “the same key” prop issue for gallery list items.
  • Started doing PR reviews by testing and adding comments. Hopefully, this can help the “Gutenberg CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” team a little bit.
  • Currently figuring out the best way to 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. PRs for reviews.

@mikeschroder

  • I’d love feedback on the approach in this PR for 24337, please. If it seems appropriate, I can built it out for the rest of the existing blocks that support the feature, but thinking it’s possible this change should happen higher up somewhere so that blocks don’t have to adjust for it.

@annezazu

  • I’ve mainly focused on the FSE Outreach Program responding to the current call for testing and pausing to get some feedback for how to improve the program.
  • I plan to ship another call for testing shortly after this current one ends alongside a summary post.
  • I want to experiment tomorrow too with holding a friendly, casual zoom call for about 30-45 min to talk through some fun FSE issues/designs/PRs that have caught my attention! Join #fse-outreach-experiment to stay tuned if that’s of interest.

@aristath

  • I’ve been working on ways to make hybrid themes a reality. Among other things, there’s a PR to allow loading a block-based header & footer in classic themes which should help theme-authors to slowly start transitioning parts of their themes to FSE.
  • Other than that, lots of PR reviews.
  • Next week I will probably keep working on the same things: FSE MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia & hybrid-themes.

@joen

  • I’ve been continuing on the Navigation block, polishing and polishing. While it’s in a good place, it’s opening up some grand questions about the next steps, all exciting ones. And I’m excited to delve into patterns for it as soon as I can.

Open Floor

Are there any updates for a home/name for Site Editor Documentation? Raised by @poena.

Carolina brought up a previous post from early February asking whether there was an update around the name and place for documentation as currently it’s causing blockers/confusion for how to proceed. Currently, the documentation in the block editor handbook that’s related to FSE is in several places and pretty difficult to find. At the same time, as interest grows around FSE, people are seeking out more information. For example, one of the concerns that Carolina shared was around how if the documentation is in the theme developer handbook or the block editor handbook, it will be difficult to find and likely not visible enough for when a large number of people are first introduced to FSE. Carolina then passed along a suggestion to have a “front page” with basic explanations of the key concepts that then guides visitors to user or developer docs depending on their interests.

After some back and forth discussion, a loose consensus was reached on the following:

  • The lack of a decision around name and placement shouldn’t stop us from creating docs and organizing them properly when these things get clarified.
  • The go/no go dates should provide clarification this month around what needs to be documented first.
  • An introduction page that can guide people curious about FSE likely needs to be created or at least explored.
  • Exploring renaming the “Block Editor Handbook” to something more general might help alleviate some of these concerns by making the Handbook more flexible to allow for FSE items.

Next steps: @mkaz will kick off a discussion for renaming the handbook and create an issue for an initial intro FSE page to direct people.

#core-editor, #core-editor-summary, #gutenberg

Editor chat summary: 31 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 31, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.7.1

WordPress 5.7.1 maintenance release.
The following release schedule is being proposed:
Release Candidaterelease candidate 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).: Wednesday 7 April, 2021 around 23:00 UTC.
Final release: Wednesday 14 April, 2021 around 23:00 UTC.

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/ 10.3

What’s new in Gutenberg 10.3.

5.8 Pre-planning

5.8 schedule

Monthly Priorities

March monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

Navigation Editor

Update from @grzegorz

Navigation 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.

Update from @mkaz

Mobile

Update from @hypest

Full Site Editing

Update from @annezazu

Task Coordination

@annezazu

  • Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.

@aristath

  • Focus FSE and getting things ready for our MVP for inclusion in core.
  • Past week focused on implementations for hybrid themes, and also adding skip-links to FSE themes.
  • Focus on reviewing PRs.

@ntsekouras

@mamaduka

@poena

  • Reviews.
  • Testing Full Site Editing.
  • Reporting issues and creating pull requests toward the FSE MVP.

Open Floor

Discussing the Full Site Editing MVP.
To summarize the discussion that happened during the meeting and after, here are the top takeways:

  • There is confusion of what MVP for Full Site Editing consists of.
  • As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
  • Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
  • At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.

A link to the full discussion on Slack.

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

Editor chat summary: 10 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 10, 2021, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

WordPress 5.7

WordPress 5.7 was released on the 9th of March.
Contains features such as various updates to the 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. Editor, from HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. to HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in a single click, new Robots 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., lazy-load iFrames and a lot more. A bit shout out to @noisysocks for his work as the technical Block Editor lead.

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/ 10.2

Download the RC version of Gutenberg 10.2.0.

Monthly Priorities

March monthly priorities. Along with Key Project updates. Thanks to @priethor!

Global Styles

Update from @nosolosw

Update from @hypest

  • Global Styles and mobile: Working on identifying tasks.

Block based 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. Editor.

  • Check out the 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 #feature-widgets-block-editor and various Widgets Screen issues on 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/.

Navigation block.

Update from @mkaz

Navigation Editor screen.

Full Site Editing

Update by @youknowriad

  • Still focusing on making sure the experience is as WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. as possible without requiring implicit theme styles.
  • Landing a PR to normalize “figure” element styles.
  • Then another one to reset the WP-Adminadmin (and super admin) styles properly in the editor canvas to avoid CSSCSS Cascading Style Sheets. bleed as much as we can.
  • I’m still iterating on the alignments/widths PR of that work.

Task Coordination

@mkaz

  • Would like to bring focus to this PR. Draft: Pulling JavaScript to the frontend from a Core Block. The PR will require enqueuing JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. on the front-end which has not been done from a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block before. The results of the PR can also help get an accordion block into Gutenberg. Associated merged PR should help enqueing assets.

@sarayourfriend

  • Old project with new focus. To asynchronously load TinyMCE for the freeform block in certain circumstances. Need help in figuring out the particularities of how TinyMCE is integrated into WordPress core. I think it could be a huge performance win if we could offload TinyMCE from the initial page load.

@hypest

  • Landed some fixes (adaptions to newer BlockEdit component is one), and an in-editor banner about deprecating the Classic editor in the apps.
  • In Progress: GSS support, Reusable blocks, removing ability to switch to the Classic editor, editor switch, dual-licensing Gutenberg, progress on Search block, progress adding search to the block inserter, progress on the embed block.
  • Blockers: We’re experiencing flakiness in the native mobile E2E tests, affecting many PRs and we’ll continue to work on fixing it.

@joen

@annezazu

  • Launched the next FSE call for testing and have been doing a fair bit of amplification.
  • Lots of feedback wrangling, issue testing, etc for the second call for testing with a draft in place for a summarized post.
  • Working on the next Core Editor Improvement post on the performance of the core editor itself.
  • Continued work on a “role of 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” post to clear up some confusion (TBD on when that’ll launch).

@ntsekouras

@aristath

@retrofox

@mamaduka

@mikeschroder

@poena

@nosolosw

  • I’ve been helping with reviews, bugfixing, and getting inner blocks working on the quote block. My focus for next week is going to be quote plus tackling some tasks for global styles.

Open Floor

Announcement

@mikeschroder
Gutenberg contributions are being prioritized by GoDaddy, so I’m spending time learning, and will be around the repo a bit more often. As part of that prioritization, I’m excited to welcome @mamaduka, who is joining the team full time for contribution to Gutenberg!

@annezazu
The third call for testing for the FSE Outreach Program that was launched yesterday! It’s centered around creating a custom (and fun) 404 page. Please help test or share the call for testing if you can’t — all of it helps. As always, join #fse-outreach-experiment if you want to stay tuned for more updates.

@priethor
I would like to raise awareness of the ongoing discussion on dropping support for IE11, and invite anybody that hasn’t already to give their feedback on the subject by March 18th.

An issue, PR and release.

@manooweb
Emmanuel wanted to bring attention to the PR: Add preload_paths filter for widgets screen and full site editing.
As well as this issue: Widget-id value used to build form field ids isn’t consistent with hidden widget-id field.

He was also wondering about releases and @annezazu shared https://make.wordpress.org/core/2021/02/11/making-wordpress-releases-easier/
Update: Let’s move forward with the March release, a July release (to give folks time to adjust their company plans), and a final release in December. I will create a plan to help us lessen the burden of releases, and in December I will see what we’ve accomplished and get some 2022/23 target release months published.

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

Editor chat summary: 24 February 2021

This post summarizes the latest weekly Editor meeting (agendaslack transcript), held in the #core-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, 24 February 2021, 14:00 UTC.

Announcements

  • WordPress 5.6.2: a maintenance release with 5 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.
  • WordPress 5.7 RC: we’re officially in 5.7 RC period which means 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. will be published this week. Check out @noisysocks message here for more information about how you can help with some regressions. 
  • Gutenberg 10.02: released yesterday to fix some bugs including a white screen on RTL languages.
  • Gutenberg 10.1 RC: released just before this meeting began!

As a reminder, 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/ 10.1 RC is being released this week to allow for a 1 week RC period before the stable release next week. Please test and report any problems. 

Outside of the above, there are a few FSE Outreach Program updates to keep in mind: 

  • Answers to Full Site Editing related questions have been shared across 5 posts found here. Check them out and expect future calls for questions! Big thank you to everyone who submitted questions, helped review answers, etc.
  • Help with the latest call for testing by building a simple homepage with a 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. using site editing blocks. If you can’t test, it helps to also share the post with others if you’re open to it.

Monthly Priorities & Key Projects updates

With the Monthly Priorities detailed in this post in mind, key project updates were given:

Global Styles Update from @nosolosw

The main activity for the global styles focus has been around this effort to improve the block supports mechanism. A few things landed, but it still needs more work to be complete. 

Navigation 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. Update from @mkaz

Making steady progress on improvements, bringing justification tools to sub-blocks, fix for CPT links, setup state, and a set of small tweaks. The biggest next up piece is menu overflow on mobile.

Full Site Editing Update from @youknowriad

All the big pieces needed for an MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia are already there and we need to iterate and improve the experience now. Riad has started exploring alignments/Group block and how themes should (or shouldn’t) define these alignments as a way to drastically improve the experience. For example, the wide/full flags we have for the post content editor are optimized for the post content and for backward compatibility but these notions don’t translate properly to a fully editable theme. Expect work to be done here!

Block Based 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. Update

The latest update for the Widgets Editor can be found here. The immediate priority is still to allow blocks to be added and edited in the 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..

Task Coordination

@itsjonq

  • Updates on the new Component System project can be found here.
  • @sarayourfriend and I are continuing the integration into Gutenberg and are now ~20% of the way through.
  • Work continues on the UIUI User interface components along with ensuring the code/workflow feels right within the Gutenberg code base.
  • Have reached the stage where we’re looking to bring over the foundational systems over with the latest status here.

@mattchowning

Current work on Gutenberg for the mobile apps includes:

  • Reusable, embed, and search block
  • Finishing up Single-Page Starter Templates
  • Planning for global style support
  • Preparing to no longer allow users to switch to the Classic editor
  • Adding search to the block inserter
  • Dual-licensing Gutenberg

@annezazu

@paaljoachim

  • Triaging issues with the label “bug” and “needs design feedback” + made tracking issues.
  • Working on Learn Workshop for setup dev env site for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Looking into creating a new UI for the inline images and welcome thoughts.
  • Worked on issues included in WP 5.6.2.

@aristath

  • Block-styles loading improvements were merged this week, so now I’ll be focusing on ideas to allow for “hybrid” themes and allowing users to combine user-created templates with traditional themes. This will allow FSE to work on a per-template basis instead of a per-theme basis.
  • Lots of PR reviews to keep things moving.

@nosolow

  • Focused on the block supports mechanism.
  • Helped with some reviews, including help support TypeScript in the codebase or preparing dev notes for block supports.
  • Created a script that pulls data out of 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. ― if anyone is interested to take that and use it to improve our docs, they’ll be very welcome.
  • For next week: continue with block supports + unblocking quote block with inner blocks. 

@bernhard-reiter

  • Big thank you to contributors who helped with a few PRs after my hallway hangout on e2e tests last week
  • I’d like to continue to increase our test coverage to make sure we don’t make the same mistake twice.
  • It’s greatly appreciated if people file issues to request those when they spot a 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. (Use the [Package] E2E Tests label.)

@ntsekouras

Two open items that need help:

Open Floor

Is there a plan to support reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. router for navigation between adminadmin (and super admin) menu pages in the future? Raised by Mohamed Magdy.

After confirming this was asking about wp-admin, Riad and Miguel chimed in to say that this something JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.-based isn’t in any Core WP plans right now and that it’s unlikely that will change. Riad mentioned that it might possibly happen iteratively in time but it isn’t currently an outright goal.

Is there anything you would like to include in March’s “What’s Next in Gutenberg” Post? Raised by @priethor.

@priethor is working on this post and asked for people to share any items they’d like to have included. Otherwise, a few contributors shared what they are planning to focus on in the month ahead:

Next Step: @priether will take the above and start writing the post.

Discussion around dropping IE11 support. Raised by @annezazu.

Here are some relevant links & previous discussions for context:

The discussion was mainly in favor with a few warnings and words of wisdom. @youknowriad shared that last time support was dropped for older IE versions, it was around the same level of usage. @desrosjd noted that he’d love to see what exists in WP Core that is IE 11 specific, as this adjustment needs to be made in trunk as well and requires manually adjustments. @mkaz shared that there is an unknown question about screen readers and IE11, that we should get a solid answer to. Ultimately, we all agreed this makes for an ideal proposal on Make Core to discuss a policy before proceeding with specifics around implementation.

Next Step: @mkaz @annezazu @priethor will work on a proposal post focused on setting a policy before figuring out implementation with reviews from @youknowriad and @desrosj. If you’d like to help review this, just DM me (@annezazu on WP.org slack).

Who can help rename the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". to trunk? Raised by @sarayourfriend.

Many months ago it was decided in this Make post to rename the main branch of git repositories to trunk. Sara opened an issue a while ago to plan this in Gutenberg but needs someone with both time and the right permissions to help out. Of note, this PR would need to be merged immediately after to fix CI issues and clean up the rest of the language in the repository.

There was some conversation about whether this could cause confusion or any unintended problems but it became clear that 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/ has made this quite seamless. Thankfully, as @mkaz pointed out, the PRs will automatically get updates, so it is more retraining yourself to git switch trunk or git rebase trunk.

Next Step: @youknowriad and @sarayourfriend are going to team up to take care of this on March 1st with planning details in this thread.

What’s the expected functionality for reusable blocks? Raised by @danstramer.

Dan re-flagged a prior question about reusable blocks trying to better understand what the expected functionality is. Specifically, he wanted to know where it was expected to be able to edit reusable blocks directly. This led to a conversation about improvements being shipped in 5.7 that should resolve these concerns!

#core-editor, #core-editor-summary

Editor chat summary: Wednesday, 17 February 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-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, February 17, 2021, 14:00 UTC.

Thank you to all of the contributors who tested the 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

WordPress 5.7 Beta 3

WordPress 5.7 Beta 3 is now available for testing!

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/ 10.0

Gutenberg 10.0 which means it’s the 100th release of 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, the 100th release of a journey that started more than 4 years ago when Matt announced the project on WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US 2016.

Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles.
  • 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 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. Editor.
  • Navigation block.
  • Full Site Editing

For detailed plan check out monthly priorities post.

Updates on the key projects

@hypest

  • Global Styles side: working on scoping things out for native mobile for Colors Support.
  • Gallery Block: What changes we need to introduce to the Gallery block support on native mobile.

@nosolosw

@youknowriad

@vindl

Full Site Editing – Infrastructure and UI milestone update:

  • Foundational PR for semantic template parts has been merged. It registers wp_template_part_area taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. that allows us to assign categories to template parts. Currently, defined ones are 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., footer, 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., and uncategorized.
  • Display of template parts has been grouped in the browsing sidebar.
  • Browsing sidebar now supports searching of content menus too.
  • The template tab has been added to Site Editor’s sidebar.
  • Block patterns can now be inserted at the non-root level. This allows the insertion of patterns into template parts among other things.
  • The persistent block navigator is getting close to being merged, awaiting for 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 for it.

@Grzegorz

A brief update from the Navigation block:

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.

@ajlende

  • A couple of PRs that I’ve been working on for a while now is finally ready for review!
  • Adding duotone filters to blocks, duotone is a lot like converting an image to black and white, but instead of just black and white, you can choose any two colors that you’d like (which makes it a lot more powerful than just a color or gradient overlay on top of the image).
  • Adding duotone filters to the image block. This one is probably best to review first as it’s more straightforward and doesn’t have any additional dependencies.
  • Adding duotone filters as a block supports the feature to make it easy for block authors to add duotone to their blocks. It shares a few of the commits from the image block PR, but was moved to a separate PR as it depends on some PHP changes in core for adding a render hook to WP_Block_Supports.
  • The video, media & text, and cover blocks have duotone support added via block supports in that PR.

@aristath

@hypest

Quick update from the native mobile folks:

  • We now have support for setting Cover block focal point 
  • Working on Reusable blocks, removal of the manual Classic editor switch, dual-licensing Gutenberg, the Search block, and Block transforms.

@youknowriad

  • Mostly focused on Reviews and Discussions.
  • Things like Gallery block refactor, Hybrid themes, and more flexible block supports are on the card.
  • Some small PRs in parallels like improving the creation flow for reusable blocks and template parts

@paaljoachim

  • Focus on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..
  • Helping to test 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 for WP 5.6.2.
  • Testing and improving docs for setup dev env + testing for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@annezazu

  • Lots of FSE Outreach wrangling mainly focused on answering the wonderful 47 questions that came in.
  • Getting the next call for testing in place.
  • Discussing an approach to docs, and doing various testing/bug reporting.
  • Shipped an update to the Outreach page

@mcsf

  • following and discussing topics related to Global Styles and FSE

@itsjonq

  • Continuing work on adding/integrating the new components into Gutenberg (via WordPress/Components).
  • Work is lead by @sarayourfriend @gziolo, and me (additional help is welcome! Let us know if you’re interested)The immediate checklist we’re working through can be found in this 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/ issue.
  • For a simpler overview of the status, you can check out the status page
  • We’re almost 17% integrated! It’s still early, but it’s ramped up a ton from the earlier days where it was stuck around 3% for initial integration details.
  • Currently drafting up a post on this Components System project for make. I hope to publish it soon.

Open Floor

@paaljoachim

  • Asked about the list of various people and areas that are more focused on. The list will help to know whom to 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.” while triaging. Some discussion around crafting list but no decision.
  • Aiming to conduct triage on Tuesday and hope that a few devs will also attend.
  • @mcsf suggested using intuition and experience to know who to ping instead of a scripted list.

Read complete transcript

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

Editor chat summary: 3 February, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, February 3, 2021, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

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.9.0 RC release

Gutenberg 9.9.0 RC is included as part of WordPress 5.7
There are several bugs and regressions in the 5.7 project board which need assignees.
Please label any 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.-fix PRs that need to be cherry-picked into WordPress 5.7 with the Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. to WP 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./RC label.
Please 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.” @noisysocks if you spot a Gutenberg bug or 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. that needs to be included in WordPress 5.7 and it will be added to the project board.

WordPress 5.7 Beta

WordPress Beta 1 was released 2 February. Work has been done on updating npm packages
in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to contain all of the functionality that is in Gutenberg 9.9.

Monthly Priorities

February monthly priorities. Along with Key Project updates.

Global Styles

Update from @nosolosw

  • Gutenberg 9.9 will come with a new 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. format (see docs).
  • TT1-blocks theme has been updated to follow this new format but hasn’t been published to the theme repo yet.
  • We’ve been working towards shipping parts of theme.json to 5.7 so themes could control the editor in a more fine-grained way. While there was a lot of progress, it proved premature given two outstanding issues that are unresolved in the format: how to express different templates/nested contexts & support the new direction for sidebars (controls that are shown/hidden) Addressing these issues would be our next focus.
  • There’s a longer and more detailed update in the overview issue.

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 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. Editor.

Update from @noisysocks

  • Saving widgets bugs in GB28379 and GB28210 has been merged. We have plenty of E2E tests now to prevent that from happening again.
  • Next priority is getting blocks in Customize → Widgets working. Work happening in GB28618.

Navigation block.

Update from @isabel_brison

On the Navigation block front, Pages list block PR is ready for final review. I have a couple of related thoughts I’d like to discuss:

  • How to best to render dynamic blocks in the editor (comments welcome on the issue!)
  • Should block markup change depending on its context? E.g. if it’s rendered inside a certain block?

Navigation Editor screen.

Full Site Editing

Update by @ntsekouras

Task Cordination

@aristath

@annezazu

  • Work on FSE Outreach Program, hoping to complete a “how to use 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/” Learn WordPress course this week.
  • Shipped the What’s next in Gutenberg post, shared a quick update to the Versions in WordPress doc for 5.6.1 & 5.7.
  • Did some triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

@ntsekouras

@joen

@mattchowning

  • Mobile team merged the audio block work. 
  • Work on porting the search block to mobile.
  • We are investigating a share extension on iOSiOS The operating system used on iPhones and iPads..
  • Working to default more users to the Gutenberg editor in the mobile apps.

@paaljoachim

  • Triaging. Testing patches on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and design triage. 
  • @gwwar Kerry and I held a triage session in the core-editor 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.
  • Working documentation for setting up a local WP dev environment + testing for Core.
  • Plan to create a Workshop on Learn.

@brentswisher

I’m just coming back after a hiatus for most of last year due to moving and an addition to the family, focusing on 5.7 bugs as I get up to speed on all the new things like FSE.

  • Look into remaining bug issues with the cover block.
  • Planning to add some more unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. to the Focal Point Picker to make it less prone to breaking.

@nosolosw

@bernhard-reiter

  • Working on a visual regression test, part of a wider effort to guard essential pieces against regressions e.g. when refactoring.

Open Floor

@annezazu

Announcement
Submit your FSE related questions by Feb 15th! For the full run down of how I’ll approach gathering answers and where you can submit your questions. For a direct link to submit questions via a form (questions welcomed as comments on the post too).
For context, this is part of the #fse-outreach-experiment effort.

I’d like to update this outreach page as it’s a few years old now and would love to crowdsource links to include.  

@backups

Please fix this bug in wp 5.7 editor. WordPress asking for me to save the page on exit without making any changes.
Comment by @paaljoachim I have followed up and added additional info to the trac ticketticket Created for both bug reports and feature development on the bug tracker.. – Ticket is fixed.

@gwwar

Would it be possible to confirm if we’d like a Playlist block in the core block library? If not what might next steps look like?
This issue was brought up as part of a core-editor triage. The issue is low priority. If anyone wants to work on it they are welcome to do so. Comment by @paaljoachim I have added a tutorial to the issue on how to create a Playlist using the Classic block.

@ashiquzzaman

We ended the Core Editor meeting with the final question…
Question for @paaljoachim what do you think editor will look act like once FSE is done working. I’m asking as a theme developer. Sometimes, I really find it hard to visualize the final version of the editor.
Reply from @paaljoachim I have been looking at FSE for a while now. A new user would expect to change everything they see on the screen. Which means we need to make it clear which section one is working in.

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

Editor chat summary: 27th January 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-01-27 14:00 UTC in Slack. Moderated by @andraganescu

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/ 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 Release

  • Gutenberg 9.9 RC has been delayed for January 29th 2021, to sync with the upcoming 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 release of WordPress

WordPress 5.7 Beta 1

  • WordPress 5.7 Beta 1 is due for release on the 2nd February 2021.
  • Beta 1 will represent the cut-off point for new commits/features for the 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. Editor.
  • The deadline for changes is Gutenberg 9.9 RC on the 29th January.
  • There is a WordPress 5.7 project board where you can follow along and keep up to date with progress.
  • WordPress 5.7 will include versions 9.3 to 9.9 of Gutenberg

Monthly Plan & Key Project updates

  • We requested updates on the key projects.

Full Site Editing

Global Styles

  • not many updates but issue 27506 is a good starting point to gauge GS status 

Block based 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. / Navigation Editor

@andraganescu provided an update for the widgets editor:

@mkaz added an update on the ongoing additions to the Navigation block:

  • The Navigation Block tracking issue is here, though we are also working on issues raised for items needed to help develop themes. So that list my get supplemented with a few additional issues. (edited) 

@grzim added an update about the navigation editor:

  • The work on menu name edit is back on track Issue 24581 . There is an ongoing discussion in #feature-navigation-block-editor about moving name edition to a side panel.
  • UXUX User experience and 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) issues have been fixed Issue 28183 , Issue 24369
  • Also inconsistencies in e2e tests are being fixed.

Task Coordination

@hypest provided a

short update about what the native mobile folks have been up to:

  • Reusable blocks rendered in-editor (only available in DEV builds for now)
  • Audio block close to merge
  • Fix for blocks auto-scroll when the keyboard appears
  • Fixes for issues resulting from some GB-web side changes
  • Fix for File block’s automated test.

@bernie will continue to work on some release tooling automation soon. Afterwards, there are two things on the automated testing front that I’d like to work on:

  • Run e2e tests in FF (draft PR).
  • Visual diffs (to avoid block regressions) (issue)
  • Anyone interested in helping with those? Experience with puppeteer would be especially helpful for the e2e tests!

@annezazu is working on the “What’s Next” post for February and the FSE program. For the FSE program, I’m trying to find creative ways for more people to help through sharing various roles for the program (helping write calls for testing, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. feedback, etc), updating documentation with more information about the process I’m loosely following/creating, and sharing an idea around how we can include polyglot communities! I wasn’t here to announce the how to triage in GitHub course is live on LearnWP too! Working on another course this week/next week for more 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/ basics 

@paaljoachim is Working on consolidating setup local dev environment + testing instructions for Gutenberg and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Triaging Design and Gutenberg issues.
Working on a Dev site for support structure. Experimenting with the design for Learn and more. 

@mcsh updates:

  • Fixed a fatal infinite recursion issue in Reusable Blocks (@gziolo now fixing the same in Template Parts)
  • Code reviews
  • Too many conversations to name, but recently: with @ella about Footnotes, with @ntsekouras about focus bugs and other issues related to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. refs, @gziolo about how we do e2e testing, table of contents block, etc.

@andraganescu did mostly code review and testing on widgets and navigation editors

@joen has been working on a bunch of small navigation block user experience related things:

  • Menu item word wrap
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org cutoff
  • Menu item overflow menu polish
  • Button block appender
  • Space between

@itsjonq is Continuing his efforts to work on integrating the new Component System into Gutenberg (working on it directly as well as coordination). He is also tinkering with new UIUI User interface tools for Gutenberg in parallel, focusing specifically on background/color tools at the moment.

@ntsekouras updates:

  • Lot’s of triaging and GH reviews with some fixes
  • `Preferences` modal is probably ready to merge (PR /28329) – thanks @joen for the styling polish there

Open Floor

Will there be Global Styles also in the Post Editor? Or is that only to be for the Site Editor?

The general consensus on @paaljoachim‘s question was that the post is a place which lacks enough visibility for the impact the changes would have so most likely the answer now is no.

What’s Next post for February

@annezazu brought up the next focuses:

  • Preparing for 5.7
  • Global Styles
  • FSE
  • Block-based Widget Editor

Global styles in WordPress 5.7

@mcsf mentioned that whatever pieces of GS that may land in 5.7, they will concern 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. structure and won’t impact users. At best, there will be experimental APIs that devs may use in Core, following in the footsteps of the well-known add_theme_supports extensions

AMA session about FSE and a dedicated FSE feature channel

@annezazu proposed to great enthusiasm an AMA session about FSE and also the creation of a dedicated feature channel for FSE.

A plan to standardize the use of feature channels

@priethor suggested a plan to standardize the use of feature channels:

  • Gather feedback on the overall feeling about these channels, whether folks think this segmentation improves communication or makes it more difficult.
  • If feature channels are agreed to be an improvement, create feature-specific channels for other feature projects such as FSE.
  • List these channels on the Feature Projects Overview page and promote them in automated welcome messages, as suggested by @annezazu.

@francina mentioned that “having multiple channels dilutes the attention of contributors, issues are not developed in a silo and are interdependent, so I am not sure having a myriad of channels is really helping, but willing to try”.

Internal Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at Yoast on February 5th

Also @francina mentioned:

We are doing an internal Contributor Day at Yoast on February 5th. Let me know if there are some PRs that need developers and/or users testing

This is a great opportunity to bubble up things in need of testing or extra development hands!

Input wanted on the editing of a menu’s name in the navigation editor

Lastly @grzim called attention on PR 25343 where editing a menu’s name is added to the navigation editor, for sharing opinions on the approach taken there to make it as user-friendly as possible.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting-notes, #summary

Editor chat summary: 20th January 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-01-20 14:00 UTC in Slack. Moderated by @get_dave.

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/ 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 Release

  • At the time of the meeting the latest release was 9.7.4.
  • The release was underway for 9.8.0 during the meeting.
  • @bernie provided us with an update:
    • Not a lot of “big” new features.
    • …but some nice enhancements.
    • Semi-transparent Spacer 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..
    • Block Switcher now shows variation icon.
    • Major changes to the Full-Site Editing framework (see full updates below).

Preparation for WordPress 5.7 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

  • WordPress 5.7 Beta 1 is due for release on the 2nd February 2021.
  • Beta 1 will represent the cut-off point for new commits/features for the Block Editor.
  • The deadline for changes is Gutenberg 9.9 RC on the 27th January.
  • There is a WordPress 5.7 project board where you can follow along and keep up to date with progress.

Monthly Plan & Key Project updates

Full Site Editing

Global Styles

@nosolosw provided an update via the agenda post:

@itsjonq also provided an updated on Global Styles UI:

  • Working through the integrations and improvements to the Component System for Gutenberg.
  • Came up with some design/interaction ideas for 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. experience. I’ve documented them as a comment in this Github issue.

Block based 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. / Navigation Editor

@andraganescu provided the update:

Task Coordination

Open Floor

New Slack channel for block based Navigation screen

  • @danr mentioned in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dev chat that work on the block-based Navigation screen has picked up again.
  • There’s a new channel for anyone interested in following/contributing – #feature-navigation-block-editor.
  • There’s a Github project for it too.

More native mobile integration/e2e tests on Gutenberg’s PR CI

  • @hypest asked about adding more more native mobile integration/e2e tests on Gutenberg’s PR CI.
  • Some regressions recently that would have been caught with some simple automated tests before their PRs got merged.
  • Adding tests will increase the run time of the CI jobs, not much but, you know, it adds up.
  • @youknowriad recommended defaulting to adding the tests and figuring out speed improvements if needed.
  • @gziolo suggested a more detailed mobile test suite executed after every commit to the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

Stale Issues/PR bot in Github repo

  • @mkaz followed up on last week’s stale issue topic.
  • Posted on Make and already received great feedback and comments there.
  • We plan to leave open until end of month and then will create a PR with next steps.
  • So if you have any thoughts not already captured, please comment on the post.

Custom Post types and Full Site Editing

  • @ndiego noted how he started diving into custom post types in the FSE and custom templates, but hit a lot of deadends.
  • Is this something else one is actively working on, or still well down the road in terms of FSE development?
  • @youknowriad said he did work a bit on custom templates recently (page templates) but not much custom post types. I’m sure there’s a few things we need to figure out there though.
  • Agreed to open Issues or PRs as required.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting-notes, #summary

Editor chat summary: Wednesday, 13 January 2021

This post summarizes the latest weekly Editor meeting (agendaslack transcript), 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, 13 January 2021, 14:00 UTC.

WordPress 5.7

WordPress 5.7 is now underway 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 due on 2 February 2021. You can help with this effort by jumping in on the following issues shared by @noisysocks:

https://github.com/WordPress/gutenberg/issues/24965
https://github.com/WordPress/gutenberg/issues/14744
https://github.com/WordPress/gutenberg/issues/24092
https://github.com/WordPress/gutenberg/issues/25983
https://github.com/WordPress/gutenberg/issues/23636

Finally, you can follow this Project board that tracks WordPress 5.7 “must-haves”. Please add issues to this board and/or reach out to (@noisysocks) if there is something you think needs to be included.

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.7 & 9.7.1

Gutenberg 9.7 & 9.7.1 were released over the last week. Highlights include drag & drop from the inserter for block patterns, updates to the reusable 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., and more.

Gutenberg 9.8 RC

As a reminder, Gutenberg 9.8 RC will be released this week to allow for a 1 week RC period before the stable release next week. Please use this as a chance to test the RC!

Monthly Plan & Key Project Updates

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles
  • Block-based 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. Editor
  • Full Site Editing

For detailed plan check out monthly priorities post.

Full Site Editing Update from @ntsekouras

Testing/feedback/review on Query Pagination block with InnerBlocks
and feedback for possible use cases of a Query Title block would be fantastic. Any thoughts and help are really appreciated!

Global Styles Update from @jorgefilipecosta

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. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. mechanism was merged! There is a proposal for a save time theme.json escaping mechanism. The progress to integrate the font size picker new version advanced nicely and the PR should be merged soon.

Widgets & Navigation Update from @andraganescu

They are both back working in the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". after some foundational changes broke them.

Native Mobile Block Editor Update from @hypest

  • We added the ability to move blocks to top/bottom via long-pressing the block mover icons
  • Removed the info popup on start about the block editor being the new default as it’s been quite some time now that Gutenberg rolled out
  • Added block insertion E2E tests
  • Made progress on porting the Audio block

Work will continue on the audio block, the code block and prepare to work on the table block.

Help test full site editing

Today is the final day to respond to the very first call for testing for the FSE outreach program. Feedback is of course always welcomed and appreciated 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/. Expect a post this week on Make Test summarizing the results of this first test and join #fse-outreach-experiment if you’d like to help with future calls for testing. Thank you to all who have already helped test!

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.

@ajlende

  • This PR has now been merged: WordPress/gutenberg#25171 adds srcset for cover images. Looks like there’s a few people who would appreciate it for performance reasons and it’s needed in order to add duotone to the cover block. The primary question in the PR is if it’s worth adding the polyfill for IE.
  • Would love a review for this PR: WordPress/gutenberg#27936 has some light refactoring of the custom gradient picker which also adds some inline documentation and simplifies the code for readability. It also allows me to reuse it for the duotone picker

@joen

@youknowriad

  • Landed the removal of the auto-drafts in Full Site Editing, an important low-level work.
  • Fixed a number of small bugs and tweaks here and there
  • A number of reviews and discussions.
  • Going forward, would like to focus a bit more on FSE, maybe the template mode in the post editor in the next days.

@ntsekouras

  • PR for Query Pagination with InnerBlocks.
  • Display matching variation icon in Block Switcher.
  • Various small 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 and reviews.

@itsjonq

  • Continue the efforts of updating our Component Systems, starting with the FontSizeControl integration.
  • Working through final details/adjustments to make sure things conventions are compatible with Gutenberg.

@annezazu

@paaljoachim

  • Triaging older issues from 2018 and 2019. As well as triaging needs design feedback issues.
  • Docs: Working on (again) improving the Local WP Development Environment setup.
  • Taking part in Learn/Training team meetings to see where Gutenberg can improve to help make things easier there.
  • Docs: Working on Improving the intro Block Editor Handbook page. Issue 27400.

Open Floor

Should we implement a “stale bot” on the GitHub Repo? Raised by @mkaz.

The full question can be seen in this comment. A stale bot essentially automatically goes through issues after X timeframe and can be programmed to share a message before handling closing out the issue/PR. By implementing some version of a stale bot to sweep through the repo, it can ideally help keep the open issues/PRs more relevant and up to date while handling out of date items. Here are key points from the discussion:

  • We’d want a long timeframe for closing. ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. uses 90 days but we’d be looking at 120+ days.
  • Important to keep in mind, closed tickets are still searchable, still exist, and still make up the archive. They don’t disappear, and can be reopened.
  • A label could be added to keep something from being auto-closed for particular items.
  • It would be important to get the messaging right in whatever comment left by the stalebot so it’s clear what action needs to be taken to keep an issue or PR open, the reasoning for such a bot, etc.
  • It’s unclear what kind of approval/agreement is needed for this change. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. currently doesn’t have this policy but it’s unclear if that’s due to tooling limitations.

Next steps: @mkaz and @annezazu will collaborate on a Make Core post to propose this change, draft a suggestion for the messaging, and get feedback to make sure this is an okay direction to go in.

Help review a restructuring change to the Gutenberg Developer Handbook. Raised by @justinahinon.

Work is underway in this PR about Gutenberg developer handbook homepage as part of the handbook restructuring project. This PR should ideally help give a better experience with more clarity for users who first enter the handbook. The first experience matters immensely so this is a great thing to get right! Give your feedback in the PR.

What’s the best way to allow my block users to edit attributes for every display (desktop, tablet, mobile)? Raised by @louis.

Here’s an expanded version of the question for clarity:

As I understand, iframing the editor is finally coming round (really great stuff). I’ve been looking at different ways to allow my block users to edit attributes for every display (desktop, tablet and mobile), but does the Gutenberg team have an idea worked out on how these attributes will be edited responsively? And if so, is it planned for WordPress 5.7.

@joen kindly jumped in to share some great thoughts:

  • This is really tricky to get right and the team likely won’t have something for 5.7.
  • The current approach is to first and foremost build as good a responsiveness as you can, right into the block. For example, having smart defaults, like how the Media & Text block collapses when responsive.
  • Right now, you can actually hook into the preview dropdown, and leverage that to create your own responsive system right now. This is what the Layout Grid block does, feel free to look at the source there.
  • Even implementing what the Layout Grid does, the experience is still lacking: How do you edit the desktop breakpoint on a physical mobile device?  How do you customize, or add additional breakpoints? All of this is TBD.

Ideally, going forward work started in this Gutenberg issue and improvements to Global Styles can enable this to work better in the editor.

#core-editor-summary