Tag Archives: summary

marybaum 12:40 am on July 30, 2021
Tags: , , , summary   

Devchat summary, July 28, 2021

A week after the release of WordPress 5.8, @desrosj led a well attended but quick chat on this agenda.

Highlighted blogblog (versus network, site) posts

Jonathan drew the group’s attention to these posts:

A Week in Core – July 26, 2021
CSS Chat Summary: 22 July 2021
Editor chat summary: 21 July, 2021
[Request for feedback] Updater Proof of Concept
Refining WordPress core’s lazy-loading implementation

He also added a late post of his own:

Consistent minor release squad leaders for each major branch: Trial run retrospective and 5.8.x releases

If you’d like to help with 5.8.xx minor releases, leave a comment on that post.

To-do items on 5.8

Moving on, @desrosj opened one last review of the 5.8 release and asked the group for retrospective comments and other feedback.

In reply, @chanthaboune said she’d likely have her retrospective up later in the day. And she said @matveb will shortly have some thoughts about features to target for 5.9.

Remember, also, that trunk is open now, so if you’re a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., keep committing whatever you feel is ready! (Ed. note: Plus, we’re also in alpha for 5.9, so whether you’re a committer or not, if you’re passionate about bringing a new feature into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., now is the time to do what it takes to land it.)

Component maintainers

@sergeybiryukov checked in with news on Build/Test, where ticketticket Created for both bug reports and feature development on the bug tracker. #53363 has details on some 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 updated naming to follow established conventions.

