Editor chat summary: 1 May 2019

This post summarizes for the weekly editor chat meeting on Wednesday, 1st May 2019, 13: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/ 5.6

The release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). was published Monday. No issues have been reported in the interim. The process for publishing the final release to 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 repository begins today (done). A pull request for the version bump was opened, in case anyone would be so kind as to grant me an approval.


WPCampus finished the final report of the Gutenberg 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) audit as of last night. After finishing communications prep, it will be release (done!).  This is a third-party report; additional context can be found here.  The report hasn’t yet been published, but there’s already a number of issues opened in the repository resulting from this audit. While immediate attention could help knock out basic issues, it may be wise to coordinate a joint meeting with the #accessibility team to view the report and identify next steps. The main takeaways are:

  1. – The GB team wants to make a concerted effort at addressing issues exposed by the audit
  2. – We’d like the accessibility team to help point our efforts in the right direction.

The GB team are unanimous is taking a dedicated timeframe to concentrate on the issues specifically reported in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ would which will provide the ability to make a significant contribution in a short amount of time. @getDave will attend this week’s #accessibility team meeting on 3 May at 15:00 UTC to connect with the team.

The ability to group multiple blocks together is in development Screencast here. Assistance is requested to test the UXUX User experience and expert guidance on writing suitable tests to cover the new logic.

Progress is being made migrating the Gutenberg handbook into DevHub (developer.wordpress.org)  https://github.com/WordPress/gutenberg/pull/15254This will be a staged approach where we generate two manifests for a short time, put redirects in place on the legacy handbook, then ultimately go back down to a single manifest. Once the initial work has been done we can look at further restructuring or other improvements,

Task Coordination

  • @nerrad is finishing work on refactoring effects as controls, and plans to start working on a new package to expose common controls.
  • @aduth has proposed improvements to documentation and build times, and is working to enhance the Column 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 add resizable controls.
  • @getdave is continuing to work on a method to convert a selection of multiple blocks to a “Group” block.
  • @andraganescu is refactoring media blocks to have a consistent replacement flow and plans to attend the accessibility meeting.
  • @jorgefilipecosta has shared an early prototype that connects the widgets screen to new widgets endpoints (related to the Widgets RFC).

Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.

The agenda for the next meeting, 8 May 2019 13:00 UTC is here, please add anything you want to discuss.#meeting-notes, #core-editor, #editor, #gutenberg