Adam Zieliński 4:32 pm on August 19, 2022
Tags: , , , ,   

Editor chat summary: 17 August, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-08-17 14:00 UTC. in Slack. Moderated by @zieladam.

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

Key project updates

Key project updates:

Task Coordination

@paaljoachim

@zieladam

  • Here’s what I’ve been up to:
  • WP_HTML_Walker – a reliable way to update the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 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. markup from PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher, forget about regexps. An official make coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) proposal is coming soon!
  • I published the proposal to Stop merging experimental APIs from the Gutenberg plugin to WordPress core
  • I’m transforming the Create your First App with Gutenberg Data tutorial into a course on learn.wordpress.org!

@oandregal

  • I’m getting back into the swing of things, so a lot of catchup. Helped with the gutenberg release and I’m ramping up to help in the area of “locking a pattern” (Add: Content lock ability started by JorgeCosta).

Open Floor

Announcements, questions and discussions.

@ndiego

There was previously some concern around adding Font Family support to more blocks since the Web Fonts 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. was still being finalized. Given this recent tracking ticket and all the associated PRs, I’m assuming that are good to move forward with full typography support across blocks? 

A reply from @hellofromtonya

  • The Webfonts API is still in development, yes. This is true. It’s entire architecture is being changed. However, the API itself as it is in Gutenberg works. The issue of using these enqueued / selected fonts within blocks though is outside the scope of the API itself. What do I mean by that? Right now, any block level interface could get the fonts from the API. That functionality exists now in Gutenberg.
  • For WP 6.1, it’s highly likely the Webfonts API will not be ready.

See the full conversation on Slack.

@priethor

The WordPress 6.1 feature freeze is scheduled for September 20th (Tuesday), and the Gutenberg 14.2 RCrelease 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). is planned for Sept 21st. It has been common in past releases to arrange the last pre-freeze RC to align with the Feature Freeze, so I was thinking of moving the Gutenberg 14.2 RC1 one day earlier to align with the WP 6.1 Feature Freeze. There are mainly three options for the feature freeze:

  • Make 14.1 the last version included; effective feature freeze on Sept 7th, 13 days of buffer time until WP 6.1 FF.
  • Make the 14.1 cycle one week longer; effective FF on September 14th, 6 days of buffer time.
  • Make 14.2 the last version, but shorten the RC period, with the 14.2 RC1 and effective feature freeze on September 15-16th.

The last two options are very similar, but I would prefer the last one (making 14.2 RC shorter) so that we avoid altering the biweekly release cycles/dates.

See the full conversation on Slack.

@hellofromtonya

PHPUnit tests > to help reduce backporting effort, I’m working on bringing parity between Core’s and Gutenberg’s PHPUnit testing. For example:

  • Turning on and testing of PHP notices and deprecations > which means source code may need adjustment to get rid of these errors
  • Running the tests against all PHP supported versions to ensure there are no incompatibilities

Why? Tests will fail in Core when backported. So catching issues early and continuously throughout the development cycle will help to ensure the PHP side of things is Core commit ready.

To get more details go directly to the Open Floor discussions 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.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary