Yearly Archives: 2021

Jeffrey Paul 5:08 pm on June 8, 2021
Tags: , ,   

Dev Chat Agenda for June 9, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 9, 2021 at 5:00 UTC and June 9, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • 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 released yesterday, so now in Beta window with Beta 2 in 6 days on Tuesday, June 15th
  • Focus now fully on tasks in the milestone and regressions found in Beta releases
  • Next Beta Scrub before Beta 2 is Monday, June 14th 20:00 UTC
  • 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). 1 in 20 days on Tuesday, June 29th
  • 5.8 release in 41 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #dev-chat

Jb Audras 10:43 am on June 8, 2021
Tags: , , , ,   

A Week in Core – June 7, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 31 and June 7, 2021.

  • 40 commits
  • 72 contributors
  • 53 tickets created
  • 5 tickets reopened
  • 77 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • List Tables: Update spacing in action items on small screens – #48546, #47895

Application Passwords

  • Allow enter key to submit profile form – #52849

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

  • Add a type property to allow Core to identify the source of the editor styles – #53175
  • Add the Site Logo block’s server implementation – #53247
  • Load the WP_Theme_JSON_Resolver class in wp-admin/load-styles.php – #53175
  • Package updates for 5.8 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 – #52991
  • Update script versions – #52991
  • Correct some docblocks added in [50836] – #50328, #52620
  • Fix failing block editor test – #53301

Boostrap/Load

  • 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 allow disabling of object cache – #53322
  • Only reference recovery mode email when it can be sent – #52560

Build/Test tools

  • Remove the ::append_to_selector() method from Tests_Theme_wpThemeJson – #52991
  • Use assertSame() in some newly introduced tests – #52482

Bundled Themes

  • Twenty Twenty-One: Check for navigation element before using it – #52773

Coding Standards

  • Extraneous white space at end of line – #51189
  • Simplify a condition in wp-admin/admin-footer.php – #53306
  • Simplify the logic in WP_Widget::get_field_name() and ::get_field_id() – #16773, #52627
  • Use strict comparison in wp-admin/options-media.php – #52627

Comments

  • Escape comment author’s email in the Edit Comment form – #53349
  • Return valid comment reply link if comments are paginated – #51189

Documentation

  • Add a @since note to wp_parse_id_list() and wp_parse_slug_list() about using wp_parse_list() – #52628
  • Correct type for the $widget parameter of the widget_block_content filter – #51566

External Libraries

  • Update the Requests library to version 1.8.1 – #53334

Plugins

  • Make sure Hello Dolly translations are deleted when the 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. is deleted – #52817

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/

  • Add ‘delete_widget’ action to delete 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. endpoint – #53289
  • Delete fresh_site option when updating widgets via REST API – #53317
  • Fix delete widget endpoint – #53313
  • Rename the $creating parameter of rest_after_save_widget action to $update – #53317
  • Restore the $creating parameter of rest_after_save_widget action – #53317

Site Health

  • Conditionally run Authorization headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. test – #52642
  • Remove unnecessary function_exists() checks from WP_Site_Health::get_tests() – #52642

Themes

  • Fix 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) issues with controls in themes screen – #52649

TinyMCE

  • Don’t attempt to initialize the same instance twice. Follow up to [51082] – #52133, #52050
  • Fix initialization when the editor is in a postbox by delaying it until document.readyState === 'complete' – #52133, #52050

Upgrade/Install

Users

  • Add user’s localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. to password reset link to ensure login screen matches the language of the email – #34281, #52605, #53321

Widgets

  • Add widget_block_content filter – #51566
  • Add missing actions to widgets block editor – #53288
  • Enable MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. and Nav Menu widgets in Legacy Widget block – #53301
  • Make new WordPress installations use blocks in widget areas instead of widgets – #53324

Props

Thanks to the 72 people who contributed to WordPress Core on Trac last week:

@TimothyBlynJacobs (4), @SergeyBiryukov (3), @nosolosw (3), @isabel_brison (3), @andraganescu (3), @alexstine (3), @costdev (3), @hellofromtonya (2), @sabernhardt (2), @joyously (2), @audrasjb (2), @jorgefilipecosta (2), @justinahinon (1), @jipmoors (1), @westonruter (1), @drebbits.web (1), @afragen (1), @stevenkword (1), @jorbin (1), @lukecarbis (1), @jdgrimes (1), @tamlyn (1), @solarissmoke (1), @5ubliminal (1), @helen (1), @celloexpressions (1), @Mte90 (1), @hellofromTonya (1), @kevin940726 (1), @garrett-eclipse (1), @y_kolev (1), @Clorith (1), @Otshelnik-Fm (1), @JeffPaul (1), @talldanwp (1), @WebDragon (1), @dlh (1), @pbiron (1), @jamil95 (1), @sushmak (1), @stevegrunwell (1), @aliveic (1), @mkdgs (1), @williampatton (1), @aristath (1), @timothyblynjacobs (1), @ocean90 (1), @noisysocks (1), @promz (1), @poena (1), @metalandcoffee (1), @desrosj (1), @patkemper (1), @herrvigg (1), @spikeuk1 (1), @dway (1), @azaozz (1), @notlaura (1), @MrPauloEn (1), @paaggeli (1), @engahmeds3ed (1), @utsav72640 (1), @kapilpaul (1), @jrf (1), @schlessera (1), @mbabker (1), @walbo (1), @reynhartono (1), @Otto42 (1), @arunsathiya (1), @danfarrow (1), and @mukesh27 (1).

Congrats and welcome to our 12 new contributors of the week! @costdev, @5ubliminal, @WebDragon, @sushmak, @mkdgs, @patkemper, @herrvigg, @spikeuk1, @dway, @MrPauloEn, @kapilpaul, and @reynhartono. ♥️

Core committers: @sergeybiryukov (15), @noisysocks (8), @joedolson (4), @youknowriad (3), @jorbin (2), @azaozz (2), @ryelle (2), @ocean90 (1), @johnbillion (1), @peterwilsoncc (1), and @clorith (1).

#5-8, #meta2952, #meta4514, #meta4621, #week-in-core

Francesca Marano 9:34 am on June 8, 2021
Tags: , ,   

Upgrade/Install component meeting agenda for June 8th, 2021

The next meeting is scheduled on Tuesday, June 8th, 2021, at 17:00 UTC and will take place on #core-auto-updates SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel with the following agenda:

  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the tickets in the spreadsheet (they all refer to Outcome 1 of the Updater initiative)
  • Status update on the rollback for failed plugin/theme updates
  • Open floor/tickets awaiting review

Got something to propose for the agenda? Please leave a comment below.

#core-auto-updates, #updater, #upgrade-install

Adam Silverstein 8:22 pm on June 7, 2021
Tags: , , ,   

WordPress 5.8 adds WebP support

WebP is a modern image format that provides improved lossless and lossy compression for images on the web. WebP images are around 30% smaller on average than their JPEG or PNG equivalents, resulting in sites that are faster and use less bandwidth. WebP is supported in all modern browsers according to caniuse.

From WordPress version 5.8 forward, you can upload and use WebP images in WordPress like you would a JPEG or PNG image today (as long as your hosting service supports WebP). Switching to the WebP format for your images will improve your site’s performance and your site visitor’s experience. 

How WebP Helps You

WebP images are significantly smaller than their JPEG equivalents, so visitors to your site will see the complete page loaded more quickly. Smaller images take less bandwidth to transmit, and your images still get all of the responsive benefits of srcset and lazy loading by default. Finally, WebP is supported in all major browsers, so most sites can start using them today.

Creating WebP images

Image editing tools support exporting in WebP, or you can also use command line conversion tools or web based tools like Squoosh. Once you save your images as WebP, upload them to WordPress and use them like you would any other image. 

Using WebP images

WebP images work like any other image in WordPress with some small caveats. 

WebP images support lossy and lossless compression, as well as an animated format and support for transparent images. In WordPress, the lossless WebP format is only supported when the hosting server uses Imagick (the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher library) until LibGD adds support. In addition, animated and alpha formats are not yet supported for resized images (lossy images are created instead when you upload in these formats).

WebP support in the media library requires that your web server’s image processing library (WordPress supports both Imagick and LibGD) supports the WebP format. Fortunately these libraries have supported WebP for quite a while so support is widely available. If your web server does not support WebP, you will see an error message when you try to upload a WebP image.

If your audience includes a significant number of users on an unsupported browser (IE11 for example), either avoid using WebP images, or  enqueue a browser polyfill.

Plans for the future

The media component team is also exploring the option of having WordPress perform the image format conversion on uploaded images – using WebP as the default output format for sub-sized images. You can track progress and test this feature on the trac ticket. We are also keeping our eyes on even more modern formats like AVIF and JPEGXL that will both improve compression and further reduce resources required for compression.

FAQ

How can I fine tune the compression quality setting used for WebP images?

Developers or plugins can use the wp_editor_set_quality 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 set the quality setting. The passed mime type enables setting by type, for example:

// Use a quality setting of 75 for WebP images.
function filter_webp_quality( $quality, $mime_type ) {
  if ( 'image/webp' === $mime_type ) {
     return 75;
  }
  return $quality;
}
add_filter( 'wp_editor_set_quality', 'filter_webp_quality', 10, 2 );

What happens if I enable the filter to use WebP sub-sizes, but upload JPEG? Do the sub-sizes have to match the original?

By default, WordPres creates the sub-sized images of the same type as the uploaded file, so uploaded WebP files to get WebP files on your site. If you want to experiment with uploading JPEG and having WordPress auto-convert these to WebP for your sub-sized images, check out this plugin (related trac ticket).

If I use WordPress multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site, will all my sites work with WebP images?

No. Multisite stores the file types that users are allowed to upload when a site is created. We are working on improving this in #53167. In the meantime, to ensure all existing sites on a networknetwork (versus site, blog) allow WebP files, you can use the site_option filter in a network mu-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. to add webp to the allowed file types for all network sites:

// Ensure all network sites include WebP support.
add_filter(
  'site_option_upload_filetypes',
  function ( $filetypes ) {
    $filetypes = explode( ' ', $filetypes );
    if ( ! in_array( 'webp', $filetypes, true ) ) {
      $filetypes[] = 'webp';
    }
    $filetypes   = implode( ' ', $filetypes );

    return $filetypes;
  }
);

#5-8, #core-images, #dev-notes, #images

Paal Joachim Romdahl 6:59 pm on June 7, 2021
Tags: , , ,   

Editor Chat Agenda: 10 June 2021

Moved to Thursday 10th June same time because of WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. EU.

Facilitator and notetaker: @ajitbohra

This is the agenda for the weekly editor chat scheduled for Thursday, June 10, 2021, 04:00 PM GMT+1.

This meeting is held in the #core-editor 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/.

  • Gutenberg 10.7 final release for WordPress 5.8.
  • WordPress 5.8 project board
  • Help Test the Widgets Editor for WordPress 5.8
  • Monthly Plan for June 2021 and key project updates:
    • Global Styles.
    • 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 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. Editor.
    • Navigation block.
    • Full Site Editing.
    • Mobile
  • Task Coordination.
  • Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meetings

Jb Audras 8:09 am on June 5, 2021
Tags: , ,   

DevChat meeting Summary – June 2, 2021

@peterwilsoncc and @jeffpaul led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Blogblog (versus network, site) post hightlights

In the last “Week in Core” issue, @audrasjb featured 98 contributors, 13 new contributors to WordPress source code and 12 core committers.

@priethor shared details on Gutenberg 10.7 including new features like the persistent List View in the Post Editor, responsive navigation menus, many design tools for blocks, and enhancements to the top toolbar, as well as iterative performance improvements and a lot of 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.

@danfarrow shared CSSCSS Cascading Style Sheets. team updates on color scheming, CSS audit, and CSS deprecation path from their last two meetings. For more information, see CSS chat summaries for May 20th and May 27th.

Blog posts that need feedback

@annezazu extended the FSE Program Testing Call #7 from June 9th to June 16th, so please check the post to learn about the feature overview, how to set up your testing environment, and the desired testing flow to help out on this.

@webcommsat has a related ask ahead of Friday’s deadline for suggestions of external channels for the promotion/info share on FSE to various audiences. Everyone is welcome to review and add suggestions in the comments.

@meaghanthompson shared a call for testing the WordPress iOS 17.5 beta, so please check the post to learn about what’s new in the release, what’s most in need of testing, how to set up the test app, and how to report issues you find.

WordPress 5.8 update

@jeffpaul shared a 5.8 schedule reminder: we are now in the Feature Freeze period where focus shifts away from enhancements and feature requests to defects and tasks.

