CSS Chat Summary: 3 September 2020

See the full meeting transcript here on Slack. I (@notlaura) facilitated the meeting.


We need someone to lead the weekly meeting on October 8 – send a message on 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/. to @laras126, or comment on this post if you are able to do that!

@ryelle added @here privileges for herself and @kburgoine so they can lead the 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. The bug scrubs / triages will be every other week one hour before the meeting (at 4pm EDT), and @ryelle will lead the next one this Thursday, the 10th.


CSSCSS Cascading Style Sheets. Audit (#49582)

I added an issue to the CSS audit repo and corresponding comment to the ticketticket Created for both bug reports and feature development on the bug tracker. about storing the audit data on 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/ instead of in a Google doc. @ryelle agreed this sounded like a good idea, especially deployments via Github pages, and potentially using Github action to regularly re-build the report. Another idea we talked about is a method to download a specific version of WordPress to run the audits on, so that we don’t have to worry about environment-specific artifacts (e.g. the .orig files from SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. conflicts).

Color Scheming (#49999)

A big week for color scheme updates! @ryelle is close to finished with the PostCSS 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 will replace the rogue colors with the approved coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. colors – visualized here. She opened a PR to the WordPress-develop repo that includes screenshot comparisons of the color replacements, and indicated next steps to be:

  1. Finish the transparent color handling
  2. Start the manual work of cleaning up anything that looks awkward after the processing
  3. Maybe add some way of ignoring certain colors/selectors/files

Related to the second item – there will be small issues that require manual review, for example, there is no orange in the color palette, so they have been replaces with reds, and another area where a specific light blue background was removed. We will need input from designers to validate these changes. Rather than adding issues based on screen or color for the review, we discussed having a Make post and allowing people to comment before deciding on a specific review structure.

Open Floor + CSS Link Share

@ryelle shared an enticing Tweet from someone attending Clarity Conf:

I shared the @property syntax where, in CSS only, you can declare custom properties with more details:

@property --colorPrimary {
  syntax: "<color>";
  initial-value: magenta;
  inherits: false;

CSS! 🔥

#core-css, #summary