Tag Archives: summary

Jb Audras 9:42 pm on September 22, 2021
Tags: , , , summary   

Dev chat summary – September 22, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Worth mentioning:

Thanks to the 42 contributors of the past week, including 7 new contributors! Kudos to the 4 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.

A Week in Core – September 20, 2021

Upcoming releases updates

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s)

@desrosj and @circlecube are still leading the 5.8.x releases.

They will publish a schedule for 5.8.2 and –if needed– 5.8.3 on September 23.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.

Concerning the next major release —WordPress 5.9— a planning roundup was published a couple weeks ago.

Worth noting that @chanthaboune proposed a review of the upcoming 5.9 key features in the last issue of the WordPress.org podcast.

@audrasjb proposed to start to schedule 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. scrubs for the milestone. He will run the first scrub of 5.9 on Thursday September 23, 2019 at 20:00 UTC.

Reminder: everyone is welcome to run a bug scrub on the #core 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. If you are interested, please read this handbook post: Leading bug scrubs. And yes, that’s a call for volunteers 🙂 Please add a comment below if you want to help.

For 5.9, @hellofromtonya pointed out that it would be nice to try to also plan some APAC-friendly bug scrubs when possible.

Component maintainers updates

Help/About – @marybaum

Build/Test Tools – @sergeybiryukov

  • Some changes were implemented to make the PHPUnit Polyfills loading more flexible and improve the related messaging. See changesets 51810-51813 and ticketticket Created for both bug reports and feature development on the bug tracker. #46149 for more details.
  • The PHPUnit Polyfills package and related test infrastructure changes are now backported to a few older branches (WP 5.8 to 5.2). This makes it easier for developers to continue testing on multiple versions of WordPress while adding tests for newer versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher, which require more modern PHPUnit practices. See changesets 51838-51840, 51843-51846 and ticket #53911 for more details.
  • Work is now complete on Modernizing to the Latest PHPUnit version. Dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is being reviewed and plan is to publish on Monday.
  • PHP 8.1: work is nearly complete, i.e. identified through tests. Will be shifting shortly into community feedback and open call for contributions to identify and help fix compatibility issues.

General – @sergeybiryukov and @hellofromtonya

Internationalization – @sergeybiryukov

  • A translator comment was added to clarify 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. HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block 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. settings form. This should reduce confusion for Polyglots translating the string.

Toolbar – @sabernhardt

  • @sabernhardt shared a draft of a Toolbar component update post (it’s also available in a Google doc if you want to add comments that way)

Open Floor

From @hellofromtonya: If you want to contribute to the Testing Team, here’s this week’s edition of Week in Test which is a curated list of where testers (of any skillset) are needed this week.

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

Dan Farrow 3:49 pm on September 21, 2021
Tags: , summary   

CSS Chat Summary: 16 September 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @dryanpress shared the working document and the trac ticket, for anybody new to the project
  • All coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have now been claimed, and are either in progress or have a PR, however @dryanpress reminded us that if anyone has claimed a file and can no longer work on it please do let us know
  • The next step is reviewing and merging PRs. Help is very welcome if anybody is up for “trying out a PR and making sure the colors still look correct (or correct enough, where maybe we made changes)“
  • @dryanpress raised the topic of skinning adminadmin (and super admin) colour schemes, as there are some custom properties for body.admin-color-ectoplasm already in custom-properties.css. We would probably create a couple of colour schemes at a later stage, for testing & demonstration purposes
  • @dryanpress outlined the final todo list for the project:
    • Merge all remaining files
    • Look for duplication and opportunities for property consolidation
    • Final team review
    • Merge proposal write-ups
  • @ryelle added that, before the final team review step, discussion will be needed about what to consolidate and how, for example rgba and box-shadow values
  • @ryelle added that, as there are several PRs now merged, anybody interested could start generating some ideas for these next steps right now
  • @dryanpress asked if we are still on target for an --experimental release in 5.9 which @ryelle confirmed we have good momentum for
  • @ryelle observed that there are other places outside of CSS files where CSS is used, for example php and js files, which also need to be reviewed. @dryanpress offered to add this and the other tasks (mentioned above) to the planning document
  • @CodeXplorer admitted to wanting to help but feeling lost, to which @dryanpress provided a few notes of the current state of the project
  • @danfarrow had quickly calculated there are now 127 custom properties in custom-properties.css. @robertg added that this isn’t including the 225 (approx) in his PR

Open Floor / CSS Link Share

Thanks everybody!

#core-css, #summary

Dan Farrow 8:37 am on September 14, 2021
Tags: , summary   

CSS Chat Summary: 09 September 2021

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

Announcements & Housekeeping

  • @wazeter shared the facilitator schedule sign-up form – please add your name if you would like to run a future meeting or CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
  • @danfarrow shared the dev-chat meeting guide which could be useful for finishing the Core CSS meeting guide
  • @danfarrow observed that some WordPress docs pages relating to local dev have not been updated to include details of wp-env and expressed an intention to remedy that

CSS Custom Properties (#49930)

  • @dryanpress has some files ready to submit, @wazeter is finishing updating media-views.css and @danfarrow posted a draft PR for forms.css
  • deprecated-media.css is the only remaining unclaimed file
  • @ryelle has been working on reviewing & merging PRs as they come in. She is planning to open a new base 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"., once more PRs are merged, to make it cleaner for the next stages
  • @danfarrow asked about the PR review process. @ryelle said she’s been trimming down custom properties to existing ones where possible, and testing in the browser
  • @danfarrow asked if creating a custom-properties aliasing existing custom-property is ever useful. @ryelle responded that they might be if there could be a requirement to style a component differently, but the subject is open to discussion. @dryanpress & @wazeter expressed the view that more aliases give users more granular control outside of the cascade
  • There was general agreement that this project is a good opportunity to clean up things like the inheritance structure, minor colour variations etc.

Open Floor / CSS Link Share

Thanks everybody!

#summary

Francesca Marano 7:59 am on September 9, 2021
Tags: , , , summary   

Dev chat summary, September 8, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

The attendees did not add comments to the posts highlighted in the agenda.

Worth mentioning

Thanks to the 61 contributors of the past week, including 7 new contributors! Kudos to the 7 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too

A Week in Core – September 6, 2021

Announcements

  • WordPress 5.8.1 release team ran into an issue with 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/ that required a chunk of manual work. WordPress 5.8.1 went out few hours after the chat.
  • The Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. is currently organizing the 2021 edition of the WordPress Translation Days.
  • Work on the jquery upgrade is rolling on now, @azaozz is working on the PR

Component maintainers

Build/Test Tools

Work has continued on adding missing @covers tags to unit tests for more accurate coverage. See ticketticket Created for both bug reports and feature development on the bug tracker. #39265 for more details.

General

Work has continued on:

  • #51553 – Fixing parameter name mismatches for parent/child classes for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 named parameter support.
  • #53635 – Making various compatibility fixes for PHP 8.1. Thanks @jrf and @hellofromtonya! 

Upgrade/Install

Open Floor

The attendees briefly discussed #53784 – Additional review welcome.

@annezazu reminded everyone about the FSE Program Exploration: Help with the future of Block Theme Switching

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

Andrei Draganescu 8:34 pm on September 8, 2021
Tags: , , summary,   

Editor chat summary: 8 September, 2021

This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @andraganescu.

Announcements

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/ 11.5 RC launched today (Sep 8)

@mikeschroder released Gutenberg 11.5 RC. You can take it for a spin from here.

Important resources for the incoming period of time

@priethor added some details about where we should look for guidance around the incoming updates to WordPress in light of the 5.9 release:

There will be an upcoming What’s Next in Gutenberg post based on the preliminary road. It’s worth noting the “What’s Next” intent is to highlight issues where contributors can help, whereas the high-level plan is defined in the preliminary road post.

Key Project Updates

Navigation Editor

@get_dave shared this week’s update:

Mobile

From mobile, @hypest offered the updates:

 Shipped

  • 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. picker search.
  • Inline previews for YouTube and Twitter embeds.
  • Alignment options for embeds.
  • New experimental Gallery block.

In Progress

  • Embed block.
  • GSS Font size, line height, colors.

Components

@mciampini shared some updates from the folks working on the components package:

Shipping:

Notable fixes:

In Progress:

Task Coordination

Feel free to add items to this post if you weren’t able to make the meeting.

@ntsekouras

@joen

@mamaduka

  • Updated documentation to replace withSelect HOC references with useSelect.
  • Worked with Riad to fix code data issue with include query parameter.
  • Checked on approved PRs, merged some, and left comments on others to see if authors have time to address the feedback. (Sorry if you received more notifications than usual)

I would appreciate feedback on the following PRs:

  • 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. Fetch: Improve isMediaUploadRequest check
  • FSE: Add basic support for child themes

@get_dave

@jorgefilipecosta

  • During the last week I updated the design of the mosaic view, I iterated on the engine to allow blocks to be aware of global styles, I proposed the PR to enhance the design of the new color picker and I did multiple PR reviews. I also started the effort to replace tinycolor with colord.
  • For the next week I place on continuing the color library replacement, Iterate on the color picker design and pick another task related to the global styles new design.

@zieladam

@annezazu

@mciampini I plan on:

@oandregal

  • I’ve been working on enabling the global stylesheet for all themes and other minor improvements. Prepared a PR to make sure themes with 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. load the styles fine 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. as well as the theme directory.
  • In the area of alignments: landed a PR that makes the wide control only available if the theme provides a wide size and prepared another for fixing floats (left, center, right) for blocks that are not part of a container.

Open Floor

Will PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher minimum required version change in WordPress 5.9?

@anil (Anil Sardemann) asked about the future min. PHP requirements of 5.9. @hellofromtonya explained that there are no plans to change the minimum supported PHP version in WordPress 5.9 since still more than 5% of WordPress runs on PHP 5.6.

Help with the future of Block Theme Switching

@annezazu brought more attention to the FSE Program Exploration: Help with the future of Block Theme Switching. This is a very new approach in that it’s all about gathering insights to help shape the potential designs rather than testing a specific flow. It’s neat to be able to be involved this early in solving a problem. Check it out, share your thoughts, and get creative!

Help needed with review

@faizan asked for a review on his 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. on Ticket 50074

#core-editor, #core-editor-summary, #summary, #themereview

Dan Farrow 9:36 pm on September 6, 2021
Tags: , summary   

CSS Chat Summary: 02 September 2021

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

Announcements & Housekeeping

  • @danfarrow shared a document he worked on after last week’s meeting: a CSS Chat Facilitator’s Guide
  • The document includes a facilitator schedule – anybody interested in running a future CSSCSS Cascading Style Sheets. Chat or CSS Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session is very welcome to add their name!
  • @notlaura let us know that her attendance will be spottier than usual for the next couple of months, but we are lucky to have had some new attendees join the meetings recently

CSS Custom Properties (#49930)

  • @robertg asked about indicating pull requests in the planning document’s Claimed & Unclaimed Files list. @danfarrow clarified that they should be marked with a link “Pull request” linking to the PR on 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/. Merged PRs are indicated by striking through the entire line
  • @Erik raised the subject of polyfilling, as the ticketticket Created for both bug reports and feature development on the bug tracker. mentions Internet Explorer. @danfarrow pointed out that the ticket was created before WordPress dropped IE support so it’s no longer an issue. It’s always fun to be reminded of this fact, so thanks @Erik!
  • @robertg shared his WIP PR adding custom properties to customize-controls.css, which is littered with border-* properties
  • @ryelle announced that anybody who has claimed a file but not been able to work on it is free to unclaim it, with no strings attached. @danfarrow welcomed this sentiment as he may well fall into this categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.
  • @danfarrow noted that all but 2 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have been claimed, and 11 PRs have been merged. He asked about the next step to which @ryelle responded that we will want to circle back to the unresolved subject of handling colours with opacity
  • @Erik noted an rgba based approach e.g. background: rgba(var(--color--), .9); which led to an interesting threaded discussion on the subject
  • @danfarrow asked @ryelle about progress in relation to her projected roadmap. @ryelle responded that at the current pace things are looking good

On that encouraging note the meeting drew to a close. Thanks everyone!

#core-css, #summary

Francesca Marano 8:26 am on September 2, 2021
Tags: , , , summary   

Dev chat summary, September 1, 2021

@hellofromtonya led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

The attendees did not add comments to the posts highlighted in the agenda.

Worth mentioning

Thanks to the 34 people who contributed to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. last week, including 2 new contributors! Kudos to the 8 core committers of the week, too

A Week in Core – August 30, 2021

Announcements

  • WordPress 5.8.1 RC 1 was released right before the dev-chat.
  • @webcommsat announced that the 6th edition of WordPress Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day has started on September 1st and will run through the whole month: you can check the dedicated website.
  • @annezazu reported that a proof of concept for a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to Playwright was shared during the core editor meeting and well received thus far.
  • Tonya noted that the Test team is working on updating the local testing docs in the handbook to include not only wp-env but also multiple workflow alternatives.

Empower everyone to contribute!

Tonya Mork

Component maintainers

Build/Test Tools

Work continues on improving the PHPUnit test suite and PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 fixes.

Help/About

@webcommsat and @marybaum are meeting to plan ahead for WordPress 5.9 and what are the implications of auto-updates on the About page.

Upgrade/Install

Open Floor

Tonya brought up #53450 and asked for feedback. Two committers added positive comments so it looks like it’s a good candidate for WordPress 5.9.

Abha reminded everyone about the resources and links that the Marketing team created to promote multiple Make teams.

Michale Rehnert asked about how to set up a Docker container for contributing purposes. @helen suggested two resources:

Colin Stewart asked for feedback on #53152.

See you next week!

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

annezazu 2:50 am on September 2, 2021
Tags: , , summary,   

Editor chat summary: 1 September, 2021

This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @annezazu.

Announcements

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/ 11.4 launched

Release notes coming soon after a quick fix. For now, some highlights:

  • The Gallery 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. now acts as a wrapper for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Image Blocks thanks to the Gallery Block Refactor. 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 and theme authors, please do check out out this dev note to get up to speed on backwards compatibility
  • The Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block now has the option to add duotone filters so you now have even more ways to add your own style to your content.
  • Padding support was added to the Buttons Block making it easier to get the spacing just right.

5.8.1 RC launches today (Sept 1)

Based on the schedule previously shared, 5.8.1 RC will launch today with the release coming on September 8th. If you can, please help test the release.

Final day for the current FSE call for testing (Sept 1 )

It’s the last day to explore the current FSE Outreach Program call for testing. If you have time, share your thoughts! If you don’t, please help amplify by sharing with others.

Reminder: monthly block theme meeting in #themereview

A reminder was shared that there is a block theme meeting in for anyone keen to chat about what’s happening with block themes. This is a recurring monthly meeting so if you missed today’s, don’t worry!

Monthly Priorities & Key Project Updates

The overarching plan for September has not yet been shipped yet so we based today’s conversation on the July & August Plan. As a reminder to those working on these projects, async updates are both welcomed if you can’t make the meeting and needed.

Navigation Editor

For the Navigation Editor portion, @talldanwp shared a lovely update. Here are some highlights:

  • A plan has been formed for migrating from the customize APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. in the navigation editor.
  • The nav editor 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.’s design has been refreshed.
  • Some conversation is underway around extensibility of the editor (join in if you’re interested). 

Mobile

Shipping:

  • Block picker search

 Notable fixes:

  • Fixed an npm install breakage on Gutenberg’s trunk 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". due to third-party dependency we were building that had an unpinned typescript dependency.

In Progress:

  • Embed block (hoping to release some inline previews in our next release)
  • GSS Font size, line height, colors

Patterns

For patterns, some context was shared amongst the core editor wranglers from @paaljoachim that the design tool overview enhancements will ultimately also trickle down to make pattern creation easier, more responsive, etc.

Styling

I’m going to reuse part of the async update from André since he’s done a ton of work there. Lots of work is underway with adding duotone support in theme.json along with a PR around enabling global styles to all themes. Expect work to continue on this path for the week ahead.

No update for the Template Editor or the Navigation Block

If anyone has any context to add around the Template Editor or the Navigation Block, feel free to chime in below in the comments.

Task Coordination

Feel free to add items to this post if you weren’t able to make the meeting.

@mikeschroder

Shipped:

  • Closed 32024 via [51677]. Thanks everyone for your help, including with the follow-up tests commit! 
  • Opened two Video Block poster related PRs (34415 and 34411).

This week, planning to investigate 33437.

@oandregal

@zieladam

@youknowriad

  • I’ve worked a bit on performance. I want to get back to some layout related work.
  • I’ve reviewed a number of PRs as well.
  • I’ve spent some time this week exploring some wild ideas for block registration (both to make easier and more universal/language independent). For the curious, the repo is here https://github.com/youknowriad/blocky it’s no where near ready but I’d love to learn more about your custom blocks, if you have examples or ideas about how you’d ideally write them and what use-cases would you want to see for the simplified “view” property.

@joen

@gziolo

@annezazu

  • Recapping and responding to the current call for testing for the outreach program.
  • Finalizing the next call for testing(more exploration than call for testing right now on theme switching).
  • Drafting some core editor improvement posts + assisting with an upcoming News post
  • Shipped a YouTube video all about patterns.
  • Triaging unlabeled PRs (down from over 100 to in the 20s). The unlabeled PRs that are left I am not quite sure what to do with so feel free to jump in.

Open Floor

Offer to run a Gutenberg Release for the first time. Raised by @mikeschroder.

If folks are interested, after shadowing @talldanwp (thanks again!), I would love to try running a Gutenberg release for the first time. Whenever it works best for the team is okay with me!

Next step: @priethor will coordinate since he helps wrangle the release process.

Proposed migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of E2E specs to Playwright. Raised by Bart Kalisz.

A proof concept was shared and well received thus far as part of a proposed migration to Playwright. At this point, a wider discussion needs to happen with impacted parties to ensure that folks are willing to follow the proposed changes. A few folks chimed in agreeing that a wider discussion needs to happen along with perhaps a comparison with Cypress (mentioned by @swissspidy). Depending on how things go, a Make Core post might make sense.

Next steps: Bart alerted the crew in #core-test and @annezazu will ensure that it gets discussed in the Core Dev meeting for wider attention.

Call for community ideas for FSE Outreach testing calls. Raised by @annezazu.

I’d love to start experimenting with community members sharing ideas for what to test in the outreach program. If you’d like to suggest an idea for a call for testing, know it’s very welcomed and all ideas will be weighed against current project priorities to figure out what makes the most sense to pursue. You can share ideas directly in the #fse-outreach-experiment 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 or via DM to me! In case you’re curious about how calls for testing have been wrangled in the past, it’s typically been a combination of monthly project priorities/release priorities + my own testing/what I can make happen + conversations with contributors.

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

Dan Farrow 11:59 am on August 29, 2021
Tags: , summary   

CSS Chat Summary: 26 August 2021

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

Announcements & Housekeeping

  • Previously we had talked about rotating the meeting facilitator on a regular basis. @notlaura asked anybody wanting to join the rota to step forward
  • UPDATE: We’re now working on a Meeting Guide document, which includes a facilitator schedule for people to sign up to

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @notlaura introduced the project for new attendees and asked for any updates
  • @wazeter committed two PRs last week, one in coordination with @robertg – more commits coming in a few days!
  • @dryanpress similarly expects to be committing in the next few days
  • @ryelle has updated the shared planning document with links to the PRs, and @circlecube has been helpfully indicating merged PRs by striking them through
  • @ryelle asked for help reviewing the PRs – @dryanpress & @wazeter offered their assistance
  • @wazeter shared some details of his methodology for themes.css where he temporarily moved many custom properties to the top of the file with a prefix --wp-admin--themes
  • @ryelle noted that all custom properties should eventually be moved into custom-properties.css
  • @wazeter asked about fallback values which @ryelle responded to: hex fallback rules, which precede rules assigning rgba values for browsers that don’t understand rgba, can now be removed since coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s browser support has been updated – UPDATE: I’ve added a note about this in the shared doc
  • @notlaura added a final note thanking all contributions, especially newcomers

CSS Link Share / Open Floor

  • @notlaura raised the topic of meeting structure, in particular keeping the structured work sessions for times when attendance is low
  • @wazeter supported the meeting format, noting that he sometimes was unsure what to do in the structured work session
  • @notlaura suggested creating some general guidelines on how to run Core CSS meetings – UPDATE: Now underway here!
  • @ryelle volunteered to run the CSS triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session before next week’s meeting – thanks @ryelle!

Thanks everyone!

NOTE: For those interested in facilitating a future meeting or triage, please add your name to the Facilitator Schedule here

#core-css, #summary

Paal Joachim Romdahl 2:55 pm on August 26, 2021
Tags: , , , , summary   

Editor chat summary: 25 August, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, August 25, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party releases

Gutenberg 11.3.0 release notes. Thanks to @vcanales for writing the notes and tackling the release!

New feature highlights:

  • New Dimensions Panel
  • 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. inserter performance improvements
  • Dimension controls for Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. Block
  • New icons for Reusable Blocks and Template Parts

Gutenberg 11.4 RC is available for testing.

Whats next in Gutenberg: July and August

July and August monthly priorities.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Check out the – Site Editor Template mosaic view

Global Styling

  • A proposal of an API to make blocks aware of their global styles. This 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. will allow the UIUI User interface of a block to show their true styles by default.

Navigation Block & Navigation Editor

  • The team have been focused on reforming the project around the goal of removing the “experimental” status of the feature within the Gutenberg Plugin (only).
  • Held a Hallway Hangout on Tuesday to compare and contrast Navigation screens and determine next steps.
    A summary of the meeting and decisions made is available.
  • Tracking issue is being updated to focus on the tasks required to remove “experimental”.
  • Work is continuing on exploring wider architectural issues such as how to best make use of the Navigation block whilst retaining stability.
  • We’ve continued with small UI/UXUX User experience fixes.

Mobile

  • Help menu option that teaches users about the block editor
  • Typography controls to manipulate the font size and line height and improved color settings

In progress:

  • Finalizing Block Picker Search
  • Embed block
  • Editor onboarding help section
  • GSS Font size, line height, colors

Components squad

At the time of the meeting there were no updates on the Pattern project.

Refactored Gallery block

The refactored Gallery block main PR from October 2020 has now finally been merged, and will be included as part of Gutenberg plugin 11.4. There is also a dev note on make core.

Task Coordination

@joen

@annezazu

  • Responding to Full Site Editing (FSE) feedback, testing FSE items, and helping amplify various efforts.
  • Working on a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post about featured image block improvements.

@get_dave

Open Floor

@get_dave

Friendly reminder from Dave to add the most appropriate labels to PRs 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/, whether you’re submitting PRs or helping with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. All efforts there make work easier for the release leadRelease Lead The community member ultimately responsible for the Release..

@paaljoachim

It would be very helpful for us who run the Core Editor Meetings to have tracking issues that are updated once a week, so we can share the project updates during the meeting. As it will also give a nice overview and it would make it easier for anyone to follow along to see the progress over time.

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