Tag Archives: core-editor-summary

Paal Joachim Romdahl 7:54 pm on August 11, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: 9 August, 2023

This post summarizes the weekly editor chat meeting (agenda for 9th of August meeting) held on  Wednesday, August 12 2023, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

WordPress 6.3 was released on the 8th of August.
Gutenberg 16.4 RC1 is available for testing.
Final version of 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/ 16.4 will be released Wednesday.
A big thank you to @mikachan for handling the 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 release.
Sarah is using this checklist.

Key project updates:

@mikachan

The WebFonts 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. – work is currently underway on the new Font Library. The initial Fonts Library: Backend PR is currently being worked on, and there are more related issues in [Tracking] Fonts Library. Stage 1: Google and Local fonts. It would be great to get more reviews on the backend PR, and also some more input on this discussion about where to store the list of Google Fonts. Thanks!

Task Coordination

@get_dave

I’m working on 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) enhancements around the 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. to try and address some outstanding concerns. Also exploring ways to improve the responsive layout of the Navigation block. Still at the thinking/exploration phase. Also re-focusing a bit on allowing custom labels for items in List View.

Open Floor

@andreiglingeanu

I’m Andrei, I’m one of the developers of the Blocksy theme.
Question: is there way to bypass namespacing the styles for some of the $styles from the editor settings?
From the discussion that happened a new issue was created:
Allow inserting un-namespaced editor styles into the iframe.

@proxxim

I wonder if it might be possible to shine some light on this discussion: 
Query Block doesn’t seem to provide settings to a Post Template in a pattern/template-part
I tried to use synced patterns in the Post Template block but there seems to be a disconnect on the front-end as long as it’s a pattern.
I registered some block variations for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./button block and added isDefault: true to one of them, but when adding a new core/buttons block in the editor that variation is not used as the inserted button.
Issue created here: core/buttons does not respect isDefault for core/button variation.
Here is an associated issue: core/button variations doesn’t appear in core/buttons inserter. 

Read complete transcript

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

Fabian Kägy 7:04 pm on August 7, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: August 2nd, 2023

This post summarizes the weekly editor chat meeting (agenda for August 2nd meeting) held on Wednesday, August 2nd 2023, 03:00 PM GMT+1 in Slack. Moderated by @fabiankaegy.

WordPress 6.3 RC3 was released and is available for testing. 6.3 itself will be released on August 8th. @priethor shared a great summary about the release day process. This is the perfect time to do some last-minute testing to help ensure the launch goes as smoothly as possible.

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/ 16.4 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). was released after the meeting ended. It’s available to test through GitHub.

Gutenberg 16.3 was released last week and the full changelog was posted here in the Make blog.

Key project updates

Open Floor

@isabel_brison shared a proposal they had published a few days earlier to improve the editor side of the release process. Any feedback on that would be very much appreciated.

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

David Smith 4:59 pm on July 26, 2023
Tags: , core-editor-summary, , , ,   

Core Editor chat summary: 26th July 2023

This post summarises the weekly editor chat meeting (agenda for 26th July meeting) held on 2023-07-26 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

Updates based on updated scope for site editing projects

Task Coordination

I was a quiet meeting…

@get_dave:

Open Floor

There we no topics raised for discussion.

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

Jorge Costa 10:55 am on July 24, 2023
Tags: , core-editor-summary, , , ,   

Editor chat summary: Wednesday, July 19, 2023

This post summarizes the weekly editor chat meeting on Wednesday, 19 July 2023, 14:00 UTC, held in Slack.

Announcements

WordPress 6.3 RC1 was released on July 18. @jorgefilipecosta congratulated everyone that participated in the release.

Key project updates

There were no updates for the key projects shared during the meeting.

Task coordination

@jorgefilipecosta

Open floor

There were no topics of discussion raised on the open floor,

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

Paal Joachim Romdahl 8:10 pm on July 14, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: 12 July, 2023

This post summarizes the weekly editor chat meeting (agenda for 12th of July meeting) held on  Wednesday, July 12 2023, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

Help test WordPress 6.3 Beta 4.
What’s new in Gutenberg 16.1? (June 29)
Gutenberg 16.2 RC3 is available for testing.
Final version of 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/ 16.2 will be released Wednesday.

Key project updates:

No updates of Key Projects during the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor meeting.

Task Coordination

@mamaduka

