Editor chat summary: 30 September, 2020

This post summarizes the latest weekly Editor meeting (agendaslack 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

@ntsekouras

@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

@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:

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

Editor chat summary: Wednesday, 16 September 2020

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, September 16, 2020, 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.6

Project board to track issues for inclusion in WordPress 5.6.

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

Gutenberg 9.0 was released on 16th September: 

Monthly Plan

September Monthly Priorities.

Updates on the key projects

@andraganescu

  • Both the navigation editor and the widgets editor need all the help they can get. The current target to get the Navigation editor out of experimental is Gutenberg 9.1, and if not it will not make it into WP 5.6 due to too little time for testing and consideration before beta 1
  • The work continues on the widgets editor with a lot of feedback since it was removed from experimental 
  • More details can be tracked on project boards for Navigation editor and Widgets editor

@ntsekouras

  • There is some ongoing work on 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. and here is where design is discussed/iterated: https://github.com/WordPress/gutenberg/issues/25198.Since there are many things to consider, feedback is more than welcome.

@nosolosw

There’s been some momentum around the Global Styles project lately (with Jorge, Riad, myself, and others working on this), these are the highlights:

  • Gutenberg 9.0 is the first to come with a UIUI User interface for users to update the theme 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. at the site editor).
  • Most of the add_theme_supports have been ported to theme.json  allowing themes to have more fine-grained control about the features.
  • There’s been a reorganization of 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. (docs) to better clarify its purpose.
  • Discussion on allowing creating your own CSSCSS Cascading Style Sheets. variables via Global Styles

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.

@ntsekouras

  • Added search in Query block
  • Added option to make PostTitle block a link
  • Fixed aspect ratio related classes on embed block
  • Reviews, issues, and triaging

@zieladam

  • Fixed global inserter in widgets editor
  • Moved legacy-widget block to edit-widget package
  • Working on registering widgets as block variations

@nosolosw

  • I’ve been helping others land features related to theme.json (reviews), plus landed some bugfixes and minor follow-ups related to that.

@mcsf

  • Added tiny improvements to Gallery block, ID-less shortcodes fall to 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. block
  • Discuss server-side solutions for block-supports
  • Discuss global styles architecture
  • Release 8.9.3
  • Explore dynamic content solutions for FSE templates
  • Reviews

@addiestavlo

@soean

@mapk

  • Query block iterations
  • 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 feedback and followups

@andraganescu

  • I’ve picked up some issues from Navigation
  • Wrap navigation editing features with filters
  • Added edit in place for menu name

@vindl

@itsjonq

  • Continue to explore/refine Component 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. / style ideas in G2 Components
  • Lately, been focused on the figuring out structure details for control variations that render within Gutenberg via this G2 Layouts/Segmenting controls thread

@aristath

  • I’ve been working on FSE & Global styles, trying to build a theme as a way to discover issues and fix them. Lots of PR reviews, I’ll start working on the Query block next since I’m finding things as I go.

@annezazu

  • Launched the guide for devs navigating the community
  • Focusing on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and testing this week to get back up to speed on the latest!

@copons

  • The main focus on the new Navigation component.
  • I’ve recently merged the initial PR which is not used anywhere yet and is exported as experimental.
  • The interface is in active development and will change a lot, though; while it works, it’s really not supposed to be used yet.
  • Meanwhile, it can be tested in the Storybook.
  • I’ve opened several issues for the next steps and discussions about style and accessibility.
  • Once the component is polished and fine-tuned enough, the plan is to start using it as template selector in the Site Editor

@jorgefilipecosta

  • Updated the global styles setProperty mechanism and solved an issue that made custom gradients not work on global styles
  • Refactored the global style’s shape
  • Added separate support keys for color and background-color
  • Continued the iterations on the font-family and font-weight PR’s
  • Did some PR’s reviews and participated in discussions around the repository

Open Floor

@jonsurrell

Some discussion around more descriptive post title for “The Gutenberg Release notes”. suggestion to add the 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 version for more clarity. There was no decision and further discussion for same to be done before next release post.

@pierlo

Asked if extending the external preview links dropdown would be included for WP 5.6. A PR is in the work which should very likely be merged well before the 5.6 beta begins 20th October.

@aristath

Some discussion around Query block to inherit default from the global query and allow the user to customize them as needed. This will avoid overriding the global query and replacing loops. No decision, to be discussed further.

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

Editor chat Summary: 9 September, 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-09-09 14:00 UTC. 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/ 8.9 release

Gutenberg 8.9 that was released on 2nd September and has been updated to 8.9.3.

Monthly Priorities

September monthly priorities.

Comment from @youknowriad
Most projects are properly on track and doing good progress.
Focus on Widgets screen, Navigation screen and Global styles.
The first experimental version of the Global styles UIUI User interface landed in the 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.

