annezazu 11:14 pm on August 6, 2020
Tags: 5.5 ( 75 ), accessibility ( 35 ), core-editor

WordPress 5.5 Core Editor Accessibility Improvements

In an effort to better communicate the specifics of what’s coming to the editor in WordPress 5.5, this post is meant to list the various 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) improvements shipping with this upcoming releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. on August 11th. Going forward, the “What’s Next in Gutenberg” posts will have clearer accessibility-related callouts to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it easier to follow relevant issues more regularly. The work to improve WordPress is never finished, and with more releases will come more improvements, but it’s encouraging to see progress in so many areas.

Thanks to everyone who worked hard to get these improvements in place in time for 5.5!

In most sections, explorations are shared of specific high impact improvements. Please view individual issues for more details.

New Editor Design

WordPress 5.5 brings numerous changes to the look and feel of the editor, informed by the goal of reducing complexity by simplifying iconography, color palette, focus, and general interface. As more features are added 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, a simpler and clearer design allows the interface to scale more gracefully. Examples include: the effort to create a single toolbar to have fewer tab stops, work done to make the single primary toolbar bigger (more tappable with a larger touch area), and higher contrast. Some changes, such as removing borders around selected blocks, have inspired spirited debates, and it’s been great to see so many people involved. As always, discussion, iteration, and collaboration are our best tools for moving forward together.

Screenshot showing the previous editor design.

Screenshot showing new design editor for 5.5 — Screenshot showing the previous editor design.

Keyboard Navigation Improvements

Enable block movement between levels using a keyboard.
Add keyboard shortcuts for moving blocks.
Improve keyboard navigation on Gallery blocks.
Add keyboard Shortcut to toggle Fullscreen.
Improve copy/paste block experience.
Improve keyboard operation of the LinkControl component
Add option to keep the caret inside block in edit mode.
Add arrow navigation between nesting levels in Navigation Mode.

Below is a screenshot highlighting the new keyboard option mentioned above that can be found in “More tools & options > Options” modal. Checking it will stop arrow keys from navigating between blocks in edit mode. You can also programmatically auto-enable it with this code snippet:

if ( 
  ! wp.data
      .select(‘core/edit-post’)
      .isFeatureActive(‘keepCaretInsideBlock’) 
) {
  wp.data
    .dispatch( ‘core/edit-post’ )
    .toggleFeature( ‘keepCaretInsideBlock’ );
}

Screenshot showing the “More tools & options > Options” modal where the new option lives.

The following video shows a walk-through of arrow navigation between nesting levels while in Navigation Mode mentioned in the above section:

Video showing a walk-through of arrow navigation between nesting levels.

Screen Reader Improvements

Announce all notices from the notice store properly.
Add heading to block inserter tips to make it more visible.
Remove titles from Button blocks.
Fix snackbar labels.
Fix missing label in Heading Toolbar.
Add explanatory text before the a11y.speak aria-live regions.
Fix overly verbose aria-label on the Social Link block
Improve announcement of CustomSelectControl on some screen readers.
Add copy action for touchscreen users or users who don’t use keyboard shortcuts.

Focus Improvements

Create consistent focus styles in the UIUI User interface.
Fix focus loss on the welcome guide.
Fix focus styles and improve Windows High Contrast mode styles for the Post Calendar component.
Implement roving tabindex on the HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. Toolbar.
Fix extra tab stop on the Modal component.
Fix focus loss issue in LinkControl component with edit mode toggle.
Fix focus loss in between row/column insertions in Table Block.
Implement roving tabindex on Block Toolbars.

The following video demonstrates the roving tabindex across block toolbars. Of note, the APIs to achieve this improvement in wordpress/components are listed as experimental for now and should ship in 5.6 so third-party developers can use them as well.

Video showing the roving tabindex across block toolbars.

If you’re interested in improving accessibility in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor, check out the accessibility team, review the current open issues related to accessibility, provide accessibility feedback on issues, and help test 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/.

#5-5, #accessibility, #core-editor

annezazu 4:25 pm on August 6, 2020
Tags: core-editor, core-editor-summary ( 18 )

Editor chat Summary: 5th August, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel on Wednesday, 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 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 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

Working with @noisysocks @talldanwp @isabel_brison and @zieladam to advance the two new editors for widgets and navigation.

@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 makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). 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

Riad Benguella 12:56 pm on August 5, 2020
Tags: core-editor, editor ( 156 ), gutenberg-new ( 72 )

