CSS Chat Summary: 28 January 2021

Housekeeping

@paaljoachim suggested that the bi-weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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 alternate between TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets & Gutenburg 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/ issues
@tellthemachines agreed & suggested triaging issues under the CSS styling label
@notlaura suggested doing this at the next bug-scrub which is scheduled for 11th February

@ryelle reported that the CSS Audit report is now updating & being generated automatically with changes to core – the automated commits reveal changes to core CSS as they happen
@notlaura suggested generating the report as JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. first, to enable changes to be tracked over time, to which @ryelle suggested adding a second action that generates a JSON report
@notlaura observed that this news will be a great update to add to the CSS audit ticketticket Created for both bug reports and feature development on the bug tracker.

@ryelle reported that her reduced colours PR has been merged into core
@ryelle has also published a PostCSS plugin & workflow that can be used by devs to automate the colour replacement
The number of unique colours has reduced from 199 to 98. @ryelle suggested that the next step would be to replace these with custom properties
This initiated a tricky-to-summarise discussion about naming which led into ideas of how to facilitate a wider discussion
@notlaura suggested a Make post inviting conversation, to align with global styles & editor design system initiatives. @tellthemachines agreed that a Make post would attract wider contribution, and @kburgoine offered to write the post [UPDATE: the post is now available here – great job @kburgoine!]

@tellthemachines reminded us that her PR is still open & has received some review feedback
She plans to add more tests in the coming week, followed by tests for mobile breakpoints
She is also considering the basis on which the tests should be automated with Github Actions

@kburgoine shared a link to the Open Collective’s Open Web Docs project, an amazing initiative to manage funding & growth for web documentation platforms, currently prioritising MDN Web Docs

Thanks everybody!