On U[grade/Install, Sergey added a second plug for his feedback request on the updater proof of concept highlighted above.

Open Floor

Above, in highlighted posts, you probably noticed that @desrosj asked for comments on his minor-releases post if you want to help with the 5.8.x minors. He actually added that suggestion in Open Floor.

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

Dan Farrow 9:57 pm on July 27, 2021
Tags: , summary   

CSS Chat Summary: 22 July 2021

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

Housekeeping

  • No housekeeping items this week

Custom Properties (#49930)

  • @notlaura shared some background on the project for new participants and suggested another session of individual work time
  • @notlaura added a note to the trac ticket indicating who has “claimed” particular coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. files

30 or so minutes later…

  • @Dave Ryan reported having made solid progress on login.css & finding some near-duplicate shades of blue, for which he added new custom properties. Work on colour unification can come later
  • @notlaura had a similar experience with shades of grey and agreed with the approach. @Dave Ryan added a note about it to the shared doc

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

Dan Farrow 9:33 pm on July 27, 2021
Tags: , summary   

CSS Chat Summary: 15 July 2021

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

Housekeeping

  • @notlaura wondered how we could encourage participation at the chats, and get more help with the Custom Properties project. She suggested maybe some guidelines on how to get started contributing
  • @danfarrow offered to add some notes to the shared document
  • @notlaura also suggested a “Call for CSSCSS Cascading Style Sheets. contributors” Make post linking to the shared document and offered to work on writing that

Custom Properties (#49930)

  • @notlaura suggested spending some time working individually on the project which is something we’ve tried at previous meetings with great success

20 minutes later…

  • @notlaura used the time to write a draft of the previously mentioned Make post
  • @danfarrow started updating forms.css noting that some custom properties have a longer ancestry e.g. --wp-admin--button--text takes its value from --wp-admin--button-primary, which in turn takes its value from --wp-admin--theme--primary. He speculated that tooling could make it easier to traverse & understand this hierarchy

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

Josepha 2:52 pm on July 24, 2021
Tags: , summary   

Dev Chat Summary: July 21, 2021

@desroj led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to 20:00 UTC <dev-chat> in #core on Making WordPress Slack

Notable news and blogblog (versus network, site) posts

WordPress 5.8 was released yesterday(July 20, 2021)! The new release was downloaded 7.7 million times in a little over 24 hours.

What’s next in Gutenberg?

What’s new in Gutenberg 11.1.0?

Requests for Feedback

Component Team Updates

Build/Test Tools

  • Ongoing modernization of PHPUnit tests. #53363
  • PHP_CodeSniffer updated to 3.6 (with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support) #53477

Auto-Updates

Themes

Open Floor

  • @desroj highlighted a bug in the 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 Filesystem 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. that was requested to be prioritized in 5.9.
  • @chanthaboune raised a discussion about Making WordPress Slack — what we can/should use it for. Should #core be the default channel? Should some other 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 be created to greet new users (who may or may not have context entering Slack that it is mostly a working environment)? This was a lively discussion, please add more thoughts in the comments below!
  • While it’s been a fairly quiet (some might say too quiet) and smooth release, @chanthaboune encouraged the hosting (and greater) community to check-in with support folks and report back any trends. @johnbillion also noted a handful of tickets about Widgets have been opened related to “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. customisation and logic plugins.”

Watch For

Interested in volunteering for upcoming WordPress releases? Please comment below and team reps will reach out!

Props to @dryanpress for taking these #summary notes!

#dev-chat

Dan Farrow 7:15 pm on July 15, 2021
Tags: , summary   

CSS Chat Summary: 08 July 2021

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

Housekeeping

Discussion: Custom Properties (#49930)

  • @ryelle has updated her PR with some custom-property additions to common.css
  • @ryelle observed that a small subset of custom-properties are getting used very often, noting “…while it feels like a lot of variables to be adding, we also use the same concepts in many places”. For example:
--wp-admin--surface--background: #fff;
--wp-admin--surface--background-alternate: #f6f7f7;
--wp-admin--surface--border: #c3c4c7;
--wp-admin--surface--border-alternate: #f0f0f1;
  • @colorful-tones had a question about a particular chunk of core CSS defining somme custom-properties being loaded from multiple unique sources which seems redundant
  • @ryelle clarified that it’s added from a SASS mixin in base-styles and she thinks its there to allow each package to be standalone
  • We agreed that it does feel somewhat redundant when multiple packages are used together. Possibly it’s something that could be improved in future with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. custom-properties

CSSCSS Cascading Style Sheets. Link Share / Open Floor

  • @ryelle shared a comment on the CSS deprecation ticketticket Created for both bug reports and feature development on the bug tracker. (#53070) that she wants to reply to. This led to a discussion about CSS deprecation which covered some of the following:
    • A wider discussion about CSS backwards compatibility needs to happen
    • Some kind of tooling might help to address the issue
    • In the ticket comment, @tellthemachines comments that, as moving redundant CSS into a deprecated.css file doesn’t offer a performance boost, it would be simpler to move it to a /* Deprecated */ section at the end of its file. @colorful-tones disagreed, noting that it deprecated.css existed it could be dequeued for a performance boost. @ryelle asked what would then happen if you installed 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 that uses a deprecated style
    • @colorful-tones agreed with JJJs comment, adding that “Plugin developers need to keep up with changes. If their plugin breaks then it is on them to update.”
    • @ryelle noted that the deprecation issue centres more on “elements that don’t exist in core anymore but a plugin could be using that markup & expecting the CSS to just be there”
    • @colorful-tones observed that multiple deprecation paths might be needed for the various sources of CSS, which @ryelle summarised as theme CSS (the Twentys styles), wp-admin CSS (all the files in wp-admin/css and wp-includes/css) and 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/ CSS (“technically a subset of wp-admin CSS but also its own thing”)
    • @colorful-tones expressed support for the approach recommended in the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket: “Create deprecated.css and perhaps even start appending --deprecated-5.8 to classes that are deprecated.”

With that we were out of time. Thanks everyone!

#core-css, #summary

marybaum 5:47 pm on July 15, 2021
Tags: , , summary   

Dev chat summary: July 14, 2021

Well now! We have less than a week left in the 5.8 release cycle, and this was its final devchat.

@francina welcomed several new attendees and opened the chat with this agenda (props @jeffpaul!).

Notable blogblog (versus network, site) posts

5.8 RC 3 is here. Please test the release and report any last-minute issues!

A Week in Core for last week highlights 44 contributors, two of them new and 14 active committers. Props @audrasjb!

Ever wondered why we use chat instead of video? So did Arnold Wright KITI, and here’s the discussion that followed.

Three items of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ news:

  • Gutenberg reached 11.0 with a basketful of enhancements.
  • Check out the latest Editor chat summary, here.
  • And there’s a late-breaking dev note that pertains to the editor 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..

If JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. is your jam, the Core JS team is changing its office hours.

And, the mobile teams would really like you to test their respective 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, for iOS here and for Android here.

Upcoming release: 5.8

A final schedule reminder: we’re in the RC period, with a hard string freeze. RC 4 is slated for Thursday, July 15 at 16:00 UTC (Ed. note: basically now, at this writing) and final release in FIVE DAYS on Tuesday, July 20.

@desrosj gave a detailed report on what still needs to happen before Tuesday. He also covered what’s going in the RC 4 release. Please check out his review and pitch in if you can!

If you’re interested in the process of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, you’ll want to see the discussion that followed, about the tickets involved and how they arose. The team is following a new, more traditional process that @francina championed for this release and has also had strong public advocates in @azaozz, @audrasjb, and others.

@chanthaboune raised this Polyglots/WP-CLI ticket and asked for some quick eyeballs.

Component maintainers

@sergeybiryukov reported in for Build/Test Tools: they’re working hard to modernize the WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite with tickets #53363 and #53491.

Open floor

@francina used the last ten minutes of the chat to go back to @Arnold W. K.’s questions and give more context about how the Core team does things.

She also asked first-time attendees how they happened to find their way to the channel.

You can catch the discussion verbatim here.

(Ed. note: Updated Friday, July 16) @webcommsat reminded the group of two things:

Marketing is still accepting ideas for social-media posts on this Social Sharing Google Doc. Questions? Ask her, @marybaum or @meher.

Marketing also still wants to know: what’s your favorite feature? Add your nomination, and why it’s your favorite, to this Google Doc.

#core, #dev-chat, #summary

Paal Joachim Romdahl 8:16 pm on July 12, 2021
Tags: , , , , summary   

Editor chat summary: 7 July, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, July 7, 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/ 11.0

Gutenberg 11.0.0 release notes. Thanks to @get_dave for writing the notes!

New feature highlights:

WordPress 5.8

WordPress 5.8 project board.

Monthly Priorities

June monthly priorities. (A special update for July and August will be coming.)
Along with Key Project updates.

Global Styles

Update from @nosolosw

  • The focus continues to look out for fixing bugs that are backported to the Betas/RC. The only major thing left at this point is being able to translate strings coming from theme.json at translate.wordpress.org. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.: theme.json strings not extracted for translation.

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor

Update from @andraganescu

  • The widgets editor is looking stable. This 5.8 RC2 release included several fixes and we’re hoping for a stable period with no new major issues. Currently, there are some problems in testing with WP 5.7.2 so please test using the 5.8 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"..

Update from @noisysocks

Navigation Block and Navigation Editor

Update from @andraganescu

  • For the navigation block I want to highlight the merge of @tellthemachines’s PR that decouples the markup if the block between the front end and the editor.

Update from @joen

Update from @get_dave

Mobile Team

Update from @chipsnyder

  • Gallery Block Refactor (PR) – Just needs the experimental feature flag work to wrap. NEEDS a code review:
  • In Progress:
  • Editor Onboarding.
  • Adding search to the block inserter.
  • Embed block.
  • iOSiOS The operating system used on iPhones and iPads. share extension.
  • Wrapping up support items for GSS Colors getting ready to look into GSS Font Sizes.

Full Site Editing Outreach program update

@annezazu

Task Coordination

@mamaduka

@joen

I have some PRs that need reviews to land, but are otherwise solid. If you have green checks, I’d appreciate it:

@get_dave

  • I’ve been working mainly on contributing bug fixes to the Widgets screens.
  • Also focused on facilitating the release of 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 11.0.0, including spending time tweaking documentation and hacking on potential improvements to release tooling.

@annezazu

  • Main focuses: end user docs for the upcoming release and the FSE outreach program (current call for testing + high level feedback items post). Want to try to test 5.8RCs every day until the release.

@aristath

  • Main focus this past week for me was bugfixes for 5.8, lots of testing, and PR reviews.

@jorgefilipecosta

Open Floor

Not getting pinged directly in the issue
when an associated PR is created.

@paaljoachim

Regarding creating a PR. The PR author should also add a comment to the associated issue mentioning that a Pull Request has been made, so that commenters in the issue will get a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” about the newly created PR. Could some information be added to the PR template to tell PR authors that they need to add a comment to the issue about the PR?

@aristath

Comment: Not all PRs are tied to a ticket… There are a lot of PRs that are the place where the actual conversation takes place, and that is fine.
So if such a comment gets added to the PR template, the wording should be such that makes it clear that if there is a ticket related to the PR, a comment would be welcomed.

Next steps and key projects

@nosolosw

I have seen that we are scoping the next steps and key projects and I think it would be good to re-align the editor agenda topics (key project updates), the monthly priorities post, and this work in the coming weeks.

@annezazu

Comment: I agree with that comment from André! I think first things first — the monthly priorities post needs to be adjusted so the key project updates can fall in line @priethor is on it as far as I know.

E2e tests

@annezazu

Topic: I’d like to talk about e2e testing and what can be done collectively to improve the reliability of these tests. I’ve repeatedly seen e2e tests brought up as a major pain point over time. I’d love to hear what ideas folks have but, for now, I think it might be neat to try having dedicated time to discuss e2e tests during meetings.

Comments:

  • Some of the main points that came up:
  • e2e tests are important to catch regressions, the more we work on them and feel responsible about their stability (and not just relaunch until it pass), the better.
  • Look to improve overall stability.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is starting to build e2e tests following models/patterns from Gutenberg.
  • What about forming a project to focus on improving the stability and robustness of the Gutenberg e2e tests? It might provide focused attention and effort as well as a board to collect and promote shared collective insights and discussion.
  • Several tests that can become unstable from time to time, and often times, the reason they break is legitimate just hard to reproduce.

A followup conversation between @hellofromtonya and @youknowriad

  • Current state: e2e test suite is robust and stable.
  • Failed e2e tests are real failures.
  • Problem: difficult to debug and identify why and where new code is legitimately making existing tests fail.
  • This changes the discussion and focus: shift towards => how to surface the why and where to help contributors make their tests more robust as well as fix problems in their source code that are making existing tests fail.

Check out the longer discussion about this topic that happened during the meeting.

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

marybaum 9:26 pm on July 8, 2021
Tags: , , , summary   

Dev Chat summary, July 7, 2021

With just two weeks left in the 5.8 release cycle, @jeffpaul led the devchat on this agenda.

Announcements

RC 2 has landed! And it needs you, to help test it in as many ways as possible and chase down any last-minute bugs. For details, check out the RC 2 release post here.

As it happens, @desrosj reported in and said the release is in great shape:

The milestone only has three 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. tickets remaining that may require changes (excluding release related task tickets and two tickets needing only to be backported). We are in great shape heading into RC3 and final release. 

@desrosj

Blogblog (versus network, site) Post Highlights

In the afternoon chat, @jeffpaul led off with the RC 2 release post above, and it is indeed worth a second read, if you’re so inclined.

Other posts of note:

The 5.8 Field Guide is out. Docs lead @milana_cap has done a masterful job of pulling it all together. So if you’re getting a theme or 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 ready for 5.8, the Guide is your most reliable source of timely, topical information on the changes that will affect your products and the processes you use to get them out the door.

Catch up on the latest feedback the Full Site Editing crew has received with this post from @annezazu. And while we’re at it, here’s the FSE team’s latest chat summary.

And @audrasjb is back with another Week in Core, celebrating 52 contributors (five who are brand-new!) and nine committers who got things going this week.

@jeffpaul thanked the authors and everyone who commented or otherwise helped share news or knowledge this past week and shared this reminder:

We are now in the RC period. That means we’re in a hard string freeze, and the final planned release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)., RC 3, is now just FIVE days away, on July 13. The 5.8 release is TWELVE days away, on July 20.

(Ed. note: Where has the year gone?)

With no seemingly urgent business connected to the release (see @desrosj on the state of the milestone, above) @jeffpaul referred the group to a post from @mapk on care and influence in the WordPress community.

Components check-in

@sergeybiryukov reported in on Build/Test Tools. Referring the community to this ticket on PHPUnit 8.x, he described the challenges that come with adding support for PHPUnit 8.x and 9.x, since they’re not compatible with versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher older than 7.1.

@marybaum commented that Help/About is looking good and then took a minute to thank all the people involved with the About page.

Open Floor

Pivoting from @sergeybiryukov‘s discussion of PHPUnit 8.x and 9.x, @azaozz opened a discussion of when WordPress might stop supporting PHP versions earlier than 7.1. The upshot, according to @sergeybiryukov: WordPress ends support for a PHP version when it’s running fewer than 5% of sites. At the moment, 8.83% of WordPress sites run PHP 5.6, and 5.23% are running on PHP 7.0.

Marketing Rep and Help/About co-maintainer @webcommsat would like to know what your favorite 5.8 feature is, so the Marketing team can write some social-media posts about it. You can share your favorites with her or @marybaum directly or in threads on this week’s marketing meeting, which run asynchronously through Friday.

@webcommsat would also like some more posts on key features in the release. To add one or more, use the commenting feature in this Google Doc.

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

Dan Farrow 4:34 pm on June 28, 2021
Tags: , summary   

CSS Chat Summary: 24 June 2021

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

Housekeeping

Discussion: Custom Properties (#49930)

hsl colours exploration

--wp-admin--color-neutral-h: 0;
--wp-admin--color-neutral-s: 0%;
--wp-admin--color-neutral-l: 100%;
--wp-admin--color-neutral-hsl:
   var(--wp-admin-color-neutral-h),
   var(--wp-admin-color-neutral-s),
   var(--wp-admin-color-neutral-l));
  • @ryelle pointed out that, as the WordPress colour palette doesn’t follow hsl we would need 3 distinct variables for each colour
  • @colorful-tones expressed a wish to see the core palette streamlined to the central column of colours and then for the other values to be generated using hsl variants using a core set of custom-properties, or new colours altogether
  • @ryelle reported having explored implementing dark mode by inverting colour values e.g. neutral-100 becomes neutral-0, but the results were unsatisfactory
    6
  • Perhaps the upcoming lch CSS colour feature will more readily enable this kind of approach

Crossover with editor (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/) custom-properties

  • @joyously asked if the custom-properties would apply to the UIUI User interface editor, and if the custom-property naming would follow the same convention
  • @ryelle clarified that currently the editor generates custom-properties like --wp-admin-theme-color for each colour scheme. These properties names will hopefully eventually converge with the new Custom Properties we are proposing

Performance

  • @joyously & @colorful-tones wondered if a large number of custom-properties could slow down browsers
  • @ryelle suggested that unchanging custom properties (which ours will mostly be) are less likely to have a negative impact

Workflow

  • @notlaura had asked about @ryelle’s workflow for adding custom properties has been. @ryelle clarified that she has been going through the values in common.css
  • As a way forward to working collaboratively on the PR she suggested each claiming a different file to work through

Cascading custom properties

  • @joyously asked if having many :root level properties is better than having a smaller number of properties which are then overwritten with specific selectors for each location
  • @ryelle responded that she would like to see how an inheritance based system would work
  • @danfarrow observed that the PR uses a form of inheritance by populating some properties with the values of others e.g. --wp-admin-menu--link--background--hover: var(--wp-admin-menu--background);
  • @ryelle explained that this will allow adminadmin (and super admin) schemes to set as few variables as possible, but also have the ability for more granular control if they need it
  • @joyously clarified that she was thinking more of “a small set of properties that are set for each class representing an area of the page”

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

David Smith 10:48 am on June 24, 2021
Tags: , , , summary   

Editor chat summary: 23rd June 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-06-23 14:00 UTC in Slack. Moderated by @get_dave.

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/ 10.9 PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party release

WordPress 5.8 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3

  • 22nd June 2021 saw the release of WordPress 5.8 Beta 3.
  • It was noted that there is still time for 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 documentation to be written.
  • @desrosj explained that there is a 4th (unscheduled) Beta planned for later this week (likely Thursday or Friday) – if there are additional things you’d like to see get tested during the beta cycle (and not after RC), there’s still time to get those in.
  • The project board for Gutenberg and WordPress 5.8 still has outstanding items needing contributors.
  • Due dates for dev notes – the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is published on the same day as RC 1, which is this upcoming Tuesday. Ideally, all 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. should be in by then. If there are any notes that will not be ready, they can be added to the guide after publish, but having them for that date is preferred.

Key Project updates

Updates were requested for the key projects:

Native Mobile Team

@mattchowning provided the update:

Shipped

  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native 0.64.x upgrade, including upgrade to React v17!

Coming Soon:

  • 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. refactor
  • Tooltips to help with Editor Onboarding

In Progress:

  • Further Editor Onboarding improvements: a help section and a “new” badge for new blocks
  • Starting work on improving the integration tests for mobile so mobile breakages are caught earlier
  • Block inserter search
  • Embed block
  • Global Style Support for colors

Global Styles

@nosolosw provided the update async:

Current focus is polishing the theme.json experience by finding and fixing bugs that are backported to the Betas weekly.The two major things left are:

  • Show preset strings provided via theme.json in translate.wordpress.org so they can be translated. This depends on a new wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ release (see) and then updating the 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. infrastructure. Trac ticket.
  • Publish dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for theme.json (I’m working on this).

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

@andraganescu provided the update.

Navigation Block

@mkaz provided an update:

  • Color overlay issues being worked and continued improvements.
  • It looks like the markup has been confirmed so will need review on the open PR to move it forward

Navigation Editor screen

@get_dave provided an update:

Full Site Editing

  • @aristath suggested that we stop using FSE as a term, and eliminate it from code whenever possible. We should use “block based” or similar instead.
  • @annezazu mentioned that template editing mode is officially opt in for classic themes and opt out for block themes for 5.8. You can see the dialogue here and you can see the PR for this here.
  • @annezazu flagged the FSE Outreach program is going to launch a call for testing/exploration around 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. tomorrow rather than today. You can see the full schedule here for June/July.

Task Coordination

@ntsekouras:

@annezazu:

  • I was out last week – still playing catch up.
  • Hyper focused on the FSE Outreach program.
  • Working on the theme.json call for testing with a few folks
  • Nearly done with the seventh call for testing summary post.
  • Shared a reflection previously on future programs (thoughts welcome).
  • Starting July 1, I’ll be focusing in as much time as I can on user docs for 5.8.

@mkaz:

  • Looking at Dev Notes for WP 5.8, the tracking issue is here.
  • The three major dev notes that I see left are:
    • Widgets Editor
    • Global Styles
    • Block 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. & registration
  • @gziolo already has a draft of the Block API note that I hope to review and publish this week. 
  • @andragan and @nosolosw are working on the other two: Widgets & Global Styles.

@get_dave:

@aristath:

  • WP 5.8 – working on improving styles & scripts loading and there are no blockers
  • We should stop using FSE as a term, and eliminate it from code whenever possible (see note above).

@zieladam:

  • I am getting back into the rhythm of contributing after my 6 months break (during which I explored data science in Tumblr).
  • Mostly going through the Widgets editor board and reviewing/submitting new PRs and refreshing my memory of how everything works.

Open Floor

Saving Flow Consistency (agenda comment)

  • @paaljoachim asking about saving flow consistency across various screens.
  • He’s made a detailed overview Issue and he feels “…it would be helpful to get this fixed for WP 5.8, so users who want to discard a save does not meet these errors.“
  • Is anyone able to take a look into this? Please let us know in the comments.

“Final call” for input on the transform vs convert debate for Block Transform API

Feedback about Block based Widgets screen

Note: this has subsequently been converted into an Issue and added to the Widgets project board.

Request for pull request approval: filters to get block templates functions

Problems testing Theme JSON for Classic Themes

  • @colorful-tones is eager to test leveraging just the theme.json for classic theme (or more like hybrid) approach.
  • Saw PR #32858, but not entirely certain how to test and verify. Should I be running latest Gutenberg plugin and latest WP Beta 3, or just latest Gutenberg? 
  • @annezazu provided advice:

@colorful-tones I might recommend asking directly on the PR to be extra safe. From what I can see to test this, you need to use WordPress 5.7 and the specific 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". that this PR is on.

Anne McCarthy

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Japan Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. successes

No blocks in inserter on Widget screen with empty Widget area

Wrap up

It was great to hear/see so many voices in the Open Floor section.

Thanks to everyone who attended.

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