CSS Chat Summary: 03 June 2021

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

Housekeeping

• @danfarrow offered to run the next bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub (01 July @ 20:00UTC) – thanks me!

Project updates

Color Scheming (#49999)

• We now have a public shared doc in which to begin documenting naming conventions for custom properties
• @colorful-tones noticed that #49999 doesn’t have a link to the Make posts about the project. @notlaura suggested adding a link to the Introducing CSS Custom Properties Make post, as well as the current status of the project
• @colorful-tones initiated a discussion about the choice of hexadecimal colour definitions vs RGB(a) and/or HSL(a). This has been discussed on several previous occasions (e.g. by me a year ago today!) and circles back to this comment from @joen:

HSL works but it would force us to have an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. based on HSL colors, we want to have a more generic API where users just define a single variable.

CSSCSS Cascading Style Sheets. Audit (#49582)

• @danfarrow reported having made progress on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ actions to autogenerate the report. There are now two actions, one to merge updates to trunk into the report branch (which appears to be working), and the Build Report action which now generates the report once a day from the report branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. TBC if it now works as expected…
• @colorful-tones offered to add a link to the CSS Audit report into the CSS Coding Standards docs [UPDATE] Now done, thanks @colorful-tones!

CSS deprecation path (#53070)

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

Open floor / CSS link share

• @colorful-tones shared a CSS-Tricks article Are Custom Properties a “Menu of What Will Change”? which resonates with the goal of creating a scalable CSS API for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. custom properties
• @colorful-tones expressed a strong desire to see Sass removed from core blocks and suggested a future discussion. @notlaura agreed that it could go on the agenda for a future meeting and suggested a Make post outlining the proposal. Example Make post proposals include Proposal: a new color palette for WordPress & Proposal: Test Badges for the FSE Outreach Program

Thanks everyone!

#core-css, #summary