What’s new in Gutenberg 9.8? (20 January)

As 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 and community continue to forge ahead with implementing Full Site Editing and Global Styles, the latest installment of the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (version 9.8) has been released today 🥳 As always, this release also includes many fixes and some nice new enhancements.

Semi-transparent Spacer 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.

The Spacer block, when selected, now has a semi-transparent background, rather than an (opaque) light grey one. This should make it easier to discern from any layer behind it (such as a Cover block or image), if that is of a very light color itself.

Block Switcher Shows variation icon

As a follow-up to an improvement to block variations that shipped with 9.7, the block switcher now displays the variation’s icon, rather than the block’s generic one.

Site Editor now iframed

The Site Editor now renders its content in an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. There is a number of reasons for this, such as avoiding adminadmin (and super admin) CSSCSS Cascading Style Sheets. bleed, or allowing to simply use a theme stylesheet for a site without any adjustments. Once this approach proves stable, the team is planning to make the same change to the Post Editor.

FSE: No more auto-drafts

Full-Site Editing no longer creates auto-drafts for template and template part post objects. These auto-drafts were previously needed for block templates and template parts that were based directly on files from an FSE theme without any user modifications. However, they required complex management and sync logic that proved fragile. By removing them, the team hopes to stabilize a fundamental part of FSE.

9.8 😬

Enhancements

  • Use a semi transparent background for the spacer block when selected. (28103)
  • Display matching variation icon in Block Switcher. (27903)

New APIs

  • Create Block: Allow using locally installed packages with templates. (28105)
  • Create block: Add support for static assets. (28038)
  • Compose: Export useIsomorphicLayoutEffect and use it. (28023)