Task Coordination

@karmatosed

  • Working on options and iterating the options panel.

@ntsekouras

  • Add tags and filtering by author 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. ( 25005, 25149).
  • Experiments with Query block.

@andraganescu

  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and code review.
  • Worked on the Navigation editor (making menu name editable).

@youknowriad

  • Working on 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. 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. to control the editor: 20588
  • Worked on the slash inserter behavior and the block search algorihm.
  • Plan to work on: Custom CSSCSS Cascading Style Sheets. support for Group block.

@paaljoachim

@mapk

  • 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 – helping to keep it moving forward. Designs are ready for implementation.
  • Query block – Exploring flows and settings.

@justinahinon

  • Working on documenting block editor packages.
  • A few PRs are on hold. Some are ready and will need a review before commit (25150, 25142, 24947). Others need refine/minor changes, plan to be done this week.

@aristath

  • Focus on performance & sustainability for FSE Themes:
  • Progressive rendering of blocks.
  • Load only styles for blocks that are used: PR 25220

@nrqsnchz

  • Working on designs and prototypes for allowing users to upload subtitles and other types of tracks to the Video block: 7673

@nosolosw

  • Details to merge 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. at edit-site: 24250
  • Helped with assorted reviews.
  • Next week, focus on follow-ups and pressing issues I should work on next.

@get_dave

  • Focused on triaging PRs marked as “Needs Testing” and providing fixes. Review on PR of transformation from the ‘audio’ 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. to the Audio block: 25114 whereby valid attributes for a source such as `mp3` and `wav` were ignored. (Could use some input.)
  • Check of PR which addresses an issue whereby the content of the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block isn’t parsed from its serialized form correctly: 25120 (Could use some input.)

Open Floor

Discussing Widgets

During open-floor @bph referred to the Widget screen: Adding a consistent wrapper issue. The answer: Theme developers can target the block in the block area with class names. Example: .my-widget-area .wp-block-latest-posts – 

On another issue with the comment Legacy Widget block: Identify the widget in the toolbar and/or settings sidebar @bph explored what will change for widgets. “I am utterly confused on what the future widget handling entails in respect to  widget registration, functions” and if there is a goal of feature parity. 

“The APIs you raise are probably something to look at and see whether support is possible, but we shouldn’t be expecting 1-1 parity”

  • The widgets themselves should work as close as possible with the new editor. The registration and other widget related functions should also be unchanged.
  • There will be incompatibilities in hooking into the widget editor itself as the new screen uses a completely different architecture
  • If there is anything that cannot be implemented then that will break backward compatibility. If it is possible to support things it should be attempted to be supported
  • It’s a different paradigm since it will just wrap the whole list of blocks. Widgets don’t map to blocks.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Widgets vs. Core blocks, if a core widget like recent posts has a block equivalent, the core widget doesn’t appear in the inserter for the Widget screen. “Authors have the option to hide widgets if block equivalents are provided”. 
  • A theme developer declares block areas
  • All “clear evidence that we should be cautious with opt-in opt-out in Core” 

Check out the widget screen discussion.

Discussing 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) concerns.

@zebulan
Opened a PR to improve PanelBody’s add to give a summary when the section is collapsed. Intended to provide a solution to the a11y problems with prepublish checks and elsewhere. 25170 Needs a review. It complements: 24024

Noticed PRs involving UI changes/additions getting merged without getting any a11y feedback. Zeb had 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.” the a11y team to check after the PR’s have been merged.
Important to remember the checklist on the bottom in the PR template.

@mkaz
I’m not sure every UI request must require a11y feedback, shouldn’t we all be learning a11y techniques and proper usage. It should only be required for a new control. Using the base framework should be a11y compliance if it’s not something new.

@zebulan
The a11y team is working on a list of anti-patterns. Pointing people to something like that could help.
Perhaps modify the PR template checklist to include checkbox for “does my PR not use any 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) anti-patterns?”

There is discussion in this issue: 20877 in relation to creating a standard dropdown or popover. Which would really support the a11y effort.

Check out the Open Floor discussion Zeb began.

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

Editor chat summary: Wednesday, 2 September 2020

This post summarizes the weekly editor chat meeting on Wednesday, 2 September 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/ 8.9

@jorgefilipecosta announced Gutenberb 8.9 was going to be released in some hours.

The big highlight of the release is that Widgets moved out of experiments. On the FSE front, multiple FSE blocks were implemented and are now available for testing in the FSE experience (“Site Editor”). With regards to the widgets screen, more details are shared below.

Aside from these two focuses, Gutenberg 8.9 contains some small new features, multiple 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 some performance improvements.

Monthly plan updates

Global Styles