What’s new in Gutenberg (August 5)

WordPress 5.5 is around the corner and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ contributors have been busy fixing a number of important issues to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure the editor on 5.5 is as stable as possible. Gutenberg 8.7 changelog reflects that with a number of fixes including important 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) ones.

At the same time, contributors are increasing the development pace on the next big projects. Global styles are being worked heavily on with the hope of shipping it by WordPress 5.6.

This releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. also saw a lot of improvements to 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 that constitutes one of the important bricks for the Full Site Editing project.

8.7.0 🇹🇼

Enhancements

Make “Attempt Block Recovery” the default option of block invalidation. (24263)
Add a block example to the Buttons block. (24249)
Make the padding for the nav block inserter content the same for all sides. (24084)
Improve margin within the media replace popover. (24309)
Move “Convert to regular blocks” button to the reusable block toolbar. (24066)
Consistently autosave edits. (23962)
Use Post Type label for Document tab in Settings 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.. (17311)
Update the Group block description. (24297)
Remove bottom margin of components dropdown menu item. (24227)
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Block Patterns improvements:
- Adds “Heading and paragraph” pattern. (24143)
- Updates “Large header and a paragraph” pattern. (24142)
- Updates the “Large header” pattern. (24141)
- Updates the “Quote” pattern. (24140)
- Updates “Two images” pattern. (24139) (23856)
- Updates “Three columns of text with buttons” pattern. (24138)
- Updates “Three buttons” pattern. (24137)
- Updates “Two buttons” pattern. (24136)
- Updates ‘”wo columns of text” pattern. (24135)
- Update “Two columns of text with images” pattern. (24134)
- Update the “Large header and button” block pattern. (24177)
Block Directory: Use local assets with automatic asset detection. (24117)

New APIs

Add support for delete operations to @wordpress/core-data entities. (21557)
Add server-side handling for the block ‘align’ supports flag. (24122)
Add isDestructive style to Button. (22921)
wordpress/create-block: Enable loading translations for created blocks. (24125)

Bug Fixes

Fix htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. mode for non light blocks. (24335)
Fix block movers overlapping. (24349)
Fix List RichText backward compatibility for multiline root tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). (24324)
Block patterns: Fix translatable strings. (24317)
Preserve the seconds when editing dates using the TimePicker component. (24305)
A11y:
- Announce block selection changes manually on windows. (24299)
- Fix arrow navigation in the LinkControl suggestions. (24222)
- Avoid focus style from being cut on the categories panel. (24197)
- Avoid focusing the block selection button on each render. (24195)
- Avoid rendering the clipboard textarea inside the button. (24194)
- Fix missing focus outline in Add New Tag. (24187)
- Fix dropdown menu focus loss when using arrow keys with Safari and Voiceover. (24186)
- Fix the gallery buttons focus style. (24157)
- Update the editor landmark regions. (24196)
- Mover control: Remove drag cursor. (23759)
Fix block insertion place after clicking Browse All in the inline inserter. (24285)
Fix last.fm svg icon alignment. (24278)
Cover: Fix padding controls showing null units. (24251)
Consistently show the default style variation if none provided. (24217)
Fix gradient RGBA/HSLA inputs’ width. (24214)
Popover: Fix arrow color to match content border color. (24208)
Fix dragging multiple blocks downwards resulted in blocks inserted in wrong position. (24183)
Fix Button block colors in the editor. (24153)
Fix the save shortcut in the code editor. (24151)
Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 notices when a block hasn’t declared ‘supports’. (24131)
Fix Block Directory icons. (24086)
Block Breadcrumb: Fix arrow direction in RTL. (24074)
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.:
- Fix missing plural forms for block related strings. (24071)
- Merge similar translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. strings in the RSS block. (24159)
- Merge similar translation strings – tables. (24169)
useBlockSync: Fix race condition when onChange callback changes. (24012)
Allow enter to insert line breaks even if template is locked. (23330)

Experiments

