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

CSS Chat Agenda: August 26, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is Thursday, August 26 at 21:00PM UTC in the #core-css channel in Making WordPress Slack.

CSS Custom Properties (#49930)

Focused on substituting existing colors throughout CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets, the CSS Custom Properties project aims to make working with Adminadmin (and super admin) Themes & Admin Color Schemes easier and more reliable both in Core and Plugins.

The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here). No prior contributing experience is required — we’re happy to assist anyone who would like to participate! This meeting we will continue with work and collaboration, time permitting.

Meeting Agenda

  • Welcome (21:00PM UTC)
  • Announcements & Housekeeping
  • CSS Custom Properties (#49930)
    • Overview & Updates
    • How to Get Involved
    • Status Check-In & Blockers
  • Work & Collaboration (time permitting)
  • Open Floor
  • CSS Link Share (Bring neat examples & helpful tools!)

#agenda, #core-css

CSS Chat Summary: 19 August 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Working Time

  • @robertg has taken on src/wp-admin/css/customize-controls.css which 2900+`lines of CSS. Bon courage Robert!
  • @wazeter has looked at other contributors change files in order to see how others have approached the problem, which seems like a sensible approach

CSS Link Share / Open Floor

Thanks everyone!

#core-css, #summary

CSS Chat Summary: 12 August 2021

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

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

   --wp-admin--theme--primary--step-10: #1a5686;
   --wp-admin--theme--notification: #d63638;
   --wp-admin--theme--notification--contrast: #fff;
   --wp-admin--theme--success: #00a32a;
   --wp-admin--theme--info: #72aee6;
   --wp-admin--theme--warning: #dba617;
   --wp-admin--theme--error: var(--wp-admin--theme--notification);
  • @robertg asked a question about where new custom properties should be defined. @ryelle answered that they should be in custom-properties.css, in the body selector so that they can be overridden by colour themes later

How should box-shadows be handled?

Working time

  • @notlaura started the 20 minute session where contributors can work on the project while having help available in the 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
  • @robertg asked if the :hover and :focus pseudo-classes should have separate custom-properties. @ryelle answered that one custom-property can be defined for --hover and also used for :focus
  • @wazeter asked about the timeline. @notlaura replied that for the 5.9 release we would be aiming for the end of August. @ryelle clarified that this is the target for “early“ consideration. We’ll know the target for the completed project when the real cutoff has been announced but she expects it to be around early-mid October
  • @notlaura added that next week’s meeting (August 18) is the last scheduled week for working time
  • @wazeter asked where questions about quirks should be addressed. @notlaura replied post in the #core-css channel or comment in the PR
  • @robertg asked if we are just targetting color, background-color, and border-colors for now. @notlaura added box-shadow, noting that this will need some additional discussion

CSS Link Share / Open Floor

Thanks everyone!

#summary

CSS Chat Agenda: August 19, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is Thursday, August 19 at 21:00PM UTC in the #core-css channel in Making WordPress Slack.

CSS Custom Properties (#49930)

Focused on substituting existing colors throughout CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets, the CSS Custom Properties project aims to make working with Adminadmin (and super admin) Themes & Admin Color Schemes easier and more reliable both in Core and Plugins.

The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here).

No prior contributing experience is required — we’re happy to assist anyone who would like to participate!

Meeting Agenda

  • Welcome (21:00PM UTC)
  • Announcements & Housekeeping
  • CSS Custom Properties (#49930)
    • Overview
    • How to Get Involved
    • Status Check-In & Blockers
  • Open Floor
  • Working & Collaboration Time
  • Huddle Up & Closing Discussion (21:50PM UTC)
  • CSS Link Share (Bring neat examples & helpful tools!)

#agenda

CSS Chat Agenda: August 12, 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday August 21 at 21:00PM UTC. The 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/..

This week, we will be continuing with a supported working session for new contributors! Please see this post with our call for contributors and more details. Our agenda is as follows:

  • Welcome
  • Housekeeping
  • Discussion around the CSS Custom Properties project (#49930)
    • Brief Overview
    • How to Get Involved
  • Open Floor
  • Working Time
  • 21:50PM UTC – Circle back, closing discussion, CSS link share

#agenda, #core-css

Dev chat summary, August 11, 2021

@sergeybiryukov stepped up to lead this agenda-less meeting. Big thank you!

Highlighted blogblog (versus network, site) posts

From @audrasjb, another A Week in Core post highlights the moving parts of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and recognizes a week’s worth of contributors at a time.

From @sarayourfriend provides an update on the native TypeScript proposal announcing that 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/ project supports native TypeScript.

From @notlaura comes a Call for CSS Contributors, a carryover and reminder from last week. Their next weekly work session is August 12, 2021 at 21:00 UTC in #core-css.

From @chanthaboune, participate in the WordPress 5.8 ‘Tatum’ Retrospective. Feedback is due on August 15th and is greatly appreciated to make future releases even better.

From @webcommsat comes a helpful post for spreading the word about 5.8. In this post, you will find social posts you can share and adapt on Twitter and Facebook.

From @annezazu, follow the latest call for testing through the FSE Outreach Program. It’s focused on using the navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. to build out a HigherEd themed 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. with three weeks to share you feedback.

From @annezazu comes a reminder to help shape the future of theme design. If you’re a block theme author or have explored that space, please share your responses by August 15th and know they are each greatly appreciated. 

Finally, catch up with the previous episodes of WP Briefing. The podcast will return in September!

Component maintainers

Reporting in on Build/Test tools, @sergeybiryukov shared that, as of last weekend, WordPress test suite is compatible with PHPUnit 8 & 9, and runs tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 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. (scheduled for release in November). Props to @jrf and @hellofromtonya for all the fixes and improvements that made it possible!  See ticketticket Created for both bug reports and feature development on the bug tracker. #46149 for more details.

Reporting on Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks, @sergeybiryukov said that there’s no major news this week.

Reporting on General, @sergeybiryukov shared that work has started on making various compatibility fixes for PHP 8.1. Thanks @jrf, again!  See ticket #53635 for more details.

Open Floor

Considering #49728 for the 5.9 release. Raised by @hareesh-pillai.

Since the topic of compatibility with the latest PHP versions came up, Hareesh flagged that it would make sense to include this additional ticket after it was pushed from 5.6.

Next step: @hellofromtonya moved it to the 5.9 milestone.

Invitation to contribute to testing. Raised by @hellofromtonya.

Anyone interested in contributing to testing including attempting to reproduce problems, gathering testing information (such as testing steps, acceptance criteria, dependencies), user testing, and automated testing, you’re invited to join us in #core-test channel.

Checking in on a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. related to 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 folks finding issues with PHPUnit updates. Raised by @jeffpaul.

@hellofromtonya and @jrf quickly chimed in to say that a dev note is in progress with an ideal publish date of next week. The quick TL;DR is:

  • Fixture methods changed in the WP test cases, i.e. changed to snake_case
  • Wrappers for the snake_case will be backported for extenders who are testing against versions other than 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..
  • Once those backports happen, then the fixture methods in your tests need to be updated for testing against trunk.

To help extenders, command-line messages will be added as well to alert and guide devs.

Bumping the ACCEPTABLE_PHP and SUPPORTED_PHP versions in light of PHP 7.3 support ending in 3 months. Raised by @hareesh-pillai.

@sergeybiryukov recommended that this be raised as a discussion topic in the next #core-site-health meeting. He also shared that he felt it was a bit too early to bump the recommended version to PHP 8.0, as there is still ongoing work to make it more compatible.

#dev-chat, #summary

CSS Chat Summary: 05 August 2021

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

Housekeeping / Custom Properties (#49930)

@Dave Ryan gave a shout out to the Call for Contributors with this great introduction to the project:

If you or anyone you know loves CSSCSS Cascading Style Sheets. or loves WordPress, we’d love some additional pairs of hands to work on the CSS Custom Properties project that’s targeted for an experimental release in 5.9 and a stable release in 6.0!

For context, this project is to replace hard-coded colors in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets with CSS Custom Properties!

This transition will make it safer and easier to override default colors in the WordPress Adminadmin (and super admin)

It opens up potential for things like an official Dark Mode (or easier-to-implement for 3rd parties), easier inheritance of Core styles in 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 wp-admin screens, custom color schemes, custom branding and more!

CSS Link Share / Open Floor

@Dave Ryan shared four great links:

Working time

The last 20 minutes of the meeting were dedicated to individual working time on the Custom Properties project, after which @Dave Ryan closed proceedings.

Thanks Dave for running this week’s chat!

#core-css, #summary

CSS Chat Summary: 29 July 2021

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

Housekeeping

Custom Properties (#49930)

  • @notlaura shared her draft Make post calling for contributors. UPDATE: The post has now been published here!
  • @Dave Ryan shared a note from his PR about the need for some common colour values – more discussion needed on this
  • @ryelle gave an update on her recent progress:
    • common.css has been updated and pushed to the try/custom-properties 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".
    • Making PRs to try/custom-properties is a great way for contributors to add their contributions
    • She is keeping try/custom-properties up-to-date with master
    • Anybody can give feedback on any PRs in that repo
  • @Dave Ryan asked if fallback values should be provided as he’s seen some changes that use them and some that don’t. @ryelle clarified that she had used them in admin-bar.css as adminadmin (and super admin) color schemes don’t apply to the frontend, so the custom properties may not be defined. @Dave Ryan pointed out that the same reasoning applies to the login page too
  • @notlaura suggested that the next few meetings which have work sessions should begin with a quick check in for updates & housekeeping and then straight into the work session

CSSCSS Cascading Style Sheets. Link Share / Open Floor

Thanks everyone!

#core-css, #summary

Call for CSS contributors! Help implement custom properties in WP Admin.

WordPress needs your CSSCSS Cascading Style Sheets. chops!

In #core-css, we have been working for over a year to devise how to implement custom properties for WP Adminadmin (and super admin) in order to allow extended flexibility of color schemes, e.g. dark mode and high contrast. After much deliberation, research, and prototyping, we are now going forward with replacing the current color scheme implementation with custom properties as outlined in ticketticket Created for both bug reports and feature development on the bug tracker. #49582, and we need some help!

If you’d like to get started on your own or learn details about this work, we are keeping track of our workflow and collecting information that will serve as future documentation in this Google Doc: WordPress Core CSS custom properties.

Join our Custom Property Work Sessions

We also know that it can take time to understand the nuances of a project enough to contribute, it can be intimidating, and it can be hard to designate the time for it. That’s why we are devoting the next three weekly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS Chats to work time and “office hours”, where experienced folks will be available to help with any issues in 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/..

The dates and times for the CSS Chat: Custom Property Work Session editions of the weekly meeting will be:

  • August 5, 2021 at 21:00 UTC
  • August 12, 2021 at 21:00 UTC
  • August 19, 2021 at 21:00 UTC

Excellent Opportunity for New Contributors

This is a great opportunity to get involved with contributing code to WordPress! The knowledge you’ll need for contributing is:

  • Ability to fork and clone a repo from GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ and create your own 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".
  • Run commands to start the WordPress development environment
  • Read CSS selectors from a file and find what they refer to in the DOM
  • Understanding of CSS custom properties (a.k.a. CSS variables) syntax

Some helpful links for where to obtain this knowledge:

That said, this knowledge is not required for attending the work sessions. If you run into an issue or have trouble following the doc above, just ask in Slack during one of the meetings, and someone will help.

We hope you will join us to help advance and maintain WordPress’ core stylesheets!

#core-css