I’m going through the 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. reports from WP 6.3 board, checking what we can fix.

@hellofromtonya

The 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. is being replaced by Font Face to support the new Font Library. Font Face has been merged into trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. but will only load into memory when Font Library is available. Making all aware that the new approach no longer includes register or enqueue of fonts, as plugins will integrate into the Font Library instead. And Font Face becomes read only of theme.jsonJSON 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. merged data, which will eliminate issues with what fonts appear in typography pickers.

This work is very low level. The new Font Face will not impact the UIUI User interface directly. Indirectly, its impact is on printing the font-face CSSCSS Cascading Style Sheets. so that fonts visually look correctly, ie use their font files to render properly. That CSS generator and printer role though has not changed from the Fonts API. What has changed? Where plugins introduce their fonts for user consideration and selection. That role moves to the Font Library.

Open Floor

@hellofromtonya

FYI: Fonts API will not get replaced until the Font Library is introduced. And this work is not being introduced into WP 6.3, as it’s still experimental.

WP 6.3 is dropping PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 5.6 support, raising the minimum supported version to 7.0.
Gutenberg though needs to run on the last 2 WP major releases, meaning it can’t yet drop PHP 5.6 support.
The 2 PHP 5.6 PHPUnit CI jobs running on WordPress trunk have been removed from Gutenberg. Why? They were failing because Core no longer runs on PHP 5.6.

  • Update your PRs if they are failing for PHP 5.6 CI jobs.
  • When to drop PHP 5.6 support.

Discussion is here: Increase the PHP minimum supported version to 7.0

@skorasaurus

As I low-level contributor and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. member, there were some suggestions within the past couple months ( i think here or in make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ comments), that a release be devoted primarily to bug cleanup.

I’d just like to suggest that again… as a triager, I’m aware that some 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. editor issues 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/ can be closed when new features are introduced but there are nearly 1,000 PRs (yes, some of them are drafts and probably be disregarded) but I imagine fellow contributors recognize the frustration of keeping up with PRs and searching through issues when they’ve already been reported.

A suggested label to go through. Open Gutenberg PR’s with no one to review these.

@mamaduka

Maybe we can keep track some of those PRs in separate board. Bug fixes are usually easier to review, unless they rewrite the whole editor

Read complete transcript

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

Andrei Draganescu 3:10 pm on July 5, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: July 5th, 2023

This post summarizes the weekly editor chat meeting (agenda for July 5th meeting) held on Wednesday, July 5th 2023, 03:00 PM GMT in Slack. Moderated by @andraganescu.

Announcements

  1. WordPress 6.3 Beta 3 is out.
  2. With 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. 3 already live, we are two weeks away from RC1 and the incoming string freeze. Please be aware that:
    • Soft string happens during Beta 4; it’s the last chance to add new strings.
    • Hard string freeze happens during RC1; no strings can be edited after this.
  3. A series of posts on phase 3 of the 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/ project has been started by @matias The 1st three installations are:

with more to come. You can check the progress by looking at the tag. 

Key project updates

Open Floor

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

Fabian Kägy 8:08 am on July 3, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: June 28th, 2023

This post summarizes the weekly editor chat meeting (agenda for June 28th meeting) held on Wednesday, June 28th 2023, 03:00 PM GMT+1 in Slack. Moderated by @fabiankaegy.

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/ 16.1 was released. You can find out all the new things in the Whats new in Gutenberg 16.1 post.

WordPress 6.3 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. 12. was released with a small delay due to an issue with how minified styles were getting generated. You learn more about how to help pest this release via the news article published about it.

Key project updates

Open Floor

@smrubenstein raised a PR they created that aims to stabilize the __experimentalDefaultBlock API of the Navigation Block. The PR is currently waiting for a review.

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

Fabian Kägy 7:40 am on June 22, 2023
Tags: , core-editor-summary, , ,   

Editor chat summary: June 21st, 2023

This post summarizes the weekly editor chat meeting (agenda for June 21st meeting) held on Wednesday, June 21st 2023, 03:00 PM GMT+1 in Slack. Moderated by @fabiankaegy.

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/ 16.1 RC1 will be released later today. 16.0 was released last week alongside the regular Whats new in Gutenberg post.

WordPress 6.3 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. 1 will be released in less than a week on Tuesday, June 27th. A good overview of the various tasks still in progress can be found in the WordPress 6.3 Editor Tasks Project on GitHub.

Even though the release of the beta is happening one day before the public release of Gutenberg 16.1 the plan is still to include all the features up until 16.1 in WordPress 6.3.

Key project updates

Open Floor

@tjnowell raised a PR that fixes an issue with CSS @container queries break editor styles getting loaded via add_editor_style. The PR is currently waiting for a review.

@aurooba shared the discussion currently happening about finding a new name for the “Command Center”. We also had a discussion about how a decision gets made in these cases. If you have thoughts about the name, please add your thoughts to the ticketticket Created for both bug reports and feature development on the bug tracker..

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

Birgit Pauli-Haack 3:22 pm on June 16, 2023
Tags: , core-editor-summary, , ,   

Editor Chat Summary: 14 June 2023

This post summarized the editor chat from  Wednesday, June 14, 2023, 14:00 UTC (agenda) held in the #core-editor channel moderated by @bph – Full transcript

Announcements

  • Gutenberg 16.0 is now available for download from the plugins repository. Release leadRelease Lead The community member ultimately responsible for the Release., Nick Diego published the release post What’s new in Gutenberg 16.0? (14 June)
  • WordPress 6.3 is less than two weeks away from 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. 1 (June 27) This is the second to last 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/ release, and it needs lots of testing.
  • The FSE Call for testing 24 is a great way to learn about the new features and at the same time provide feedback before the beta releases, deadline for comments is June 28

New Developer Blogblog (versus network, site) posts

Project updates

Task Coordination

@Leonardus Nugraha, 6.3 release squad docs team,

published the Dev Notes tracking issue for WordPress 6.3. It’s the first time, Leo is working on this, so he definitely requires your help finding all the PRs that would need a dev notedev 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..

@ndiego 6.3 Editor Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. release squad
If anyone is looking to contribute and work on an issue, the items on the Editor Tasks for 6.3 board are the most important for 6.3

Open Floor

@bernhard-reiter

This is more of an early pre-announcement, but @fullofcaffeine has been working on a PR that will enable us to publish a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for a previous version series even if a new stable release has already been published. (E.g. if the current Gutenberg version is 15.9.1, and we discover a serious 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. in 15.8.1, the changeset will allow us to publish a 15.8.2 release with a bugfix.) Since it is a somewhat substantial change to the release GHA workflow, we’re planning to land it only after GB 16.1 has been published, in order not to interfere with WP 6.3. We’re currently targetting July 5 (see). Here’s some more info shared by @fullofcaffeine.

@Hanzala 

“[I] missed last few meetings due to some work stuff but it feels good to finally join today’s meeting. Hope to contribute on some task in a coordinated way. just wanted to share that”.

Birgit: “It’s good to have you join us today and we are all looking forward to your contributions. Bangladesh and WPDeveloper have been contributing quite a lot lately  Especially for 6.2. Thank you!

Hanzala: “Yeah many people are really interested. Hope we can find some impactful contributors.”

Props to @paaljoachim for review.

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

David Smith 2:41 pm on June 7, 2023
Tags: , core-editor-summary, ,   

Core Editor chat summary: 7th June 2023

This post summarises the weekly editor chat meeting (agenda for 7th June meeting) held on 2023-06-07 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

  • Gutenberg 15.9.1 is the latest release following on from 15.9.0.
  • The 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). wasn’t released yet.
  • Check out the Issue for backporting the PHP changes from the Plugin for the WordPress 6.3 release. Please check whether you’ve received a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” and if you have please take time to help get your changes ready.

Updates based on updated scope for site editing projects

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@ndiego:

  • Currently working on the release process for 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/ 16.0 RC1 and part of that is going through all of the PRs attached to the milestone to make sure each has a [Type] ... label. These are used to auto-generate the changelog.
  • Wanted to request that when folks create/review a PR, to please make sure they add a type label (i.e. [Type] Bug, [Type] Enhancement etc.).
  • Focusing on the Contributor Guide sections of the 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. Editor Handbook. The goal is to get each page updated and accurate as well as adding missing info.

@get_dave:

  • I been working on several PRs relating to the work underway to refresh and improve the core LinkControl component.
  • Adding focus mode for Navigation Menus as part of work to add Navigation section to the Browse Mode sidebarSidebar 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..

Open Floor

It was a quiet meeting due to WCEU…

New Contributor review requests

#core-editor, #core-editor-summary, #meeting, #summary