CSS Chat Agenda: 16th July 2020

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, July 16, 2020, 5:00 PM EDT.

This 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

CSS audit status updates
- What is the purpose of recurring reports, and what data is useful in recurring reports?
Color scheming updates
- Is it useful to distinguish custom properties implementation work in ticketticket Created for both bug reports and feature development on the bug tracker. #49930 and #4999 is ongoing iteration and naming exploration?
- Review screenshots annotations with an option for naming (#4999)
- What data do we need to generate a color scheme? e.g. @mixin adminadmin (and super admin)-scheme($color-primary) – the lightness/darkness values for all color schemes will not be the same, so we need to pass more information to the mixin.
CSS Latest and Greatest Link Share
Open floor

#agenda, #core-css

tellthemachines 7:25 am on July 16, 2020
Not sure I’ll make it to the chat tomorrow, so leaving my comment here on the recurring audit reports topic:

I think the main purpose of these reports would be to check on the health of our CSSCSS Cascading Style Sheets. code regularly. To that effect, we should be checking things like:
- new values for e.g. colors, margins, etc. are being introduced as little as possible;
- avoiding use of px units;
- specificity isn’t increasing.
For some of these, we might be able to leverage stylelint, but with the current state of the codebase it would require adding disable comments in too many places, or else a major refactor 😁
For checking values @ryelle‘s css audit tool is definitely the best candidate. I think we should use it to do the whole report, and then add stylelint when the code is in a better place. (The main advantage of stylelint vs periodic reports is it can be used for real time checking, so that sub-optimal code need never be committed.)
- Lara Schenck 8:45 pm on July 16, 2020
  
  Excellent, thank you @isabel_brison – we will be sure to discuss these points!

Comments are closed.

Welcome!

Communication

Share this:

Site resources