Bug Fixes

  • Reusable Blocks:
    • Show an error message when a reusable block has gone missing. (28126)
    • Fix dismiss notice after error. (28015)
  • Cover Block:
    • Fix nested cover block 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.. (28114)
    • Fix invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. cover block transforms. (28087)
    • Fix cover 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.. (28287)
    • Fix Cover focal point picker. (28350)
    • Fix matrix alignment issue. (28361)
  • Fix block error when transforming blocks with Link Popover opened. (28136)
  • Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Notice in navigation-link. (28134)
  • Prevent link paste in RichText components in Button and Navigation blocks. (28130)
  • Fix floating date status inferred for posts where the status has been edited. (28127)
  • BlockSwitcher: Fix crash due to null reference. (28122)
  • Verse: Fix line-wrap rendering on front-end of site. (28109)
  • FocalPointPicker: Fix rendering and dragging experience. (28096)
  • Block Directory: Fix “missing” block when the block can be installed from the directory. (28030)
  • Fix locked template not updating when inner blocks template prop changes. (28007)
  • Fix editor crash when registering a block pattern without categories. (27970)
  • Fix the RTL editor styles and the theme styles option. (27947)
  • Don’t close the block inserter when clicking the scrollbar or an empty area. (27946)
  • Fix AlignmentMatrixControl focus issue. (27945)
  • Fix unexpected autosave for published posts. (27942)
  • Fix RadioGroup to support zero as a Radio value. (27906)
  • Update embed block transforms to permit multiple links to be pasted in a paragraph (#27551). (27746)
  • Change the week 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. and left button style to meet the date spacing. (27730)
  • Add aria labels to box control component inputs/button. (27727)
  • Use clientWidth when no width is available for cropper. (27687)
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Normalize _fields value for use in stableKey. (27526)
  • Fix appender margins again. (27392)

Performance

  • Components: Expose composite 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. from Reakit. (28085)
  • Improve Inserter block hover performance. (26348)

Experiments

  • Full Site Editing Framework:
    • Load content in iframe. (25775)
    • Avoid using auto-drafts for theme templates and template parts. (27910)
      • Delete unused options while upgrading the plugin. (28164)
      • Fix _wp_file_based term deletion in migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.. (28300)
    • Fix the border radius in the site editor. (27986)
  • 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.:
    • Add border radius to the theme styles schema. (27791)
    • Add theme.json 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. mechanism and JSON file specifying which theme.json paths are translatable. (27380)
    • Add: Save time theme.json escaping. (28061)
  • Group Block: Add border radius. (27665)
  • Hide the theme without comments.php deprecation message. (28128)
  • Fix navigation editor. (28080)
  • Widgets: Temporary fix for saving widgets. (28078)
  • Decouple query from edit site. (27972)
  • Only enable the template mode for viewable post types. (27948)
  • Box control units: Ensure custom units are preserved. (27800)
  • Navigation Block: Use draft status when user creates a post and don’t render unpublished posts in menus. (27207)

Documentation

  • Docs: Improve README file for @wordpress/create-block. (28052)
  • Create Block: Update the demo included in the README file. (28037)
  • Docs: Switch heading to Quick Start for consistency. (28019)
  • Docs: A wether, as it turns out, is a castrated ram. (28008)
  • Update Quickstart guide for the Development Environment documentation. (28005)
  • Update copyright year to 2021 in license.md. (27951)
  • Block API: Add more inline comments. (20257)
  • Changelog: Group entries for 9.8.0-rc.1. (28332)

Code Quality

  • Remove effects test file and remove unused refx dependency. (28162)
  • Annotations: Replace store name string with exposed store definition. (28156)
  • Edit Widgets: Replace store name string with exposed store definition. (28044)
  • Interface: Replace store name string with exposed store definition. (28041)
  • Upgrade Reakit to version 1.3.4. (28013)
  • Fix PHPCS warning: Undefined variable $i. (27955)
  • Consolidate block editor initializations. (27954)
  • Fix create-block PHP template files according to WordPress standards. (27949)
  • block-directory: Simplify the LOAD_ASSETS flow by making it an async function. (25956)

Tools

  • Workflows (i.e. 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):
    • Create Release Draft when tagging version. (27488)
    • Add action to upload release to SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. repo. (27591)
    • Compare Performance upon Release. (28046)
    • Build Plugin Workflow: Bump node version to 14. (28048)
  • End-to-end tests:
    • FSE: Fix intermittent errors in multi entity editing test. (28107)
    • Fix randomly failing end-to-end test. (28073)
    • Upgrade puppeteer to 5.5.0. (28055)
    • Performance tests: Fix. (28026)
  • Scripts:
    • Align default engines for check-engines with the package. (28143)
    • Add support for static assets in build commands. (28043)
    • Make it possible to transpile .jsx files with build command. (28002)
    • ESLint minor version upgrade to 7.17.0. (27965)
    • Upgrade Jest to the new major version (26.x). (27956)
    • Use wordpress/stylelint-config in wordpress/scripts. (27810)
  • Linting:
    • ESLint Plugin: Enable import rules used in Gutenberg. (27387)
    • Add no-unsafe-wp-apis to recommended configuration. (27327)
    • Remove /wordpress from test/linting ignore paths. (20270)
    • Update changelog for stylelint-config. (28074)
  • Testing: Prevent a direct usage of Reakit. (28095)
  • Update the minimum Node.js version to 12. (27934)
  • wp-env: Ensure the environment is used with the logs command. (27907)
  • Packages: Fully automate npm publishing with the latest and next tags (28335)
  • Upgrade webpack to version 5. (26382)
  • Revert “Upgrade webpack to version 5”. (27974)

Various

  • Gutenpride Template:
    • New Package to use with the tutorial. (27881)
    • Create Block: Enhancements to Gutenpride tutorial template. (28215)
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: Remove redundant array coercion. (28072)
  • Visual editor: Remove focusable wrapper. (28058)
  • Readme: Increase tested Version up to WP 5.6. (28050)
  • Interface: Remove deprecated prop from InterfaceSkeleton. (28034)
  • List View: Reduce whitespace and always show nested blocks. (28029)
  • Making 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. inspector’s tabs stick when scrolling. (28003)
  • Chore: Update Lerna dependency. (27990)
  • Try: Make focus width a CSS variable. (27968)
  • Add translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. context to all block’s titles. (27933)
  • Add primary destructive button style. (27774)
  • Modifies the widgets dashboard link to point to the new widgets editor. (26880)
  • Use standard select element for small number of authors. (26426)
  • Add srcset for cover image. (25171)

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.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 9.85.55s29.05ms
Gutenberg 9.75.29s26.32ms
WordPress 5.64.66s28.57ms

Kudos to all the contributors that helped with the release! 🙏

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

CSS Chat Summary: 14 January 2021

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

Housekeeping

@notlaura pointed out that we missed a scheduled 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 today which started a short discussion about how to make them consistent.

The outcome was that the lead for each scrub should be established the week before which @notlaura will check in with to make sure the scrub can go ahead as planned. If necessary an upcoming scrub can be skipped and removed from the meetings calendar.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported having made a PR to reorganise the audit tool’s HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. report directory structure with the goal of simplification. He also moved the report stylesheet into /src and added a command to copy it into /public, which means that files inside /public need no longer be edited manually.

@notlaura noted that the property values reports issue still needs to be resolved. She linked to this related github issue as a place to discuss & keep track of ideas.

Color Scheming (#49999) & Visual 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. Testing (#49606)

@isabel_brison shared her PR to add visual regression tests for wp-admin pages which is now ready for review/testing. This will be a very useful addition to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing suite, particularly for CSS.

@ryelle reported that she shared her reduced colours branch in dev chat and is hoping for more feedback, from design especially. To encourage this she also added needs-testing to #49999. The branch is available here – please have a look.

Open floor & CSS link share

@isabel_brison shared a link to Web Directions’ call for speakers for their upcoming CSS conference. The deadline is the end of this month so get those proposals in!

@notlaura shared a useful reference for logical CSS functions min, max and clamp.

@danfarrow shared a piece of CSS esoteria: an ugly hack for rounding values down with two decimal places.

This prompted wry speculation on the usefulness of 0.01px precision, and with that the meeting concluded. Thanks everyone!

#core-css, #design, #summary

A Week in Core – January 18, 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 January 11, 2021 and January 18, 2021.

  • 18 commits
  • 41 contributors
  • 47 tickets created
  • 4 tickets reopened
  • 102 tickets closed

As we get closer to the first 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. of WordPress 5.7, the Core activity has started to increase again this week 📈😎

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.

Code changes

Administration

  • Update hover and focus states in adminadmin (and super admin) menu – #28599
  • 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): Remove <strong> tags from labels on 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/theme editor screens – #52232

Bundled Themes

  • Twenty Twenty-One: Remove duplicate CSSCSS Cascading Style Sheets. rules – #52158
  • Twenty Twenty-One: Remove leftover file from `build:rtl` task – #52293

Coding Standards

  • Improve code layout in wp-admin/includes/class-wp-media-list-table.php#51014
  • Coding Standards: Fix WPCS issue in [49963]#52316

Customize

  • Update button label reference in themes help text to reflect the label introduced in [41626]#52271

Docs

  • Correct description for wp_slash() and wp_unslash()#51800
  • Docs: Clarify the instructions on starting the local environment for the first time – #52278

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.

  • Add support for German (Austria) 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. in remove_accents()#52110
  • I18N: Add context for the Public string in site attributes list on Edit Site screen – #52309

Media

  • Use consistent method for instantiating an attachment author object in Media Library – #52030

Menus

  • Fix minor UIUI User interface issues on Edit Menus screen on smaller viewports – #49245, #51706

Posts, Post Types

  • Introduce a 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. paginate_links() output – #44018

Privacy

  • Use more consistent wording for strings related to personal data requests – #51849

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

  • Allow sending an empty array to delete multi 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. keys – #50790

Script Loader

  • Remove unused source file for wp-a11y.js which was replaced with the @wordpress/a11y package – #50093

Widgets

  • Implement TinyMCE on text widgets in Accessibility Mode – #52073

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@audrasjb (7), @mukesh27 (3), @afercia (3), @sabernhardt (2), @ibdz (2), @poena (1), @rianrietveld (1), @Boniu91 (1), @ravipatel (1), @jomisica (1), @accessiblejoe (1), @florianziegler (1), @hedgefield (1), @michaelarestad (1), @ryan (1), @yoavf (1), @chemiker (1), @paaljoachim (1), @estelaris (1), @SergeyBiryukov (1), @passoniate (1), @nonverbla (1), @pawki07 (1), @alexstine (1), @carloscastilloadhoc (1), @hellofromTonya (1), @garrett-eclipse (1), @re.ardestani (1), @laxman-prajapati (1), @hansjovisyoast (1), @MadtownLems (1), @hareesh-pillai (1), @chrisvanpatten (1), @dariak (1), @xkon (1), @transl8or (1), @ovidiul (1), @johnbillion (1), @patopaiar (1), @antpb (1) and @justinahinon (1).

Please welcome our 8 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@jomisica, @nonverbla, @pawki07, @carloscastilloadhoc, @reardestani, @dariak, @ovidiul and @patopaiar.

Core committers: @sergeybiryukov (11), @ocean90 (3), @ryelle (2), @joedolson (1) and @timothyblynjacobs (1)..

#5-6-1, #5-7, #week-in-core

DevChat notes – 13 January 2021

Thanks to @thewebprincess and @metalandcoffee for leading the 05:00 UTC and 20:00 UTC devchat meetings this week.

Slack discussion for the 05:00 meeting

Slack discussion for the 20:00 meeting 

Announcements

  1. Core Editor Improvement: Drag & Drop Blocks and Patterns from the Inserter. You can now drag and drop blocks and 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. patterns from the inserter. You will need 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/ 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
  2. A Week in Core – January 11, 2020 for a summary on the activity in the team.
  3. Recap and proposal: align the WordPress release cycle with the industry standard. There are two proposed solutions. Questions from @francina: Do you have question about those? Do you want to discuss them here? Do you prefer to leave comments? 
    4. Editor chat summary: Wednesday, 13 January 2021

Upcoming Releases

Discussions

  • @timothybjacobs: on the spread of releases between four and six per year, time for recovery, wait between releases for a feature which misses a release date, impact of ‘sitting out a release’ in the event of a six per year cycle. Suggestion of a 2 month release cycle, followed by a 4 month cycle? To get an idea of what it might feel like without jumping straight to 6 a year
  • @francina: it’s four and not more because the rationale is to increase incrementally and not in one go… Predictability is key and having a calendar shared well in advance is also important
  • @sarahricker: pace should pick up now people are back from holiday and getting into a rhythm for four releases a year will help
  • to be able to get four releases in 2021, we should start to prepare next release (squad, goals, etc) as soon as the current release is branched (end of alpha cycle)
  • almost like you need a A team/B team to tick/tock the releases
  • @francina: this calendar was proposed by me to Matt at WCUS2019 and published only after his approval. 2020 has been rough and personally I don’t think we made all the preparations necessary to add a release. Life got in the way. I don’t think 5.7 should be taken as an example for how releases might be done for the rest of the year. Described it as a transition release
  • @Whyisjake: coming back just after the holidays is part of the issue. The issue is not as much about number of relea@whyisjakeWhyisjake: coming back just after the holidays is part of the issue. The issue is not as much about number of releases, but:
    • identify bottlenecks
    • clarify expectations
    • communicate the schedule in advance
    • pick a procedure, ANY procedure, and stick to it long enough to test it out

Extra help needed for 5.7

@webcommsat asked: Do we know the specific areas where more contribution is needed? Knowing where the gaps are for contributors can help with potential recruitment/ encouragement to support those areas. A lot of people who volunteered/ showed interest for a release may be interested/ available to help, but not know where to start. Perhaps some of them could be approached and if their skills/ interests match, could be asked to help in the specific areas where we are short.

@francina: Everyone can contribute to a WP release at any time, in any field they are interested in.

@chloe Bringmann: I think calling out the need each focus has for volunteers is a good first step. I am happy to help connect people to projects. It isn’t a long term solution so I welcome thought partnership on future engagement plans.

Areas identified in the meeting as needing more contributors:

  • @sarahricker: 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) could use some recruitment
  • @johnbillion: testing
  • @estelaris: add more sessions for combined 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)/design
  • @noisysocks: editor (GB) needs help
  • @metalandcoffee: coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor could use some help
    • for a better understanding of what we did and what we need to do, @hellofromtonya shared some stats from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. This is what has been discussed. Three weeks to 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 (Feb 2).
      Progress has been very light, though normal for year-end. Ramp up after the holidays/year end has been slow.
    • Scrub participation has been very very light sometimes 
    • 64 tickets closed or ready for commit
    • 68 features and enhancements still open that have a hard-stop on Beta 1 [ report ]
    • stats posted for 5.7
  • @francina: Hence the discussion about what goes into Beta and what doesn’t. When defect work happens and where feature work happens. This is are not theoretical exercises about naming conventions in web development. Clarifying what gets done and when, helps contributors and the plugin and themes ecosystem to know when WordPress is tested ‘enough’ to work on their own products

    @hellofromtonya: shared a concern discussed in the APAC-friendly dev chat. Do you think it’s reasonable for everyone to switch gears at Beta 1 to shift from the current release directly into the next release cycle? Or do you think contributors need a break and time to ramp down and then ramp up back up again?
  • @audrasjb: it really depends on the individual

    Discussion on an additional 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:
  • @metalandcoffee: do you think we should add an additional bug scrub per week with 68 bugs still being open? Not sure how helpful that would be.
  • @audrasjb: features and enhancements are our main goal for now. As always, we won’t get everything committed in time, but it would be nice if components maintainers could help on those features/enhancements. And speaking of testing, it’s especially needed for those tickets
  • @hellofromtonya: participation in the scrubs has been very light throughout 5.7. I don’t think adding another will help.
  • Scrubs are specifically focused on features and enhancements
  • @francina: Test scrubs should be back on Friday. @monikarao is preparing a list of tickets

WordPress 5.6.1 news

@audrasjb: 5.6.1 Trac update:

  • 52 tickets in the milestone
  • 23 are closed as fixed
  • 11 are fixed 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. but waiting for proper 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. in 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". 5.6.1
  • 18 are still in the to do list (not committed/closed/reopened for backport)
  • the idea is to release by the end of January 2021, probably around the 24 or 26
  • a post will be published very soon on Make/Core with more details.

Updates from the Component Maintainers and Focus Leads

@sergey: Build/Test Tools, General, 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., Date/Time, Permalinks: No major news this week.

@audrasjb: circling back to 5.7, I forgot to share my quick Docs update, for those interested:

  • 29 tickets marked as `needs-dev-note`
  • 10 of them are already closed as fixed
  • the traditional 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. spreadsheet will be started in a couple days
  • 4 tickets are marked as `needs-docs`, and more to come.
  • will try to pay some attention on updating the HelpHub documentation

@imath

@hedgefield

  • Design: still getting my bearings as I was only inducted a few days ago but we’re working through the design-related tickets, some are already set for dev, and some are on their way there

Upgrade/Install/Core auto-updates (@audrasjb)

@audrasjb

  • Menus: nothing new, except I have 1 ticket ready for commit
  • 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.: nothing new

Open floor

Kelly: would like some attention on #49999 and the linked PR. It’s apart of a larger project to clean up the adminadmin (and super admin) CSSCSS Cascading Style Sheets. code and to standardize the color palette used across all screens.

@ryelle the PR is to reduce the number of colors used in wp-admin’s CSS. It’s part of the work on ticket #49999, but the PR has a more concise description (the ticket is a larger project). There are also some before & after screenshots.

#devchat

Test Scrub for WordPress 5.7

As part of the 5.7 release, we’ll be hosting test scrubs focused on the tickets milestoned for 5.7 on Friday, January 12, 2021 at 13:30 UTC in the #core channel 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/..

Following are the tickets going to be discussed in the scrub

Testing Environment

  1. Open the Terminal app
  2. Install homebrew by pasting /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)" – You might be asked if you want to install the Xcode Command Line Tools, confirm.
  3. Install GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. by typing brew install Git
  4. Install Docker by typing brew cask install Docker
  5. Install Node by typing brew install Node
  6. Open the Docker app in your computer and ignore the welcome screen that tells you to create a container
  7. Clone 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 with the wordpress-development environment by typing git clone and the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org you get when you click on the green button on the top of the GitHub repo that says Code. Pick the HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. URL.
  8. Go to the directory where you cloned the repo (you can use cd wordpress-develop to locate it)
  9. Now type these 4 commands
    1. npm install
    2. npm run build:dev
    3. npm run env:start
    4. npm run env:install
  10. You should be able to access the development version of WordPress at http://localhost:8889/. You can access it with username admin and password password

Do you have a ticketticket Created for both bug reports and feature development on the bug tracker. you want to bring up for testing?

Fantastic!

In order to allow testers to manually test the 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., you should include the following information:

  • What are the steps to reproduce the problem?
  • What are the steps to test?
  • Are there any testing dependencies such as 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 or script?
  • What is the expected behavior after applying the patch?

#5-7, #test, #testing

CSS Chat Agenda: 14 January 2021

Note: 1 hour before the meeting, we will have the bi-monthly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

This is the agenda for the upcoming CSS meeting scheduled for Thursday, January 14, at 10:00 PM UTC. 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
    • Checking in on meeting format
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual 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. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 07 January 2021

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

Housekeeping

@notlaura asked if the recurrant format of the meetings is still working and there was general agreement that yes, it is.

CSSCSS Cascading Style Sheets. Audit (#49582)

@ryelle commented that @notlaura‘s config file PR is looking good and that she has started a new PR using GitHub actions to auto-generate the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS audit report.

@notlaura shared a screengrab of an issue with the report’s in-page navigation when used with config files. The full text of each property-value query is being used in the nav making it look quite unwieldy.

This led to a discussion about how property-value audit queries should be formed in order to provide useful results, and then to a recap of the end goals of the audit. The consensus was that one of the main goals is to improve consistency of CSS values, and to identify repeatable patterns which could be abstracted into design-system type naming.

@ryelle clarified that this was the thinking behind audits reporting the top 10 most & least used values.

Color Scheming (#49999) & Visual 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. Testing (#49606)

@ryelle expressed some doubts over the benefits of the reduced colors branch. The group was quick to dispel these doubts, pointing out several ongoing benefits of the project and assuring her that it’s well worth continuing with.

Bolstered by the positivity, @ryelle said she would refresh the 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". and bring it up at the next dev chat.

Open floor & CSS link share

@ryelle put a call out for testers for patches she has contributed to these three CSS related trac tickets.

@notlaura shared a link to @q‘s 2020 proposal about a global style system, suggesting it would be cool to apply to apply such a system to WordPress adminadmin (and super admin).

And with that inspiring thought the meeting drew to a close. Thanks everyone!

#core-css, #summary

Editor chat summary: Wednesday, 13 January 2021

This post summarizes the latest weekly Editor meeting (agendaslack transcript), held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, 13 January 2021, 14:00 UTC.

WordPress 5.7

WordPress 5.7 is now underway with BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 due on 2 February 2021. You can help with this effort by jumping in on the following issues shared by @noisysocks:

https://github.com/WordPress/gutenberg/issues/24965
https://github.com/WordPress/gutenberg/issues/14744
https://github.com/WordPress/gutenberg/issues/24092
https://github.com/WordPress/gutenberg/issues/25983
https://github.com/WordPress/gutenberg/issues/23636

Finally, you can follow this Project board that tracks WordPress 5.7 “must-haves”. Please add issues to this board and/or reach out to (@noisysocks) if there is something you think needs to be included.

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/ 9.7 & 9.7.1

Gutenberg 9.7 & 9.7.1 were released over the last week. Highlights include drag & drop from the inserter for block patterns, updates to the reusable 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 more.

Gutenberg 9.8 RC

As a reminder, Gutenberg 9.8 RC will be released this week to allow for a 1 week RC period before the stable release next week. Please use this as a chance to test the RC!

Monthly Plan & Key Project Updates

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles
  • Block-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
  • Full Site Editing

For detailed plan check out monthly priorities post.

Full Site Editing Update from @ntsekouras

Testing/feedback/review on Query Pagination block with InnerBlocks
and feedback for possible use cases of a Query Title block would be fantastic. Any thoughts and help are really appreciated!

Global Styles Update from @jorgefilipecosta

The 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. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. mechanism was merged! There is a proposal for a save time theme.json escaping mechanism. The progress to integrate the font size picker new version advanced nicely and the PR should be merged soon.

Widgets & Navigation Update from @andraganescu

They are both back working in the main 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". after some foundational changes broke them.

Native Mobile Block Editor Update from @hypest

  • We added the ability to move blocks to top/bottom via long-pressing the block mover icons
  • Removed the info popup on start about the block editor being the new default as it’s been quite some time now that Gutenberg rolled out
  • Added block insertion E2E tests
  • Made progress on porting the Audio block

Work will continue on the audio block, the code block and prepare to work on the table block.

Help test full site editing

Today is the final day to respond to the very first call for testing for the FSE outreach program. Feedback is of course always welcomed and appreciated 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/. Expect a post this week on Make Test summarizing the results of this first test and join #fse-outreach-experiment if you’d like to help with future calls for testing. Thank you to all who have already helped test!

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@ajlende

  • This PR has now been merged: WordPress/gutenberg#25171 adds srcset for cover images. Looks like there’s a few people who would appreciate it for performance reasons and it’s needed in order to add duotone to the cover block. The primary question in the PR is if it’s worth adding the polyfill for IE.
  • Would love a review for this PR: WordPress/gutenberg#27936 has some light refactoring of the custom gradient picker which also adds some inline documentation and simplifies the code for readability. It also allows me to reuse it for the duotone picker

@joen

@youknowriad

  • Landed the removal of the auto-drafts in Full Site Editing, an important low-level work.
  • Fixed a number of small bugs and tweaks here and there
  • A number of reviews and discussions.
  • Going forward, would like to focus a bit more on FSE, maybe the template mode in the post editor in the next days.

@ntsekouras

  • PR for Query Pagination with InnerBlocks.
  • Display matching variation icon in Block Switcher.
  • Various small 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 reviews.

@itsjonq

  • Continue the efforts of updating our Component Systems, starting with the FontSizeControl integration.
  • Working through final details/adjustments to make sure things conventions are compatible with Gutenberg.

@annezazu

@paaljoachim

  • Triaging older issues from 2018 and 2019. As well as triaging needs design feedback issues.
  • Docs: Working on (again) improving the Local WP Development Environment setup.
  • Taking part in Learn/Training team meetings to see where Gutenberg can improve to help make things easier there.
  • Docs: Working on Improving the intro Block Editor Handbook page. Issue 27400.

Open Floor

Should we implement a “stale bot” on the GitHub Repo? Raised by @mkaz.

The full question can be seen in this comment. A stale bot essentially automatically goes through issues after X timeframe and can be programmed to share a message before handling closing out the issue/PR. By implementing some version of a stale bot to sweep through the repo, it can ideally help keep the open issues/PRs more relevant and up to date while handling out of date items. Here are key points from the discussion:

  • We’d want a long timeframe for closing. ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. uses 90 days but we’d be looking at 120+ days.
  • Important to keep in mind, closed tickets are still searchable, still exist, and still make up the archive. They don’t disappear, and can be reopened.
  • A label could be added to keep something from being auto-closed for particular items.
  • It would be important to get the messaging right in whatever comment left by the stalebot so it’s clear what action needs to be taken to keep an issue or PR open, the reasoning for such a bot, etc.
  • It’s unclear what kind of approval/agreement is needed for this change. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. currently doesn’t have this policy but it’s unclear if that’s due to tooling limitations.

Next steps: @mkaz and @annezazu will collaborate on a Make Core post to propose this change, draft a suggestion for the messaging, and get feedback to make sure this is an okay direction to go in.

Help review a restructuring change to the Gutenberg Developer Handbook. Raised by @justinahinon.

Work is underway in this PR about Gutenberg developer handbook homepage as part of the handbook restructuring project. This PR should ideally help give a better experience with more clarity for users who first enter the handbook. The first experience matters immensely so this is a great thing to get right! Give your feedback in the PR.

What’s the best way to allow my block users to edit attributes for every display (desktop, tablet, mobile)? Raised by @louis.

Here’s an expanded version of the question for clarity:

As I understand, iframing the editor is finally coming round (really great stuff). I’ve been looking at different ways to allow my block users to edit attributes for every display (desktop, tablet and mobile), but does the Gutenberg team have an idea worked out on how these attributes will be edited responsively? And if so, is it planned for WordPress 5.7.

@joen kindly jumped in to share some great thoughts:

  • This is really tricky to get right and the team likely won’t have something for 5.7.
  • The current approach is to first and foremost build as good a responsiveness as you can, right into the block. For example, having smart defaults, like how the Media & Text block collapses when responsive.
  • Right now, you can actually hook into the preview dropdown, and leverage that to create your own responsive system right now. This is what the Layout Grid block does, feel free to look at the source there.
  • Even implementing what the Layout Grid does, the experience is still lacking: How do you edit the desktop breakpoint on a physical mobile device?  How do you customize, or add additional breakpoints? All of this is TBD.

Ideally, going forward work started in this Gutenberg issue and improvements to Global Styles can enable this to work better in the editor.

#core-editor-summary

Editor chat summary: Wednesday, 6 January 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, January 6, 2020, 14:00 UTC.

Thank you to all of the contributors who tested 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

WordPress 5.7

WordPress 5.7 is now underway with Beta 1 due on 2 February 2021. Now’s the time to be thinking about what 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/ features 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 we want to ensure are in the release. Project board to track WordPress 5.7 “must-haves” is available. Please add issues to this board and/or reach out to (@noisysocks) if there is something you think needs to be included.

Gutenberg 9.6

Gutenberg 9.6 was released on 23rd december. The big focuses throughout this release cycle were Full Site Editing and Global styles. This release also includes many fixes and some nice new features and enhancements.

Gutenberg 9.7

Gutenberg 9.7 was released on 6th january. First release of 2021 🎉. A number of contributors enjoyed some well earned time off but it didn’t stop them from shipping exciting features for 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.

Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles
  • Block-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
  • Full Site Editing

For detailed plan check out monthly priorities post.

Updates on the key projects

@jorgefilipecosta

  • On the Global Styles side, the work to include the new version of the components is ongoing. Starting with the font size picker. Our end to end tests was improved To not be as markup dependent And work with both versions of the components. There were some end-to-end tests that were legitimately failing And fixes were submitted. Besides that, the discussions on 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. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. continued to happen. But all the feedback was applied and I think is ready to merge.
  • Another big chunk of the work saves time escaping the theme.json structure to align with what happens with other WordPress data saved in custom post types. This work is proving a little bit more complex than I anticipated. But a part should be ready very soon
  • Currently, we are blocked on an issue regarding transpiling. zustand is not being transpiled and the build is not ECMA compliment. I am not really sure how to force the transpiling of that specific lib. All the solutions I tried failed. But I have a considerable lack of babel knowledge So any help here is appreciated

@annezazu

  • The Full Site Editing Outreach program is underway with the very first call for testing
  • While you can leave feedback anytime 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/, this call for testing will be open until January 13th.
  • If you don’t have time to test right now, no worries—another way to help would be to share the call for testing with others.
  • If interested in joining the fun in general, please :dance: your way over to #fse-outreach-experiment

@paaljoachim

  • In regards to widgets screen update Every Wednesday UTC there is a block-based widget editor chat in the #feature-widgets-block-editor
  • The first meeting after the holiday was earlier today.

@noisysocks 

  • Going through various 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. issues. A new technical method is on its way check the main issue

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@get_dave

@ntsekouras

  • Add block transforms preview
  • Display Block Information by matching block variations is merged. This includes the addition of a property (isActive) in Block Variation’s settings. This optional property is a function to match block variations after their creation.
  • Add new post link to Query Block.
  • I have a PR for new block ‘Archive Title’.

@itsjonq

  • I had a break in December, so I’m catching up on all the things.
  • My primary focus is to continue work on the new Component System (aka. “G2 Components”).
  • As @jorgefilipecosta had mentioned earlier, we’re working on integrating things with the ‘FontSizePicker’ component. I’ll be helping with all integration efforts on that front. We’ll then have the UIUI User interface set up to start improving the UI for Global Styles.

@priethor

I’ve just started working on this issue, my first contribution Navigation Block: Add support for a dynamic home URL

@paaljoachim

  • I am working on various documentation such as updating Setting up a Local Dev environment. I also made a video for it. How to test a PR issue. Etc.
  • Widget screen Using the Move to option

@youknowriad

I took the time where everyone was away as an opportunity to solve two of the long-standing issues we had:

  • Reusable blocks to use controlled inner blocks (multi-entity save flow)
  • Refactor FSE templates and template-parts to avoid auto-drafts for theme provided template files.

One is shipped and I’ll continue with the second one

@adamsilverstein

  • I’ve been working on improving the Combobox controls we added for the post author and page parent selector and could use some help/review on when someone has a chance.

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

A Week in Core – January 11, 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 January 4, 2021 and January 11, 2021.

  • 10 commits
  • 19 contributors
  • 64 tickets created
  • 6 tickets reopened
  • 41 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.

Code changes

Bootstrap/Load

  • Add missing <p> tags to error message in wp-load.php#52254

Customize

  • 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): Add an empty alt attribute to the <img> tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) used as a hidden placeholder in 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. preview when no logo is chosen – #51846

Docs

  • Correct description for wp_parse_list()#51800

Editor

  • Support filtering arguments in 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. type registration from metadata – #52138

Help/About

  • Accessibility: Use more descriptive link text for the Privacy Policy link on the Privacy screen – #52233

Login and Registration

  • Introduce the lostpassword_user_data 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. which allows for the user data object during a password reset request to be filtered – #51924

Posts, Post Types

  • Introduce the wp_list_table_show_post_checkbox filter which allows the visibility of the bulk edit checkbox on the post list table to be controlled separately from the edit_post capability of the current user – #51291

Privacy

  • Clarify the “Contact information” heading in default privacy policy content – #52272

Quick/Bulk Edit

  • Aaaand our best commit message of the week so far, by @johnbillion (read the full commit message here) 😂
    By the power vested in me, I hereby declare the top bulk actions and the bottom bulk actions joined forever in MatrimonyScript – #46872

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

  • Fix fatal error on 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 when calling the single item 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 routes – #52205

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@audrasjb (4), @mukesh27 (2), @shital-patel (1), @marcelo2605 (1), @carike (1), @hareesh-pillai (1), @pbiron (1), @garrett-eclipse (1), @subrataemfluence (1), @clayray (1), @sabernhardt (1), @swissspidy (1), @TylerTork (1), @laxman-prajapati (1), @alexstine (1), @coreyw (1), @oakesjosh (1), @TimothyBlynJacobs (1) and @johnjamesjacoby (1).

Please welcome our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@TylerTork and @coreyw.

Core committers: @sergeybiryukov (5), @johnbillion (3), @timothyblynjacobs (1), @and @gziolo (1).

#5-6-1, #5-7, #week-in-core