@chaion07 and @francina led different bug scrubs this past week. There’s a final bug scrub on Monday, June 7th at 20:00 UTC to work to clear the milestone before the 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 release the next day. Here is the full bug scrubs schedule.

The next milestone will be Beta 1 on Tuesday June 8, 2021 after which point the focus will shift to testing and fixing bugs discovered during the 3 weeks beta period.

There are two “big” remaining tasks and a call for help from @youknowriad:

  • The Query 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. where 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/ team had some feedback about it being too powerful (need to find better heuristics to disable editing there). Feel free to contribute to the discussion. There is also a subset of this issue.
  • A proposal to change in how edited block templates are linked to themes (using theme mod instead of taxonomies). The Gutenberg team would appreciate some thoughts here from Core folks familiar with these APIs (theme mods, performance, database).

Also, these are the dev notes that need to be written for the editor.

@youknowriad shared that he consider that the Core team is ready for Beta 1, ideally, we’d have some improvements for the Query block by then but not sure if it’s necessary for beta 1.

WP 5.8 Docs focus update

@milana_cap shared that out of 165 tickets, 35 (Gutenberg excluded) are marked for some sort of documentation:

  • 28 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, 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.
  • 5 for updating DevHub
  • 12 for updating HelpHub

Gutenberg will have:

  • 10 dev notes (as per the list shared by @youknowriad)
  • 12 updates for dev docs
  • many updates for end user docs

Everything except block editor end user updates can be found in this spreadsheet. Block editor end user updates can be found in this Drive folder.

Docs needs the most help with end user documentation. For block editor in particular. Some changes from 5.6 and 5.7 are still not published and we had a significant drop in number of contributors due to pandemic situation. Anyone interested in getting involved please 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.” @milana_cap (zzap on 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/). 

Components check-in and status updates

Build/Test Tools, Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks (@sergeybiryukov): No major news this week.

Upgrade/Install (@audrasjb): @francina hosted the weekly meeting and posted the meeting notes.

Menus, Widgets (@audrasjb): no major news this week.

Open floor

@poena has a request on the agenda post for anyone with knowledge on adminadmin (and super admin) pointers:

Theme Check is a 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. used to analyze themes submitted to the theme directory. I’m looking for someone who knows about admin pointers and if this issue from 2016 is still valid. Does the core team want themes with wp_enqueue_script( ‘wp-pointer’ ); or wp_enqueue_style( ‘wp-pointer’ ); to be blocked from the theme directory? The theme would not be able to be uploaded.

If you’re experienced with admin pointers, please respond to the comment on the agenda post or respond in the linked 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 by the repository owner. https://github.com/ issue above.

@webcommsat pointed out that WordCamp Europe is Monday to Wednesday next week!

#5-8, #dev-chat, #summary

Héctor Prieto 9:27 pm on June 4, 2021
Tags: , ,   

What’s next in Gutenberg? (June 2021)

This monthly status update contains 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 June. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so.

How to follow along with Gutenberg:

Here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project. There is also an index page of Gutenberg development-related posts and a Site Editing Milestone overview issue that breaks down the upcoming work into more concrete next steps.

WordPress 5.8 focuses

With WordPress 5.8 Beta 1 planned for June 8, the priorities for the month heavily focus on stabilizing, testing, 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. fixing, and documenting the features recently merged in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., which can be followed in the WordPress 5.8 project board. However, design and development in other Gutenberg areas continue as well, and contributions are welcome!

The remaining tasks for 5.8 include:

Widgets Editor

Work on the block-based Widgets Editor is a continued focus. The main efforts target stabilizing and documenting the editor and the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. block editor, as well as deciding whether the Widgets Editor should be enabled by default.

If you want to help us test the block-based Widgets Editor, drop by the Widgets Editor Call for Testing and report on your experience!

Follow along:

You can find more information about the current work in progress in this tracking issue, as well as on this project board. Moreover, you can join #feature-widgets-block-editor in 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/ 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/ for future 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. Editor-focused meetings.

Navigation Editor

Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible with menus while bringing block functionality to yet another part of WordPress and offer a more modern experience. Current efforts include:

Follow along:

You can follow the progress of this project on this project board or review the new Navigation Editor tracking issue and join #feature-navigation-block-editor in WordPress.org Slack.

Full Site Editing

