This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor Slack 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 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). 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.
Gutenberg 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, Widget 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 & block 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 A11y 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.json 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 API 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 triage 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, backport 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 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 bug 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 category 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
