CSS Chat Summary: 20 May 2021

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

Project updates

Color Scheming (#49999)

  • We discussed some next steps for the project:
    • Document the naming scheme well enough that anyone can create consistent variables
    • Start splitting up some CSSCSS Cascading Style Sheets. files to create variables with --experimental
    • Start design (or at least exploration) for the new color schemes
  • @ryelle shared some initial custom property names based on the contents of common.css and an associated PR where comments can be posted
  • We discussed where the custom property names & methodology should be documented
  • @notlaura summarised the next steps:
    • Start writing naming documentation in a Google doc
    • Review / experiment / iterate in @ryelle’s PR
    • Update doc draft as standards emerge

CSS Audit (#49582) & CSS deprecation path (#53070)

  • @notlaura has published the Make post announcing the project
  • We speculated as to where else it could be linked from to improve visibility. @notlaura suggested the CSS Coding Standards //Best practice// or //Related links// section
  • @danfarrow reported having merged a PR from @colorful-tones which adds a link back to the GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ project page into the CSS audit HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. report
  • Changes in the 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". need to be automatically pushed into the report branch. @danfarrow volunteered to look into this in an attempt to “get his head around” GitHub actions 🙂
  • @notlaura suggested keeping the project in the meeting agenda for the next couple of weeks, a suggestion which was met with approval

Open floor / CSS link share

  • @ryelle wanted to put a call out for tickets with patches as she is planning a push to review & commit tickets early next week [UPDATE The push has now been & gone]

Thanks everyone!

#core-css, #summary