This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 1st July 2020 held in Slack. Moderated by @andraganescu.
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.4.0
Gutenberg version 8.4.0 was released.
A huge thank you to @noisysocks for helping for tackling the huge release.
Here is the nice release post. It was a packed release with the Image Editing as highlight.
@ellatrix is maintaining a project board for 5.5 of issues/PRs that need to go into the next release.
Monday Gutenberg 8.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). will be released, which is the last Gutenberg release going into WP 5.5, so all features and enhancements that need to go in WP 5.5 must be (ready) in this release. After that, we ideally only 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. regressions or limited 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. fixes for new things.
It’s also time to start thinking about dev notes 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, and 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.. Anybody can help by writing a dev 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, and 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 any of these features doing their best to cover:
- explaining the change
- why it was done
- and, if it’s an impacting change, how to update the third-party code
The monthly plan for June. A plan for July is in the works by @annezazu
My PR to move reusable blocks to their own tab in the inserter is nearly ready, but there is one remaining end-to-end test failure that I need help to resolve. Remember, this is on the WP 5.5 must-have list: PR:23296
I’ve made some great improvements to the Heading 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. heading level checker PR. If feedback is positive, it should be good to merge: PR:22650
I have a PR to add color controls to the List block. A lot of users have asked for this feature, and some contributors have suggested that we get this in soon for WP 5.5. However, there are some big editor style conflicts that I think need resolving first. I need help to get this one to progress any further. Once it is resolved, it will open the door to other list-based blocks getting color controls: PR:21387
My PR to lighten the editor DOM of the Buttons block is still stuck. I need technical help to resolve it. I consider this PR vital to fixing the current confusing/broken state of the Buttons block’s alignment controls. My plans to fix the block rely on this initial task being completed first. I would really like to get this done before WP 5.5: PR:23222
I have a PR to polish the Custom HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block which needs design feedback and a code review: PR: 21711
I have a PR to update several usages of Lodash.includes to the vanilla Array.prototype.includes. I’ve double and triple checked this PR to avoid errors. All I need is a review before I can merge: PR: 21063
While rebasing that PR, I discovered a bug in a unit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. which I have fixed in a separate PR that needs a review: PR: 23599
My PR to convert ReusableBlockEditPanel to a function component and add type info is still waiting for reviews: PR: 21181
I have a PR to convert PostSavedState to a functional component. It also awaits reviews: PR: 23038
I’m backporting changes to WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. from Gutenberg and helping in general to have everything sorted out for beta 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
I’d love eyes on this one, which tightens up the sidebar 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. controls: PR: 23578
I’ve been continuing work with the image editor. I have two open bug fix PRs: WordPress/gutenberg#23432 and WordPress/gutenberg#23569 (which also paves the way for re-adding flip controls) which could use review. And I simplified the scope of my batch 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. PR mentioned last week WordPress/gutenberg#23369. If we intend to release the API not under an experimental flag, I’d like to get this change into 5.5 since I think it’s a much nicer API to use.
I’ve been testing in Full Site Editing and reviewing docs for the Block Directory
I’ve been helping with designing flows for template creation in FSE, and reviewing/testing PRs for 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) and design. Also started looking into updating .org Gutenberg preview
I’ve worked on merged PR that adds unlink support in Buttons Block PR: 23445
PR for enabling add row/column in Table block, after having added one — needs review PR: 23508
I have a PR for allowing the Pullquote to have the same transforms with Quote block — needs review PR: 23562
I’m focusing on 5.5 to help review and test where needed.
- I’ve worked on our CI setup and used Github 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/ Actions instead of Travis.
- I’ve been working on the iterations to the inserter
- Trying to help cleaning the patterns to include to Core
- I’m also working on a job to run Gutenberg e2e tests on Core to ensure the editor is stable on Core too: PR: 356
- Reviewing different PRs here and there
I am helping to get the dev environment tips and tricks in place to help any user for migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to various node and npm versions.
We’re working on flows to create new templates and would love your feedback on initial needs/ideas here.
For those that use the WordPress Figma libraries, updates are on the way to incorporate the new block editor patterns, as well as some general cleaning to make these more relevant. In the Components and Patterns files, there’s a page called “In Progress” where I’m building out the new elements. Once those are approved, we’ll migrate them to the main pages.
Arpit G Shah
How can we manage to work with the new contributors?
Myself and a bunch of other folks who have been working on a new, block-based, menus page (nav-menus.php) in wp-admin (and super admin) will host a weekly chat in #core every Wednesday, 2020, 07:00 AM UTC, starting next week, on Jul 8th.
In general it will be a triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. around issues in GitHub labeled with either `[Feature] Navigation screen` or `[Block] Navigation` but also completely open to exploring any subject around improving the navigation creation process in WordPress, increasing compatibility with the incoming FSE and also maintaining backwards compatibility.