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