The PR that implements the Global styles sidebar on the edit site is now out of the draft state. https://github.com/WordPress/gutenberg/pull/24250. The PR allows us to have something more concrete to test the global styles mechanism and should probably be merged soon.

Besides the main global styles PR, @jorgefilipecosta said that we have proposals for font family and font-weight picking in https://github.com/WordPress/gutenberg/pull/24868 and https://github.com/WordPress/gutenberg/pull/24978.

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

Regarding the navigation block task @andraganescu said:

They’re both being worked on. For the Navigation editor (screen) the goal currently is to bring it into a sort of MVP state (outlined in https://github.com/WordPress/gutenberg/issues/24875 and then take the same steps that we took for the Widgets editor.
Recently the editor got drag and drop into its version of the ListView.
The Navigation block is getting updates via the work on the editor.
One thing that is a bit of a blockerblocker A bug which is so severe that it blocks a release. now is the uncertainty around the “edit in toolbar” feature suggested for the LinkControl, feature which is also present in some of the editor’s interactions.

Widgets screen

Besides the big update that widgets are going to move out of the experimental state on WordPress 8.9, @andraganescu added that call for testing post in progress, and it should soon make it on the make coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site).

Full Site Editing

Regarding full site editing @ntsekouras, is experimenting with the query block. Namely, adding tags, order, and some orderby support and transform multiple heading blocks to list or paragraphs.

Monthly plan preview

@annezazu shared a small preview of the monthly plan for September:

  • Global Styles & Editor focused APIs: hope is that work on editor focused APIs can be wrapped up in the month ahead.
  • 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: launched out of experimental, hoping for lots of feedback, working on an updated design, and have a nice set of 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) issues to work through.
  • Navigation Screen: discussing blockers to this being moved out of experimental & working on various items including nestinga fresh designenabling edit links in toolbar etc.
  • Full Site Editing: focused on milestone #2.

Task coordination

@jorgefilipecosta

Shared the following update:

Last week I was involved in helping the editor side tasks of WordPress 5.5.1. I reviewed multiple global styles related PR’s and shared some insights in the discussions that were happening. And I proposed the font family and weight picking mechanism.

Next week I will continue the reviews on global styles related PR’s. I will try to take the open PR’s I have to the finish line, and I will try to have a prototype of how to use and load third-party fonts.

@youknowriad

  • Working on 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 to control the editor.
  • Adding spacing controls to the group block
  • Custom CSSCSS Cascading Style Sheets. for the group block (depending on the available time)

@mapk

  • Finalized Widget Screen design iterations.
  • Digging into Query block.
  • Reviewed and helped iterate on text-only topbar.

@itsjonq

@itsjonq shared the following update:

I’m continuing to work on the G2 Components project. Currently focusing on creating (also supporting the creation) of larger pieces.
One of the ways this is manifesting is through prototyping more complete UIs/experience (e.g. Navigation, and soon FSE/Global styles).
Also exploring how G2 components could be used in WP-Adminadmin (and super admin). Another focus to evaluate potential integration into Gutenberg (via `@wordpress/components`).
One of the results from this is splitting parts from the core system so that smaller chunks can be migrated (e.g. Style system)I’ve continued to host Zoom session calls + blog G2 components updates on the blog:
https://g2components.wordpress.com/Also updating the documentation as I go:
https://g2-components.com/As always, open to feedback + suggestions! From UIUI User interface designs to workflows, to documentation, etc…
I’ve received a few already, which have been lovely.

@michaelarestad

@nosolosw

Shared the following update on the agenda:

  • This week: I’ve made progress on adding an initial prototype for the global styles sidebar in the Site Editor. Just today the PR moved from draft state to open for reviews. It still needs some tweaks, but, fundamentally, it’s a candidate for merging. I’ve also been helping here and there with feedback and reviews.
  • Next week: keep pushing this work forward.

Open floor

Justify use of “Needs… Feedback”

@isabel_brison wrote on the agenda post:

I’m wondering if we should try/encourage adding comments to justify use of “Needs… Feedback” labels in Gutenberg, as it’s not always obvious which aspect of the issue/PR needs feedback. It would help if the person adding the label elaborated a little on where feedback would be useful.

@jorgefilipecosta said it makes sense that when someone uses a feedback label to also include a comment saying exactly what feedback is needed. As sometimes, the discussions get big passed by many topics, and it is not easy to know what actionable feedback is needed.

@youknowriad said that adding process over process is just raising the bar for contribution. And added that it’s also fine to ask “Why did you add the Needs thing feedback”?

@mapk referred he noticed that many designers do list out the feedback they’re looking for when a design is proposed. @jorgefilipecosta said that we should probably expand that practice to non-design PR’s.

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

Editor chat summary: 26th August 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-08-26 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/ 8.8 has been released