Work on this major focus for phase 2 is ongoing and is expected to continue as a big-picture goal for 2021. Apart from all the features making it into 5.8, this is the status of the different FSE areas and their upcoming work:

Milestone 1 – Site Editing Infrastructure and UI

  • As the Template Editing Mode is landing in 5.8, efforts focus on testing and stabilizing this feature. If you would like to help, check the current FSE Outreach Program round focused on Template Editing Mode!

Milestone 3 – Global Styles

  • The first version of Global Styles has been merged in core, and focuses need to be revisited. Any relevant update will be posted in this GitHub issue on demand.

Milestone 4 – Theme Blocks

Milestone 5 – Query Block

  • With great power comes great responsibility; because the Query Block is so powerful, contributors are making sure it lands in the best status possible in 5.8 as mentioned in the “WordPress 5.8 focuses” section above.

Further work on the Query block not limited to 5.8 includes:

Milestone 6 – Navigation Block

Follow along:

You can follow the progress of this project with this overview issue showing key milestones for site editing. For each major milestone, there are related issues you can follow if you want a more granular look at each next step.

If you’re interested in testing Full Site Editing, check out the FSE Outreach Program to learn more. If you have questions about Full Site Editing, check out this recent effort to offer answers.

Areas to be aware of

WCEU 2021

WordCamp Europe 2021 is scheduled for 7 to 9 June 2021 as an online event and will include several sessions related to Gutenberg, such as:

  • Full Site Editing (Discussion Panel)
  • A walkthrough of Full Site Editing (Workshop)
  • The Future of Themes in WordPress (Discussion Panel)
  • Blazing fast block development (Talk)

Make sure to register if you haven’t already!

Theme Developers

Calls for testing

Block Patterns

Ways to Get Involved

While the above items are our focuses, don’t forget that you can always help with triage, testing issues, good first issues, and reviewing PRs. In particular, if you’re interested in helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. but don’t know where to start, there’s a course on Learn WordPress for how to do triage in GitHub! Check it out and join us.

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.

Meetings to join:

While you can view all meetings here, here are specific meetings to join depending on your interest. Remember that you need a WordPress.org slack account to participate:

  • Core Editor weekly Wednesdays @ 14:00 UTC in #core-editor focused on all things Gutenberg.
  • Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in #themereview focused on preparing for Full Site Editing.

Thanks @andreamiddleton and @cbringmann for reviewing this post.

#core-editor #gutenberg-next #gutenberg

Dan Farrow 9:05 am on June 4, 2021
Tags: ,   

CSS Chat Summary: 03 June 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @danfarrow offered to run the next 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. scrub (01 July @ 20:00UTC) – thanks me!

Project updates

Color Scheming (#49999)

HSL works but it would force us to have an 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. based on HSL colors, we want to have a more generic API where users just define a single variable.

CSSCSS Cascading Style Sheets. Audit (#49582)

  • @danfarrow reported having made progress on the 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 by the repository owner. https://github.com/ actions to autogenerate the report. There are now two actions, one to merge updates to trunk into the report branch (which appears to be working), and the Build Report action which now generates the report once a day from the report branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. TBC if it now works as expected…
  • @colorful-tones offered to add a link to the CSS Audit report into the CSS Coding Standards docs [UPDATE] Now done, thanks @colorful-tones!

CSS deprecation path (#53070)

  • The next step is a Make post from @tellthemachines, probably on hold until after the upcoming 5.8 release

Open floor / CSS link share

Thanks everyone!

#core-css, #summary

Francesca Marano 9:01 pm on June 3, 2021
Tags: ,   

X-post: Welcome to make.wordpress.org/project

X-comment from +make.wordpress.org/project: Comment on Welcome to make.wordpress.org/project

Lara Schenck 7:34 pm on June 3, 2021
Tags: ,   

CSS Chat Agenda: June 3, 2021

Note: 1 hour before the meeting this week, @sabernhardt will lead a CSSCSS Cascading Style Sheets. 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. scrub looking at 5.8 tickets.

This is the agenda for the upcoming CSS meeting scheduled for Thursday, June 3, at 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!

  • Housekeeping
  • Project Updates
    • Color Scheming (#49999)
    • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS deprecation path (#53070)
    • CSS Audit (#49582)
  • Open Floor + CSS Link Share

#agenda, #core-css

#agenda, #core-css