What’s new in Gutenberg (8 july)

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/ 8.5 has been released. 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 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. that is going to be included entirely (without experimental features) in WordPress 5.5.

Drag and Drop

Since its first introduction, the experience of drag and dropping blocks to reorder them has stayed almost untouched. This release includes several iterations to improve on this interaction. Drag and drop supports vertical reordering more clearly, it replaces the cloned element with a nice little drag chip and smooth the scroll-on-drag behavior.

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) improvements

One important addition in this release is the possibility to disable arrow navigation across blocks. While writing long form content, it’s very important to be able to navigate using arrow keys between blocks, this can be confusing for screen reader users. We now have an option to disable that behavior.

Easy upload for external images.

Another workflow people use while writing is to rely on external tools to write or collaborate on their posts and when ready, copy/paste these into 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.

The downside is that any external images used there are hosted elsewhere and may not always persist. In this release, if an image block is using an external images, you’ll have the possibility to upload it to the media library while keeping it as is on the post with a single click.

8.5 🇸🇪

Features

  • A11yAccessibility 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): Add an option to keep the caret inside blocks in edit mode. (23546)
  • Add anchor/id support to all static blocks. (23197)

Enhancements

  • Add an edit button to the gallery images. (23554)
  • Image block: Allow uploading external image if image host allows it. (23565)
  • Drag And Drop:
    • Enable for multi selection. (23477)
    • Improve the drag and scroll behavior. (23082) (23448)
    • Don’t show a cloned block while dragging. (23024)
    • Polish the block drag chip. (23609)
  • Image editing:
    • Move zoom control to toolbar dropdown. (23677)
    • Add original aspect to dropdown. (23659)
    • Add filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to REST APIREST 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/. image edit. (23539)
    • Polish zoom slider. (23418)
    • Add permission checks to the endpoint. (23423)
  • Block Directory:
    • Return inactive plugins in search results. (23688)
    • Use CDN for block directory assets. (23499)
  • Add line height rule to the post title. (23656)
  • Avoid ordering block types per frecency inside block categories. (23643)
  • Polish the document 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. controls. (23578)
  • Add modern color scheme support. (23558)
  • Use a consistent close icon across the UIUI User interface. (23551)
  • Redesign the transform menu. (23028) (23449)
  • Redesign the canvas inserter. (22789)
  • Unify tooltip styles. (23382)
  • Add block variations to the slash inserter. (23364)
  • Hide the most used blocks by default and add an option to enable it. (23358)
  • Add reusable block tab to inserter. (23296)
  • Add keyboard shortcuts for moving blocks. (23276)
  • Cover block: Don’t show the matrix alignment button when no background set. (23196)
  • Spacer: Show tooltip with height value on resize. (23077)
  • Improve post publish buttons alignment. (22390) (23487)
  • 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). Preview and Save Draft buttons use the same style. (21192)
  • Add unlink URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to buttons block. (23445)
  • Clean the patterns list to include in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. (23608)
  • Add pullquote block tranformations. (23562)
  • Remove block label from child block appender. (23393)
  • A11y: Move blocks between levels using keyboard. (22453)

New APIs

  • Support orientation prop in InnerBlocks. (23416)
  • Support a flexible useItems 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. for the autocompleters API. (22853) (23385)
  • Stabilize the image editing REST API endpoint. (23536)
  • Stabilize the block directory REST API endpoint. (23528)
  • Add descriptions to Block patterns. (23070)

Experiments

  • Sitesite (versus network, blog) Builder:
    • Remove the button block appender. (23436)
    • Improve the template parts insertion flow. (23295)
    • Fix template part resolution for edited files. (23591)
    • Fix inspector panels buttons. (23464)
    • Add template part block keyword. (23623)
    • Allow wide alignment. (23488)
    • Remove templateIds state. (22893)
  • Navigation screen and block:
    • Fix saving issues. (23559)
    • A11y: Improve keyboard navigation on the Navigation block toolbar. (23281)
    • Fix text size no longer overwritten. (23360)
    • Adjust Navigation block submenu padding and spacing. (23380)
    • Update placeholder label. (23297)
    • Hide the block toolbar on the navigation screen. (23021)
    • Allow setting up menus that auto add new pages. (22697)
    • Allow Search block to be added alongside links. (22656)

Bug Fixes

  • Block Directory:
    • Support .svg extension for results icons. (23442)
    • Throw error if we have an issue registering blocks. (23439)
    • Remove the overflow on the Add button. (23409)
    • Fix double border in block list. (23625)
  • Fix the upload icon size. (23553)
  • Allow scrolling over Popovers. (23696)
  • Fix quote left border color in dark mode. (23692)
  • Fix empty block list appender visibility on aligned blocks. (23672)
  • Fix horizontal Block Mover Layout. (23640)
  • Fix invisible drop target indicator. (23638)
  • Rich text: Fix soft line break in caption on enter. (23622)
  • Fix clicking Gallery items buttons on Safari. (23586)
  • Hide block list appender in a reusable block if it’s not being edited. (23584)
  • Revert “Remove the style CSSCSS Cascading Style Sheets. class when the default style variation is chosen”. (23548)
  • Classic block:
    • Add height: Auto to content wrapper. (23547)
    • Add scroll to last edit position. (23544)
    • Adjust placement of the toolbar. (23438)
    • Prevent content loss by regularly dispatching changes. (23408)
    • Fix undo keyboard shortcut. (23376)
  • Fix the Gallery images buttons rendering. (23471)
  • Fix Post title top margin. (23447)
  • Fix file names generation for edited image files. (23440)
  • Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. warning when cropping imùges. (23432)
  • Polish block moving animation. (23401) (22640)
  • Fix small RTL regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in Buttons block. (23390)
  • Fix centered legacy button. (23381)
  • Fix React warning while unmounting slots. (23365)
  • Don’t show the “Move to trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days.” action if the user is not allowed to delete posts. (23174)
  • add inline font-sizes and colors to the editor for themes that don’t enqueue the preset classes. (22356) (22668) (23717)
  • Create Block: Fix missing scripts section in scaffolded package.json. (23443)
  • Scripts: Fix build script with style.css files. (23710)
  • Restore removed props and behavior back to Query Controls. (23419)
  • Add support for hexadecimal colors in gradient presets. (23363)

Performance

  • Improve the performance of the keyboard shortcuts binding. (23394)

Documentation

  • Add a documentation page explaining how the repository is organized. (23563)
  • Document the WordPress 5.5 backported code. (23478) (23708)
  • Add .markdownlint.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. configuration extending scripts configuration. (23655)
  • Add “Create a Block” tutorial Create a Block tutorial. (22831) (23654)
  • Update wp-env Ubuntu documentation. (23650)
  • Add documentation for InnerBlocks orientation prop. (23641)
  • Remove DropZone position argument from documentation to reflect removal in WordPress 5.4. (23577)
  • Update categories in block registration documentation. (23572)
  • Update ESNext usage in public API. (23475)
  • Clarify the wp-block-styles documentation. (23359)
  • Add documentation for setting up Prettier for markdown. (23286)
  • Typos and tweaks: (23542) (23489) (23590) (23300) (23534) (23467)

Code Quality

  • Optimize useSelect calls (dependencies) (23255) (23247) (23245) (23249)
  • Reduced the number of SASS color variables. (23648) (23454)
  • Remove unused getBlockIndex selector from useBlockDropZone hook. (23634)
  • Scroll on drag: Remove blockNodes context dependency. (23561)
  • Add missing notices dependency. (23517)
  • Remove BlockPopover key prop and related code. (23504)
  • Show a warning when SlotFillProvider is missing. (23493)
  • Block toolbar: Remove data-align attribute. (23468)
  • Extract block draggable scroll behaviour into React hook. (23444)
  • Refactor Dropdown to use functional component. (23142)
  • Refactor Embed Edit component: Class component to Function component. (22846)
  • Extract navigation link rendering code from the navigation block. (21075)
  • Block editor: Use vanilla JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. instead of Lodash if possible. (21063) (23633)
  • Add “engines” to the package.json and “engine-strict = true” to the package.json. (23600)
  • Block Directory: Remove custom permission check in favor of canUser. (23624)
  • Remove REST_WP_REST_Block_Types_Controller_Test which now exists in WordPress Core. (23500)
  • Editor: Remove unnecessary block directory dependency. (23476)
  • Plugin Controller: Return the plugin without the extension. (23395)
  • Clean up image editor REST route. (23368)
  • Make slash inserter tests more stable. (23367)
  • Post Author block: Fix end-to-end test fixture indentation. (23209)

Build Tooling

  • Add new command for pre-releasing npm packages. (23357)
  • Move the CI setup from Travis to 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. (23523) (23520) (23518) (23470) (23538)
  • Add npm cache to Github workflows and use checkout v2. (23482)
  • Update bin/validate-package-lock.js error message. (23435)
  • Minor improvements to the release tool and release documentation. (23441)
  • Tools: Always append prerelease to version update in package.json when preparing npm release. (23480)
  • Scripts: Add custom TerserPlugin configuration. (22990)
  • Scripts: Exclude node_modules from source map processing in start script. (23711)
  • Fix rc version number added to the CHANGELOG. (23433)
  • Tests: Jest – Add typeahead plugin. (23366)
  • Tests: Run end-to-end tests only as an adminadmin (and super admin). (23588)
  • End-2-end Tests: Add test for using block variation with the slash inserter. (23585)

Various

  • RangeControl: Integrate NumberControl + update internal state flow. (23006)
  • Create Block: Generate a block.json file. (23399)
  • Sync Block Context changes from Core. (23602)
  • Scripts: Remove default exclude rule for node_modules for SVG, CSS and Sass files. (23495)
  • REST API: Sync /themes endpoint with Core’s. (23321)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version Loading Time KeyPress Event (typing)
Gutenberg 8.5 6.86 s 27.84 ms
Gutenberg 8.4 7.22 s 27.85 ms
WordPress 5.4 8.91 s 40.52 ms

Kudos for all the contributors that helped with the release. 👏

#core-editor, #editor, #gutenberg-new

What’s next in Gutenberg? (July)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for July. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Sitesite (versus network, blog) Editing project. 

Preparing for WordPress 5.5

On July 6th, Gutenberg 8.5 RC is planned to be released! This is the last 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. going into WordPress 5.5 and is the major focus for this month so 5.5 can be set up for success. Keep in mind that this means that all features and enhancements that need to go into WordPress 5.5 must be ready for this upcoming release. After the 8.5 release, ideally only fixes for regressions or fixes for bugs in new features will be added in. You can read the latest news about what editor features are planned for inclusion in 5.5 here.

Follow along:

You can follow the progress for this effort on this project board.

Full Site Editing

Work on this major focus for phase 2 is ongoing and is expected to continue iterating over the next months. We’ve wrapped up the major work needed to build the technical foundation of this project and are now moving towards expanding the UX & UI:

  • Refining and pruning block patterns.
  • Refining 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. and navigation screen.
  • Building out flows for new template creation.
  • Improving the flow for inserting new or selecting existing template parts, currently being explored as “sections” in the block editor. The exact naming is being discussed further here.

We’re watching the Theme Experiments repo as well to see how themers are attempting to build block-based themes. Thank you to everyone participating there as it’s a super useful way for us to determine prioritization. 

Follow along:

The high level, important tasks have been split into sections and highlighted on this overview issue. If you’re interested in being a part of testing Full Site Editing, check out the experimental outreach program to learn more

Navigation Screen

As @andraganescu mentioned here, those who have been working on a new, block-based, menus page (nav-menus.php) in wp-adminadmin (and super admin) are starting a new weekly chat in #core to begin better syncing up efforts. The meeting will happen in #core every Wednesday, July 8, 2020, 01:00 AM MDT, starting next week, on July 8th. These meetings will be focused on triaging issues in 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/ with the  [Feature] Navigation screen or [Block] Navigation labels but are also open for discussing improving the navigation creation process in WordPress, increasing compatibility with Full Site Editing, and maintaining backward compatibility.

To help get everyone thinking more about navigation, check out the following related issues that are currently being explored:

Follow along:

You can follow the progress of this project on this project board, review the overview issues (Block Navigation, Navigation Screen), and join the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat.

Miscellaneous Focuses

Because preparing for 5.5 is such an important piece of this month to get right, the items below are still focuses but are more minor than they have been these last few months. Once work for 5.5 is in a solid place, it’s expected that greater attention will return to these areas:

Global Styles

As a reminder, Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. You can follow the progress for this overall system in this overview issue. For more recent and immediate next steps, you can follow this issue describing the current state of work. 

WidgetWidget 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

As part of expanding the block editor to other screens in the admin, work slowly but surely continues to improve the widget screen. You can follow the progress of this focus by reviewing issues with the [Feature] Widgets label.

Areas to be aware of:

Block & 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 Developers

There is a new block creation tutorial done by @mkaz in light of the block directory’s experimental status being removed. Expect new block guidelines, more documentation, and a  block validator tool coming your way this month. For now, anything that can be done to test the block directory and give feedback would be greatly appreciated 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). this a success. 

Theme Developers

Last week, an awesome Q&A from the Gutenberg Times (hat tip @bph) was done on block-based themes featuring @itsjusteileen @kjellr. You can see some pretty neat demos in there including the theme export button. If you’re curious about or working on block based themes, check out the recorded discussion.

Ways to Help:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. If there’s anything we can do to make contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

#core-editor #gutenberg-next

Editor features for WordPress 5.5 – update

As a continuation of the previous post outlining the WordPress 5.5 Editor features, here’s an update on which of those features will be in 5.5, and which will not. In the previous post, there were two “sets” of features. The first was “definite for inclusion,” and the second was “features that need help.”

Currently the 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. includes the following list of new additions and improvements to the editor:

  • A new 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 design.
  • Introducing block patterns and the block patterns APIs for themes and plugins.
  • A new block inserter panel with streamlined categories, collections, native support for patterns, and block directory integration.
  • An improved editing experience, with refined drag and drop, block movers, parent block selection, device previews, contextual focus highlights, multi-select formatting allowing changes to many blocks at once, ability to copy and relocate blocks easily, and better performance.
  • An expanding set of design tools with inline image editing, theme support for link color, multiple alignment options and customizable padding in cover block, mobile support for auto-playing videos, extended background and gradient support to other blocks (group, columns, media & text), broader unit control beyond pixels (rems, %, vh, vw), line height adjustments, and more.
  • Over 1500 additional changes to the editor experience.

That is an impressive list! It also includes most of the items that needed help: block patterns, block directory and block design tools. Keep an eye on this blogblog (versus network, site) in the coming weeks for 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. detailing each feature listed above.

Thank you to every contributor that took the time to push these features over the finish line! 🎉

However, even though lots of work went into these features and considerable progress was made, there are some features previously planned for 5.5 that could not be included:

  • The navigation block
  • The new navigation screen
  • The new widgets screen

To monitor progress and participate there are a few places to start:

  • Navigation and the navigation screen issues are tracked in the Navigation project within the 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/ repository. There are also issues not tracked in the project but labeled accordingly.

To test the current status of these projects, remember to turn them on within the Gutenberg plugin experiments screen.

Thank you for your support, contributions, and all other kinds of participation in this amazing new incoming WordPress release!

#5-5

Devchat meeting summary: July 1st, 2020

@whyisjake led the chat for this agenda

Highlighted/Need Feedback Blogblog (versus network, site) Posts

A few blog posts and announcements were shared by @whyisjake

@azaozz recently published a plan to update the version of jQuery that is shipped with WordPress: ‬Updating jQuery version shipped with WordPress‬‬

@sergey‬ published this proposal last week to change some of the closure statuses in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.: Proposal: Rename “invalid”, “worksforme”, and “wontfix” ticket resolutions. ‪@sergey‬‪ shared that he is waiting on more feedback and will summarize this weekend or so.‬‬

@audrasjb recently published ‬WordPress 5.5: Better fine grained control of redirect_guess_404_permalink()

@desrosj recently published External Library updates in 5.5: call for testing

What’s new in 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/

@whyisjake noted the amazing new image editing capabilities (with gifs!) : What’s new in Gutenberg (24 June)

As a follow up, ‪@Andrei‬ posted the editor chat summary earlier today: Editor chat Summary: 1st July, 2020

@whyisjake pointed out that for anyone interested in contributing to closing some 5.5 tickets, ‪@ella‬ has a 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/ board tracking issues for the net 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..

@desrosj wants help to test SimplePie and PHPMailer! All 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 authors that utilize these libraries should receive an email alert. The updates have been in 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. for at least a few weeks now, and no issues have been found yet. @ipstenu has picked it up and just needs a clone.

Upcoming Releases

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. 1 is right around the corner: WordPress 5.5 Development Cycle @whyisjake noted that from this point on, no more commits for any new enhancements or feature requests in this release cycle, only 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 and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point, and can be picked up for commit again at the start of the WordPress 5.6 development cycle.

Components Check-in and Status Updates

APAC Scrub @davidb‬‪ provided an update on the ‬APAC scrub last night. With Beta 1 approaching, the deadline for Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. type tickets is at that point.@audrasjb congratulated everyone on bringing the number down this past week. @whyisjake ‪asked what the process would look like between now and ~next Tuesday for these tickets? @davidb said ‬triaging while pinging owners/maintainers as much as possible for updates. Monday and Tuesday will probably see a lot of punting though, if these tickets don’t move between now and then‪. @whyisjake then asked if a ticketticket Created for both bug reports and feature development on the bug tracker. doesn’t see movement, do we normally move to Future Release or 5.6? @davidb said mostly Future Release with a comment that the owner/maintainer/committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. can update to the current milestone when they assume ownership to avoid the “kick the can down the road” issues of the past.@whyisjake gave major props to @davidb and everyone else that takes the time to keep the ticket garden tidy.‬‬

@francina mentioned that there has been a lot of discussion in 5.3 and 5.4 about what bug fixes can be fixed. Group asked if we should revisit or continue as we did until she finds the time to write the proposal?

@audrasjb noted that ‪#48751 was intentionally punted to 5.6 and not Future release and should be left in its current milestone‬‬

@marybaum team is on track to attach rough layout and copy for the About page to the ticket on track with Beta 1 and then commit by RC1, so polyglots can have the full period to translate. She gave props to ‪@estelaris‬, ‪@yvettesonneveld‬ and ‪@abhanonstopnewsuk‬ for art direction, help with the message brief and outreach to the marketing team.

@francina gently reminded all the component maintainers that we are 6 days away from Beta 1 and ask for help if needed.

@whyisjake provided a link for the list of components, with the maintainers: Component Pages – 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). WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@whyisjake mentioned that WordPress 5.5 introduced a new sitemap component.

@Carike mentioned that there is still a significant difficulty that some components have a large number of maintainers, while only one is currently active. It prevents people from volunteering. @francina and ‪@yvettesonneveld‬ talked about the possibility of mentoring new contributors to avoid burnout.

@Carike mentioned that one couldn’t triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets properly without maintainer status. @clorith said anyone can triage tickets, it’s also possible to have gardener capabilities without being a maintainer. @johnbillion seconded this and said maybe the status is not set on Trac @whyisjake posted the link to some docs around bug gardening: Bug Gardening @sergey also posted the link to a good overview for anyone interested in triaging/gardening @‬desros ‬has a new related post in his drafts and will try to wrap that up and get it published next week!‬

@audrasjb gave a few updates from the components he’s working on:

  • Everything is fine from Widgets and Menus components. The biggest remaining ticket is #48170 and it’s only waiting for review.
  • Everything is fine from Plugins and Themes auto-updates. We have few remaining tickets but no blockerblocker A bug which is so severe that it blocks a release..
  • From the 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) focus: we’ll start punting to Future soon. We still have two remaining bug scrubs to handle the remaining tickets.

New 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.-based menus page: @Andrei‬ and a bunch of other folks have been working on a new, block-based, menus page (nav-menus.php) and think it’s time to start syncing with everyone else on how things evolve. They will host a weekly chat in #core about the current evolution and state of the new navigation screen. The meeting will happen in #core every Wednesday, July 1, 2020, 12:00 AM PDT, starting next week, on Jul 8th. In general it will be a triage 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.

@sabernhardt mentioned that #50120 could benefit from more attention

Open Floor

@Hareesh asked, with regards to ticket #50503 (linked #40039), if it is conventional to make such changes for all bundled themes all the way up to Twenty Ten? @williampatton @whyisjake @audrasjb agreed it was and @whyisjake said the team normally coordinates with ‪@ianbelanger‬ who pushes those same changes to the non-bundled versions that are the in the theme repo.

@enrico.sorcinelli raised ticket #21676, based on the analysis ‪@sergey‬ he thinks that is definitively the time to take a decision for this 8-year old ticket and long awaited simple feature. ‪@sergey‬ asked everyone to read the recent comments on the ticket and share their thoughts

#5-5-2, #dev-chat-2, #summary

Editor chat Summary: 1st July, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 1st July 2020 held in Slack. Moderated by @andraganescu.

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/ version 8.4.0

Gutenberg version 8.4.0 was released.
A huge thank you to @noisysocks for helping for tackling the huge 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..

Here is the nice release post.  It was a packed release with the Image Editing as highlight.

WordPress 5.5.

@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 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 backportbackport 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 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 for new things. 

It’s also time to start thinking about 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.. Anybody can help by writing 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 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

Monthly Plan

The monthly plan for June. A plan for July is in the works by @annezazu

Task Coordination

@zeb

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 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. 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 HTMLHTML 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 testunit 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

@gziolo

I’m backporting changes to WordPress CoreCore 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 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

@annezazu

@joen

I’d love eyes on this one, which tightens up the 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. controls: PR: 23578

@ajlende

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

@itsjusteileen

I’ve been testing in Full Sitesite (versus network, blog) Editing and reviewing docs for the Block Directory

@nrqsnchz

 I’ve been helping with designing flows for template creation in FSE, and reviewing/testing PRs for a11yAccessibility 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

Nik Tsekouras

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

@mapk

I’m focusing on 5.5 to help review and test where needed.

@youknowriad

  • I’ve worked on our CI setup and used 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 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

@paaljoachim

 I am helping to get the dev environment tips and tricks in place to help any user for migrationMigration 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.

@michaelarestad

We’re working on flows to create new templates and would love your feedback on initial needs/ideas here.

Open Floor

@noah

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 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). 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?

@andraganescu

Myself and a bunch of other folks who have been working on a new, block-based, menus page (nav-menus.php) in wp-adminadmin (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 triagetriage 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.

#core-editor, #core-editor-summary, #core-restapi, #gutenberg

CSS Chat Agenda: 2nd July 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, July 2, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making WordPress 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • CSS audit status update
  • Color scheming update
    • #50504 High contrast color scheme in 5.5
  • CSS Latest and Greatest Link Share

#agenda, #core-css

CSS Chat Summary: 25th June 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1593118837002500

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

I added a summary comment with remaining items to the main CSS audit ticket, and confirmed with the group that we were in agreement to remove auditing CSS comments from the list. I also added property counts for letter-spacing and font-family to go along with the other typography-related properties.

There was general agreement that the “Determine methodology recommendations” sub-task ticketticket Created for both bug reports and feature development on the bug tracker. is complete since we have been using @ryelle excellent CSS audit tool. The next step will be determining how to automate the results, and @isabel_brison suggested that be a separate ticket. In addition to an automation ticket, I added that we will want to have a ticket to determine the display of audit data.

Color scheming updates

@ryelle mentioned the merged PR to 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/ that successfully applied the adminadmin (and super admin) color scheme using a single base color with accompanying Sass mixin vs using the post-css themes approach we’ve looked at previously.

@danfarrrow mentioned the possibility of computing the color values in native CSS using custom properties. There was agreement that this would be ideal, but that Sass or PostCSS would be required at least in part, and we would need to test out some approaches, including something like outlined in this blog post. @youknowriad mentioned an issue with the approach outlined in the blogblog (versus network, site) posts ties the colors 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. to HSL values, and we would want to have the colors available in a more generic form. Still, some experimenting is in order before we fully rule out the possibility!

CSS Latest and Greatest Link Share

I shared the gap property that can be used for horizontal and vertical spacing between elements for both flexbox and CSS grid. While support is not green across the board yet, recent versions of Chrome have full support, so we are getting close and this blog post of mine gives an overview of using the gap property with a fallback.

#core-css, #summary

Media Meeting Recap – June 25, 2020

Here’s a summary of the #core-media chat from June 25, 2020. Weekly media meetings happen on Thursdays at 14:00 UTC; see the full transcript here, in the Make WordPress Slack.

Attendees: @paaljoachim, @joemcgill, @desrosj, @chaion07, @cdog, @sageshilling, @antpb, @afercia, @swissspidy, @JJJ, @pbiron

Discuss Media REST APIREST 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/. endpoints

The below post was discussed as an effort to bring visibility to the changes in image editing. Please take a moment if you haven’t to consider any Media implications of the changes. Many great ideas have been documented in the post.

Ticketticket Created for both bug reports and feature development on the bug tracker. #50105: Remove infinite scrolling behavior from the Media grid

#50105 was discussed and there is some help needed testing the most recent patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to remove the infinite scrolling behavior in Media grid. Separately from this issue, a new 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. was found that needs some attention. The unintended consequence of the changes were that the number of items counted for the “Load More” button are incorrect as they calculate images that do not render. The ticket at minimum before 5.5 needs a more accurate count to better represent what is left to load. An issue to track this can be found in #50410.

Media Meeting Continued June 26 at 14:00 UTC

One topic that did not get a chance to be discussed was #16020 “Upload custom avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. for user in Dashboard” which was recently commented with a recommendation to remove from the 5.5 scope. Given the timeframe and wide range of complexities, this needs some time to:

  1. Discuss tomorrow at 14:00 UTC to determine next steps
  2. Collaborate with the Privacy team to ensure this is done in the best way for everyone and in a featured 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.

Please feel free to continue the momentum of this issue join in on the discussion tomorrow.

#core, #core-accessibility, #core-media, #media, #summary

Editor chat Summary: 24th June, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 24th June 2020 held in Slack. Moderated by @paaljoachim.

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/ version 8.4.0 RC 2

Gutenberg version 8.4 RC 2 was released today.
A huge thank you to @noisysocks for helping for tackling the huge 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..

The next Gutenberg release 8.5 to be released on the 6th of July and will be included in 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. will be on the 7th of July.

Project board for WordPress 5.5.

@ellatrix is maintaining a project board for 5.5 of issues/PRs that need to go into the next release.
@youknowriad is already satisfied with what has already been added to 5.5.
@michael-arestad there are a few issues he would like to see added. Such as PR: Try: Don’t show a clone when dragging.
@ellatrix We should begin polishing what we have now for the next release.
@mcsf we need to backport a lot of PHP changes to core and begin thinking about compiling 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..

Monthly Plan

The monthly plan for June.

Task Coordination

@zebulan
I’ve been working on moving reusable blocks to their own tab in the inserter.
I’ve also been working on various PRs to fix cases where useSelect calls were missing dependency arrays or had incorrect dependency arrays.
BlockSettingsMenuControlsSlot: add missing useSelect dependency
useDisplayBlockControls: add missing useSelect dependency
Optimize useSelect calls (batch 1)
Technical issues in this PR blocking future improvements: Buttons block: lighten editor DOM even more. Once that PR is unblocked, I can resume work on this one: Buttons block: overhaul alignment/justification controls If anyone could help figure this out so we could try and get this done before WP 5.5, that would be much appreciated. Right now the Buttons 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. alignment controls are confusing and broken.

@ntsekouras
I’m working on adding keyboard support for moving blocks.
Associated. Prototype: move blocks between levels with keyboard

@poena
Because this feature that introduces descriptions to block patterns would require changes to existing block patterns, a decision is needed so that it may be included in 5.5. We probably don’t want 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). breaking changes after patterns are available in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@michael-arestad
We’re starting in on the “Create a new template” flow
If you have any thoughts or ideas, let me know.

@youknowriad
I worked a lot on end 2 end tests lately, hopefully they are more stable now
Finally landed the quick inserter PR.
I’ll focus in on 5.5 related tasks (backports, tests on Core…)
Polish and 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 on Gutenberg side.

@annezazu
I’m continuing to do triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. on needs-testing and unlabeled alongside officially placing docs about the FSE Outreach Program here. There are more to come that are being drafted and shared for feedback in #fse-outreach-experiment including a general FAQ.

@joen
I’ve been sheparding this drag and drop improvement along, and it’s looking like it can land, so I would just highlight it for your eyes once again.