Gutenberg 8.8.0 is now available. Release leadRelease Lead The community member ultimately responsible for the Release. @itsjonq joined us and provided his highlights:

  • forward movement + momentum on some of the bigger projects of Gutenberg, like Widgets, Full site editing, and the Post 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. suite
  • Improved UIUI User interface for 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 mobile, especially surrounding Toolbar and pop-up like components (like menus and Popovers)
  • there also appears to be a tiny performance improvement compared to 8.7.

@itsjonq ended the overview of this new release by giving huge personal thanks to everyone who helped me before/during the release process to help get 8.8 out.

Monthly Plan & Key Projects

Task Coordination

  • @annezazu
    • I’ve been focused on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., light testing, and working on this Guide for Devs Working in the WordPress.org Community. Slower moving than I want to be on the guide a bit right now but feedback welcome.
  • @youknowriad
    • I’ve landed some PRs to use allow the usage of _fields  in  core-data improving some of the 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/. calls performance in the editor.
    • Next couple weeks, I want to make a push on the Block Editor Controlling 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. (part 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.)
  • @jorgefilipecosta
    •  I reviewed global styles related PR’s. I am working on implementing font family controls on the global styles context.
  • @michael-arestad
    •  I’ve started in on Block Directory work. I’m starting in on updating the current install flow (via block inserter search). I’ve already got some good feedback that I am using to make a new iteration that should be posted in an hour or two. I will also be exploring block management in and out of the editor.
  • @nosolosw
    • I’ve been focused on other tasks the past week. For the next week, I’m continuing work on 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. at site edit & controlling the block editor.
  • @zieladam
    • Last two weeks I was focused on addressing security issues in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and in 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, unfortunately I don’t have any links to share.
    • Starting this week I’m back on the widgets editor. After merging the initial version@noisysocks composed a list of all the reported issues that I’m going through and publishing multiple PRs  Also, @mapk is exploring the design of the widget editor. While these explorations are still in progress, I already started prototyping a few suggesstions.
  • @ari
    • I’ve been focusing on exploring FSE and ways to improve it…
      • performance (switch from post-metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. to a 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. for the theme)
      • allowing the use of arbitrary units in columns
      • More styles cleanups for front-facing styles
      • Other minor bugfixes wherever I encounter them
      • Triage
    • Next week I’ll keep working on front-facing styles and start diving deep in global-styles as much as I can
  • @mapk
    • Iterated on 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 designs and Legacy Widget block.
    • Provided some feedback and design work on a text-only toolbar.
    • Trying to triage our 2400+ issues.
  • @itsjonq
    • I’ve continued focusing on the “G2 Components” project.Enough of the foundations have been designed/built, so I’m starting to explore large things like:
      • Prototyping/Building large/complex UI
      • Documentation (to support prototyping/building)
      • Tooling to improve design/dev experience
    • I’ve continued to host Zoom sessions where I collab design/dev things in G2.  I plan on continuing! They’re wonderful .I’m blogging all notable updates here.

Thank you for the work that is happening and does not make it into this list!

Open Floor

  • @desrosj
    • I’m here to flag that 5.5.1 will be released a bit more quickly than usual because of some pesky bugs that were discovered. It would be great if some block editor 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 were included! Happy to help if needed. The proposed schedule was just published.
  • @annezazu
    • Woohoo! I’m starting the “What’s Next” post for September and wanted to check in with this crew collectively to see what will be the focus for the month including any specific PRs, discussion issues, etc you’d like to flag. Don’t need to cover it all in this meeting but high level items would be lovely
      • @andraganescu the work on the new editors (Navigation and Widgets) will continue in September
      • @youknowriad I see a continuous effort on “Controlling Block Editor APIs” as well, I’m hoping to “finish it” on September if things go well.
  • @andraganescu
    • I want to raise that we want to move those editors out of experimental. There is a great deal of work still happening and still needed, but it’s important that  they become visible sooner rather than later.
      • @mapk With Matias’ recent feedback on the Widget Editor, I think this can happen. It appears we’re keeping a closer tie-in with my initial designs which are pretty much implemented.
  • @paaljoachim I was thinking about the general importance of drag & drop. How we can improve it in Gutenberg?
    • A discussion followed suggesting we add drag and drop in select mode and debating how it should work when writing
  • @itsjusteileen
    • Wondering if, in conjunction with any documentation being done for getting setup to do testing, if there wouldn’t be someone willing to do a zoom for folks interested in getting all the tooling needed to get started. It’s a bit of a barrier of entry for some folks.
  • @mkaz announced in a follow-up that he’ll be hosting a “hallway hangout” session on contributing documentation to Gutenberg repository. It will be an introduction covering 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/ PR workflow and environment setup.  The session will be on Tuesday, Sept 1st @ 1600 UTC / 9:00am PDT. It will be recorded and posted for those who can not make it.

Thanks to everyone who attended.

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

Editor chat summary: 19th August 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-08-19 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/ 8.8.0 release

  • At the time of the meeting it had not been released but Gutenberg 8.8.0 is now available.
  • Release leadRelease Lead The community member ultimately responsible for the Release. @itsjonq joined us and provided his highlights:
    • Full site editing has progressed with updates to Global Styles, the Post 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. suite, and Template management.
    • Initial work has begun on the new 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 – a project that’s part of a wider effort to add more block enabled sections to the WordPress experience.
    • This release also saw important 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 mobile improvements to user-interfaces like the Toolbar, navigation menus, and Popovers.

Monthly Plan & Key Projects

Navigation screen, Navigation block and Widgets screen

@andraganescu provided the update:

Andrei also point us towards the Navigation screen and Widgets project boards where help for code review, testing and picking up issues is always welcome.

Global Styles & Editor focused APIs

@nosolosw provided the update on his two focuses for the month:

  • Land an initial user-facing tool to set styles globally.
  • Make progress on controlling the block editor, see tracking issue. The idea is to enable themes to control the editor via 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..

For people interested in this area of work, the tracking issue lists specific tasks to help with.

For people getting started, a good first Issue is to migrate core blocks to use the implicit style attribute for colors and/or font-size.

Full Site Editing

@michael-arestad provided the update:

  • An iteration on the multi-entity saving flow is in the works!
  • Several of the post blocks now have icons and descriptions.
  • A mockup for a document-level grid has been proposed.
  • I’m starting in on everything related to the block directory.

@annezazu also reminded us about:

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.

No one was available to provide an update. If anyone would like to provide this async, then please leave an update in the comments.

Task Coordination

Open Floor

Thanks to everyone who attended.

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

Editor chat Summary: 12th August, 2020

This post summarizes the weekly editor chat meeting agenda. Held on 2020-08-12 14:00 UTC in Slack. Moderated by @paaljoachim.

WordPress 5.5

WordPress 5.5 was released on 11th August.

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

The latest release of Gutenberg, version 8.7 was released 5th of August.

The Monthly Priorities

The monthly plan for August.

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

Scroll back to Navigation block chat.

Task Coordination

@zebulan

@youknowriad

  • I’ve been working on the server-side support for Block 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. support flags.
  • Upgrading some libs (ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/., lodash)
  • I’m planning to focus more deeply on the “Editor controlling APIs”
  • I’ll probably spend some time on the forums to check 5.5 feedback and issues.

@aristath

  • This week I’ve been working on prep work regarding block styles and FSE/Global-Styles: Removing hardcoded colors from block-styles, separating editor & front-facing styles, converting absolute units to relative etc.

@ntsekouras

@zieladam

@mapk

  • Accordion block. I’ll have some style variations up this week.
  • Topbar labels for icons with @tellthemachines.
  • New icons for Post blocks.
  • 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.-block editor designs (Figma file).

@annezazu

@joen

  • Catching up and reviewing. Always happy to review.

@mcsf

  • Helped @ntsekouras land his changing of Embed blocks to block variations.
  • Been reviewing PRs such as refactors or Global Styles-related items.
  • Triaging issues.
  • Team support.

@shaunandrews

@sageshilling

@q

  • Focus on experiments on evolving the Editor UI.
  • Taking a deep look into wordpress/components, and seeing how it can be improved to address many pain-points + missing features we have today, and setting up the UIUI User interface layer for success for the future. One of the many drivers for this is my involvement in improving editor Design Tools, which relies very heavily on the UI layer. I’ve started sharing some of these updates with folks via Zoom sessions, 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/ posts, and most recently, a dedicated blogblog (versus network, site) (published yesterday) https://g2components.wordpress.com/
  • I’m planning on hosting another collab Zoom session today.

@noahtallen

  • Working on moving Global Styles forward and how that looks/feels within the editor (will be getting these into an issue soon) [Full Site Editing]
  • Moving the first iteration of Multi-Entity Saving forward with engineering [Full Site Editing]

Comment by @paaljoachim

  • Let’s be sure that any Full Site Editing UI adjustments are also reflected back to the regular Gutenberg content creation where it is applicable to do so.

Open Floor

From the agenda post.
@zebulan brings focus to the work done by @aristath on the usage of relative units (rem, em) in relation to block styles in themes and removing hardcoded colors. PRs.
https://github.com/WordPress/gutenberg/pulls/aristath

@psykro
Getting workshops up on learn.wordpress.org. One of the workshops is a beginners guide to block development, following by a group discussion. It would be helpful to have Gutenberg developers present. We need feedback. The group discussion details (including date and time) are on the meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. event – https://www.meetup.com/learn-wordpress-discussions/events/272503390, the actual workshop you can watch any time on learn.wordpress.org.

@aristath
Supporting prefers-color-scheme queries.
Gutenberg has no option to set a Dark scheme in relation to user preference and 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) issues. Discussion: prefers-color-scheme media-query
@paaljoachim
Check the experimental design tools by @q as color schemes is one of the areas he is experimenting with.

@mkaz
“Remove Embeds for Facebook and Instagram”
https://github.com/WordPress/gutenberg/pull/24472
Basically Facebook is changing the FB and Instagram embeds on Oct 24, so older embeds will no longer work. So at what point should we remove from WP?
@paaljoachim
Brought up the above issue during the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dev chat in the #core channel on 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/.. Link to discussion: https://wordpress.slack.com/archives/C02RQBWTW/p1597265852021400

@itsjusteileen
Andrei are there notes or follow up on the Nav meetings?
@andraganescu
Not yet.
@itsjusteileen
The idea being theme authors need to look at building progressive enhancements, and keeping up with this feature even if it is exploratory would have benefit to FSE and communicating with the theme team. I can take a look at today’s meeting then and go from there.
@paaljoachim
Back scroll link to Navigation meeting held in #core channel on Slack.

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

Editor chat Summary: 5th August, 2020

This post summarizes the latest weekly Editor meeting (agendaslack 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, August 5, 2020, 08:00 AM MDT and was moderated by @annezazu.

WordPress 5.5 RC 2

WordPress 5.5 RC 2 is now available with WordPress 5.5 is slated for release on August 11th, 2020.  Remember to help translate, test, and report bugs — all lovely and helpful ways to contribute. On a related note, you can follow along with WordPress 5.5 “Must Haves” for Gutenberg on this board although there’s not much left.

If you like to look ahead, check out this “What’s on your wishlist?” post for planning 5.6 and share your thoughts by August 20, 2020. 

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/ version 8.7

Gutenberg 8.7.0 was released last week. Update your sites and check out what’s new. Thanks to everyone who helped with this release.

Monthly Plan

Here’s the overarching plan for August. With efforts around 5.5 winding down, this opens up work to return to areas like 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, and continued work on the Navigation screen & 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.. Details are in the post!

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!

@ntsekouras

  • Fixed block insertion place after clicking Browse All in the inline inserter.
  • Completed some 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) fixes (fix block movers overlapping, Add arrow navigation to Warning dropdown menu.)
  • Polishing refactor embed block to be a single block (with 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 block variations.  

@zebulan

  • Working on some enhancements to the InnerBlocks 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. including currently trying to rewrite a PR to use the callback API suggested here. Could definitely use some help getting it to work.
  • Keeping various other PRs up-to-date. Most of them are simply awaiting design/technical reviews.

@paaljoachim

  • Helping triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Gutenberg Design issues.
  • Giving feedback to various issues.
  • Attended and recorded @itsjonoq’s very cool Zoom jam session.

@annezazu

  • Shipped the what’s next in Gutenberg post for August.
  • Helped with WordPress 5.5 Q&As.
  • Focused on needs-testing for triage.

@youknowriad

  • Working on 5.5 and Gutenberg fixes, 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. releases.
  • Started working a little bit on the Block API supports flags and planning to expand the work to Global Styles.

@andraganescu

@itsjonq

  • Continued experimentation + research in the area of the Editor Interface and component layer. This is in support of Design Tools and the efforts of refreshing the editor experience. It’s materialized into a component library with a focus of design/developer experience (working with or using the parts). There’s also the goal of having core/system level a11y support, including visual considerations (dark mode, high contrast, color blindness, reduced motion).
  • Shared this work with a couple of folks on a hallway hangout Zoom call (more to come!) and wrote a follow-up Github post here. It’s worth noting that this is highly experimental!

Open Floor & Ways to Help

Throughout this core editor chat, there was a theme of people highlighting and wanting help with various issues. As a result, the structure of this summary is being adjusted to fit the content. Remember: teamwork makes the dream work ❤️

Give feedback on this new navigation overview issue. Raised by @andraganescu.

It proposes a path forward for a few things, including:

  • How the blocks in navigation feature will work
  • How backwards compatibility will be handled
  • How rendering of this feature will function

Review PRs on Block toolbar: split switcher from mover and simplify styles issue and Document settings: Split “Status & visibility into multiple sidebar panels. Raised by @zebulan.

Both of these issues address things that the a11y team would really like to see make it into core.

[Completed] Review this PR on setting an error state when there is an upload error. Raised by @kirilzh.

@itsjonq already reviewed this PR and it’s been merged since the meeting took place. Great job, everyone.

Give feedback on the approach taken in this PR on showing sibling inserter on hover. Raised by @kirilzh.

In particular, right now @kirilzh is feeling stuck trying to handle blocks with nested blocks in them. Any guidance anyone can give on general approach would be appreciated to help refine this PR.

Help review this open issue showing different behaviors for default category term with editors. Raised by @enricosorcinelli.

There was some discussion in slack about this particularly on the topic of where the root issue ultimately is: 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/. or block editor 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.. @timothyblynjacobs chimed in just after the meeting closed to clarify that the actual bug is that the REST API allows emptying that categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. in the first place. This now seems to be a question of general product decision: is it okay to have a post without categories? What’s the historical context here? If you have thoughts to share, please chime in on the thread.

#core-editor-summary

Editor chat summary: Wednesday, 29 July 2020

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, July 29, 2020, 14:00 UTC.

WordPress 5.5 RC 1

The first release candidate for WordPress 5.5 is now available. This is an important milestone in the community’s progress toward the final release of WordPress.

Thank you to all of the contributors who tested the 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.

Project Board For WordPress 5.5

The remaining issues are located in the Project board.

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

Gutenberg 8.6 was relased on 22nd July.

Monthly Plan

What is next in Gutenberg for July.

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.

@annezazu

@ntsekouras

Refactor embed 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. to be a single block ( with 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 block variations. (https://github.com/WordPress/gutenberg/pull/24090)

@sageshilling

Working on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. media block editor proposal

@shaunandrews

Design work continues for the new editor sidebar

@mapk

@itsjusteileen

Testing in FSE. Moving to a new machine and will need to give @paaljoachim, @mkaz, and @Noah Allen dev environment tutorial a run on setting up from scratch for testing Gutenberg.

@nrqsnchz

  • Merged the last remaining PRs for Block Patterns and tested across Core default themes.
  • Been helping with testing and feedback on various 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)-related issues

@mcsf

  • WP5.5: Review fix/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. PRs, review/help with 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.
  • Review many PRs or comment in issues
  • Try to improve Docker performance on macOS (24001)
  • Support some other contributors at an individual level

@andraganescu

@michael-arestad

I’m working on a flow for creating a template from scratch – Currently, I’m  exploring “designing” a layout via document-level grid. I’m also planning a jam session or two next week. 

@zieladam

  • Focused on in-toolbar link editing (#24021)
  • Investigating the way forward for the widgets editor
  • Working on fixing e2e tests on the AutosaveMonitor fix in #23962

@itsjonq

  • Continuing with Design Tools Efforts (in general)
  • Focus lately has been advancing @wordpress/components in the spirit of the new “G2” designs. Approaching it systematically from foundations (much needed IMO) rather than applying tweaks on top.

@zeb

  • Got a PR merged that moves the reusable block’s “Convert to regular blocks” button to the block toolbar! https://github.com/WordPress/gutenberg/pull/24066
  • A few days ago I created a PR to implement an `itemWrapper` prop for `InnerBlocks` that allows child blocks to each be wrapped with a given element. It’s a rather significant change and there may be better ways of implementing it, so any technical feedback and ideas are much appreciated! https://github.com/WordPress/gutenberg/pull/24232

@isabel_brison

  • I’m working on adding labels to the editor icon buttons (10524 and 15311). I’ve done an initial PR to add an option to show labels, but it only affects the post editor for now. I think we’re going to need this functionality in the site editor too, and am wondering what would be the best way of having a setting that works across both editors. Thoughts welcome!

Open Floor

Patterns and WordPress 5.5

@joyously asked about the pattern, are they part of GB or part of WP? The reason is that the images are stored on .org, and the text goes through .org translations. @youknowriad clarified that Patterns live in Core codebase and the images are hosted in wp.org like the block examples.

Cherry picking from Gutenberg 8.7 for WordPress 5.5

@jeffpaul asked are there any 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 performance improvements that are planned to be cherry-picked from Gutenberg 8.7 to merge into WordPress 5.5? To prepare WordPress 5.5 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. @youknowriad mentioned that the potential addition fixes might not be worth mentioning.

Documentation “Keeping up with gutenberg” Index

@annezazu shared about a new page in the core handbook called “Keeping up with Gutenberg”. It’s an index of Gutenberg related posts from various Make blogs to make it easier to follow development. Feedback is very welcome to improve it. Props to @bph and @williampatton who led these efforts. @swissspidy raised if there is a way we can somehow automate that list of posts? as currently its manually curated and seems tedious to maintain.

Galleries as composed image block

@andraganescu raised @Zeb added https://github.com/WordPress/gutenberg/pull/24232 and @noisysocks raised the PR for discussion here as it affects some implementations that count on InnerBlocks including the blocks in navigation feature and the implementation of galleries as composed image blocks

Some discussion around wrapper for the inner block but no decision. Further discussion to continue on the PR for introducing prop to specify the wrapper

Missing post update action

@paaljoachim highlighted the issue of missing “Update post” action when there’s an autosave.

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

#core-editor-summary

Editor chat Summary: 15th July, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 15th July 2020 held in Slack. Moderated by @itsjusteileen.

WordPress 5.5 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

Beta 2 was released 14th July.

Project board for WordPress 5.5.

The remaining issues are located in the Project board.

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/ release 8.5

Gutenberg 8.5 was released 8th of July. This is the last 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 that is going to be included entirely (without experimental features) in WordPress 5.5.

Monthly Priorities

What is next in Gutenberg for July.

Link to the first 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. chat

Back scroll to the first Navigation block Slack chat meeting

Task Coordination

@zebulan
I opened a PR to implement a solution to make the Improve parent block selector button UI. Needs more feedback.
PR: More block: use an actual placeholder for input text.
PR: Heading block: add heading level checker needs a final code review.
PR: Polish Custom HTML block Needs design feedback and code review.
PR: Fix odd usage of transform-styles wrap function (and tighten types) and
Block Editor: use optional chaining and nullish coalescing instead of Lodash.get needs reviews.
PR to lighten the editor DOM of the Buttons block is still blocked by an issue with how AlignmentHookSettingsProvider works. Technical help is needed to proceed. My plans to fix the current confusing/half-broken state of the Buttons alignment controls rely on this PR.


@mkaz
Working on docs, good progress on dev env setup and Create a Block tutorial. An open PR-23946 links up the Create a Block tutorial making it the starting point for block development. Once merged, we need to audit older block tutorial to correct overlap and expand it to be for intermediate topics.

@paaljoachim
Documentation: Installing a local development environment has been separated from the new block creation tutorial. Almost finished with the dev environment documentation and will be asking for testing when it is finished. A new PR for the third iteration of the dev env docs will be created soon.

@zieladam
Content loss/autosave issue: #23781
New idea of “local drafts” library: #23955
Navigation screen project board.
New link editing interface (directly in block toolbar): #23375

@annezazu
Launched the “Versions in WordPress” Doc with help from @mkaz
Light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. focused on unlabeled & block directory testing.
Gave feedback on the language around the block directory checker plugin.
Hoping to start work this week on updating the Gutenberg FAQ.

@ntsekouras
Refactored MediaPlaceholder and More blocks to function components.
PR for Classic block content bug.

@shaunandrews
I posted a design for a new sidebar for navigating between templates, posts, and pages without leaving the editor.

@nrqsnchz
Shepherding the last remaining updates and tweaks to the block patterns that will ship with 5.5.
Started looking into Site Editor: Improve template part visibility.
I’ve yet to start looking at updating wp.org/gutenberg. Will focus mostly on graphics and images.

@youknowriad
The big priority for me is 5.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, package releases and backports.
I helped review several PRs: FocalPointPicker, Perf testing for site editor…
Worked on several small performance improvements here and there.
Starting to work on 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. for 5.5.

@ItsJonQ
Continuing with Design Tool efforts.
Continuing research/experiment on improving our (ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/.-powered) 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/. UIUI User interface within the Editor.

@cvoell
Updating documentation with latest native mobile updates.
This includes a new section on troubleshooting new native mobile CI jobs, and improved tracking for any remaining randomly occurring failures.

Open Floor

@jonsurrell
The Gutenberg plugin only includes minified JavaScript.
The minified JavaScript uses .js extension not .min.js.
That diverges from what WordPress conventions and what WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does. Even the Gutenberg packages bundled into core include readable and minified sources with .js and .min.js extensions, respectively.
I have opened this PR to propose that minified JavaScript in Gutenberg use the .min.js extension to align with convention.

@jonsurrell
Should we ship readable sources in the Gutenberg plugin?
New issue created. Plugin: Include readable source files which also includes a link to 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/. discussion.

@jonsurrell
How to disable the Block Directory on some sites?
New issue created: Block Directory: Provide documented way to disable.

@mkaz
We updated the GitHub workflows to not run some actions (e2e & unit tests) if only markdown files are changed. Tests had to be removed from required list due to how 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 work. It is possible for the tests to now fail, but the merge button is allowed. So for those merging, please double check all tests pass. We want to try it out and see if it causes a problem. The change is a good boost to speed up tests and use less resources that helps other tests to run. There is a ticketticket Created for both bug reports and feature development on the bug tracker. open on GitHub to allow conditionally requiring actions.

@enricosorcinelli
Opened tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket and now Github issue for Different behavior for default category term with editors.

@itsjusteileen
Did anyone ever propose an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. block?
There is no Github issue for this yet.
@paaljoachim
There is one for iframing all of the content (but none for iframing a block):

@BackuPs
When is this gonna be fixed? Normal editor on rtl switches shortcode enclosed content and html content. Check the ticket for more information.

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