Full Site Editing and Site editor:
- Add alignment support to post content block. (24014) (24077)
- Post Title Block: Add style attributes. (24246)
- Remove more initial PHP state. (23775)
- Template Part: Improve title editing interactions. (23661)
- Update the Post author, ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. and Comment blocks to use lightBlockWrapper. (24253)
- Query blocks: Support wide alignments in the editor. (24229)
- Post Comments Block: add block alignment support. (24226)
- Post Excerpt block: Added icon and description to Post Excerpt block. (24203)
- Post Date block: Added Post Date icon and updated block with icon and desc. (24178) (24225)
- Post Author block: Added a description. (24171)
- Post Comments Counts: Add style attributes. (24167)
- Post Comments Form: Add style attributes. (24162)
- Post Author and Post Excerpt: change editor selector class. (24104)
- Post Comments block: add style supports for text and background settings. (24080)
- Post excerpt block: Add color, fontSize, lineHeight, and text alignment. (23945)
- Add Post Tags block description and icon. (23496)
- Add a description to the Post Title block. (23494)
- Update Post Author block to use __experimentalColor and __experimentalLineHeight. (23044)

Global styles:
- Fix link color style property name in global styles. (24296)
- Fix merge algorithm. (24294)
Navigation Block and screen:
- Fix Navigation Block submenu being overlapped by Cover block overlay. (24062)
APIs:
- Add initial support for themes to control the editor. (24275)
- Prefix useSimulatedMediaQuery __experimental. (24279)
- URLInput Customizable control rendering. (24115)

Documentation

Update Gutenberg FAQ with more recent information. (24202)
Clarify custom link color documentation for themes. (24056)
Add a link to the WordPress Data guide. (24327)
Document the new block tools theme support and core block patterns. (24265)
Replace the demo link of the Gutenberg Storybook in the documentation. (24212)
Docs: Update default values for Popover props ‘noArrow’ and ‘position’. (24207)
Added missing documentation link for contributor handbook. (24179)
Docs: Convert Block Registration RFC to the Block Metadata document. (23832)
Typos and tweaks: (23899) (24057) (24033) (24211) (24100)

Code Quality

Improve rootClientId comparison in useBlockDropZone. (24307)
Clarify wp.blocks.createBlock error message. (24287)
Convert blocks to function component with 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.:
- BlockInvalidWarning. (24284)
- ReusableBlockConvertButton. (24015)
Add missing prop to WPBlockVariation type definition. (24110)
Remove deprecated blockType.context support. (24155)
Wrap LinkControlSearchInput in forwardRef. (24119)

Build Tooling

Perf Tests: Set up 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". only once for all test suites. (24123)
Revert “Build: Use .min.js suffix for bundled 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/.”. (24239)
Add a GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. Diff to the output of the static checks job on failure. (24154)

Various

Fix intermittent Navigation block test failure. (24146)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version	Loading Time	KeyPress Event (typing)
Gutenberg 8.7	6.97 s	26.63 ms
Gutenberg 8.6	6.84 s	27.15 ms
WordPress 5.4	9.55 s	43.81 ms

Kudos for all the contributors that helped with the release. 👏

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

Ajit Bohra 11:35 am on August 5, 2020
Tags: core-editor, editor ( 156 ), gutenberg ( 193 ), meeting notes ( 91 )

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 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 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

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. focused on needs-testing and a quick FSE test
Helped review this new index for keeping up with Gutenberg
Shared an idea I’m calling “hallway hangouts” & helping wrangle some sessions
Updated the Gutenberg FAQ (PR here)
Working on the “What’s Next in Gutenberg” post for August
Raised my hand to help with the 5.5 Q&As

@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

Post block updates.
Post block icons
Accordion block
Digging into Browse mode

@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

generally working on the navigation editor (screen)
working to help picking the widgets editor (screen) project back up
merged https://github.com/WordPress/gutenberg/pull/21557 and now entities have a delete operation available (props @epiqueras)

@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 Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). 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

annezazu 4:11 pm on August 4, 2020
Tags: agenda ( 485 ), core-editor, core-editor-agenda ( 22 )

Editor Chat Agenda: 5 August, 2020

Facilitator and notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for 2020-08-05 14:00 UTC

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

WordPress 5.5 RC2
Project board for WordPress 5.5
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
Monthly Plan
Task Coordination
Open Floor

Even if you can’t makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the meeting, you’re encouraged to share anything relevant for the discussion:

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

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

annezazu 5:06 pm on August 3, 2020
Tags: core-editor, gutenberg-next ( 10 )

What’s next in Gutenberg? (August)

This is a monthly update containing the high-level items that GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ contributors are focusing on for August. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. Tied to this, there’s a new page courtesy of @bph, @williampatton, and myself that provides an index of Gutenberg related posts across various Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). blogs.

Addressing WordPress 5.5 feedback

WordPress 5.5 is set to be released on August 11th and any efforts spent here will be focused only on addressing critical regressions that might come up with this releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Ideally though, this won’t be an area that needs great attention for this month’s work.

Follow along:

You can follow the remaining items for 5.5 here.

Global Styles & Editor focused APIs

As a reminder, Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. Last month, this was a smaller focus but, with 5.5 shipping in August, more time will be spent building out the Global Styles system and editor focused APIs. Some of this work will include the following:

Adding support for themes to control the editor in a global context.
Adding a global styles sidebar so users can begin to tweak styles.
Exploring further APIs specific to controlling the editor.

Follow along:

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

WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Screen

As part of expanding 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 to other screens in the adminadmin (and super admin), work slowly but surely continues to improve the widget screen as part of a wider effort to add more block enabled sections to the WordPress experience. You can find initial ideas for what this might look like in this issue. Work will include the following:

Allowing themes to opt into the block based widgets screen.
Exploring sidebars_widgets based widget management.

Follow along:

You can follow the progress of this focus by reviewing issues with the [Feature] Widgets label.

Full Site Editing

Work on this major focus for phase 2 is ongoing and is expected to continue iterating over the next months. We’ve wrapped up the major work needed to build the technical foundation of this project and are now moving towards expanding the UX & UI:

Creating a template from scratch.
Exploring a new sidebar for navigating between FSE content.
Determining how multi-entity saving should work.

We’re watching the Theme Experiments repo as well to see how themers are attempting to build block-based themes. Thank you to everyone participating there as it’s a super useful way for us to determine prioritization.

Follow along:

The high level, important tasks have been split into sections and highlighted on this overview issue. If you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more.

Navigation Screen

As a reminder, those who have been working on a new, block-based, menus page (nav-menus.php) in wp-admin are running a weekly chat in #core to begin better syncing up efforts. The meeting happens in #core every Wednesday at 7AM UTC. These meetings will be focused on triaging issues in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ with the [Feature] Navigation screen or [Block] Navigation labels but are also open for discussing improving the navigation creation process in WordPress, increasing compatibility with Full Site Editing, and maintaining backward compatibility.

If this interests you, check out the following issues to join the discussion:

Sharing ideas for solving nesting in horizontally constrained spaces.
Sharing ideas for drag and drop in the navigation block on the navigation screen.
Building out navigator drag and drop.
Exploring in-toolbar link editing.
Figuring out how best to render inner blocks.

Follow along:

You can follow the progress of this project on this project board, review the overview issues (Block Navigation, Navigation Screen) & join the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat.

Areas to be aware of:

Block & PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developers

The Block Directory is coming to WordPress 5.5 and to help get ready @tellyworth shared this post discussing proposed guidelines and the following resources:

Block Creation tutorial that teaches you how to write a block plugin.
Block Submission tutorial that gives some tips and suggestions for ensuring your block is ready for the Block Directory.
Block Checker tool which will help you discover any issues that might prevent your plugin from working.

The Gutenberg Times covered this new feature in a comprehensive article that includes historical information to help understand what this might unlock for the community.

Theme Developers

@poena wrote an extensive block-based theme tutorial to help others get started with building their own.

Ways to Help:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

#core-editor #gutenberg-next

Paal Joachim Romdahl 1:50 pm on July 28, 2020
Tags: agenda ( 485 ), core-editor, core-editor-agenda ( 22 )

Editor Chat Agenda: 29 July, 2020

Facilitator and notetaker @ajitbohra.

This is the agenda for the weekly editor chat scheduled for 2020-07-29 1 4 :00 UTC.

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

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

Miguel Fonseca 8:43 pm on July 22, 2020
Tags: core-editor, editor ( 156 ), gutenberg-new ( 72 )

What’s new in Gutenberg (July 22)

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 has been released. Keeping with our July focuses, we’ve been working hard to get ready for WordPress 5.5 while continuing to ship various enhancements to continue to expand Gutenberg. In particular, this releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. focuses on local UIUI User interface improvements, performance improvements, and 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. As part of this work, some of these fixes have made their way to 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. 3.

Cover 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. video position controls

The positioning of video backgrounds in the Cover block can now be adjusted. Previously, these positioning controls were available only to image backgrounds. The focal point picker and the input controls support cursor and keyboard interaction alike.

8.6 🇯🇲