@itsjonq
Continue efforts under the “Design Tools” label.
More recently, helping out with the drag/drop experience @joen and @michaelarestad mentioned.

@itsjusteileen
I’ve been testing in Full Sitesite (versus network, blog) Editing (FSE) and helping @annezazu over in #fse-outreach-experiment. I also helped get Add reusable block tab to inserter moving and on the Project Board for 5.5. I also added Discussion: Should theme.json support conditional logic like theme supports and looking for input.

@ellatrix
I’ve been helping out with 5.5 🙂

@ajlende
Image editing tools.
Working on Image Editor Batch API for updating the REST APIREST 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/..
Discussion about in #core-restapi channel.
Outside of Gutenberg land: Add option for flipping the image to the crop view which can be re-added in a future Gutenberg PR after it was removed in Image editing: batch editing in cropper component.

@noisysocks
Regarding task coordination, this week I’m: Releasing Gutenberg 8.4.
Working on allowing Search to be added to the Navigation screen.

Open Floor

@Kiril Zhelyazkov
I need eyes on Block icons are reordered when adding new blocks. There are different suggestions for how it should be handled and I can’t decide which is the right way to solve it.
–> No replies yet.

@chrisvanpatten
I’m not sure if I’ll be able to attend the meeting this week but I want to call attention to this issue: Patterns should not display if their blocks are not allowed.
@youknowriad
Plans to take a closer look at the issue.

@mrwweb
Use .has-background to indicate any type of background. Introduce second class for type of background.
The Block-based Themes team agreed it makes sense and we’ve since done additional research and gotten feedback that seems to confirm this is a positive change. Because it is an issue that involves changing front-end CSSCSS Cascading Style Sheets. classes, it feels like this needs to get into the soonest release possible to avoid causing disruption. At this time, the general consensus is that the risk of adding it is very low, but that will obviously increase over time.
@zebulan
Comment: A has-background class sounds like a good idea to me.

@itsjusteileen
Eileen is asking for comments to this issue:
Discussion: Should theme.json support conditional logic like theme supports
@youknowriad
Comment: I don’t think we need to add condition logic to 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. aside block vs global specific settings but the editor settings are filterable whether they come from theme.json or not, so conditional logic is possible there.

@MrMark
Before I submit a ticketticket Created for both bug reports and feature development on the bug tracker., wondering if anyone knows the reasoning behind having a bottom margin on wp-block-columns and wp-block-column so that when you have columns within columns, it creates large margins below that grouping, etc.
@michael-arestad
Comment: I think it’s worth a ticket/issue. If anything, we could add some conditional CSS to remove the bottom margin from child column blocks. Or just remove the margin.
@jonoalderson
Comment: https://every-layout.dev/layouts/stack/ is handy for this sort of thing. Much cleaner than conditionals for parent-child structures.

@joyously
We need either more knowledgeable people or a document (user docs for editor) to send users who ask questions in the Gutenberg plugin support forums.

@paaljoachim
Having a buddy buddy system where developers can help and review each others PRs. Reach out to other developers through a polite direct message and ask for advice. We are all here to also help each other along our paths.

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

Media Chat Agenda: 24th June, 2020

This is the agenda for the weekly Media Meeting scheduled for Thursday, June 24, 2020, 04:00 PM GMT+2.

This meeting is held in the #core-media channel in Making WordPress 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/..

– Topics to Discuss

Implications of the proposed experimental REST APIREST 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/. endpoints for image editing: https://make.wordpress.org/core/2020/06/14/shipping-experimental-endpoints-in-core-rest-api-meeting-summary-june-11-2020/

#50105: Remove infinite scrolling behavior from the Media grid – Discuss next steps. Seems that this could use testing and dev-notes. Let’s see how we can help here!

Custom AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. feedback that @cdog provided last week:
https://make.wordpress.org/core/2020/06/18/media-chat-agenda-18th-june-2020/#comment-38779  

Discuss support for WebP – @joemcgill said in #core-media, “Given the announcement yesterday that Safari is about to support WebP, I’m wondering how we might go about supporting the format in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., revisiting this discussion: https://wordpress.slack.com/archives/C02SX62S6/p1581005513097600

Even if you cannot 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 meeting, you are encouraged to share anything relevant for the discussion. If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #media