Full meeting transcript here on Slack. @notlaura facilitated the meeting.
Reminder that @kburgoine will be leading the biweekly core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS Cascading Style Sheets. bug 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 next Thursday, October 22, one hour before the CSS Chat meeting.
@ryelle reported her progress of having written up an issue about adding configuration file support to her CSS Audit tool, to which @notlaura reported having been prompted by the issue to begin work on the feature!
The generated reports are now accessible as Github 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/ pages (here for example). @ryelle observed that eventually this tool should be migrated to the WordPress github repos.
@notlaura mentioned that a comment about report generation should be added to the Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker., for community reference and put a call out for a volunteer to do this, specifying:
the key items to include in a comment are the link to the generated report (https://ryelle.github.io/css-audit/public/wp-admin) and the next steps, which are to complete the data (missing property values) and to style the template
Color Scheming (#49999)
@ryelle reported that she has kept her reduced-color branch testing site up-to-date with WordPress trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. There followed a short discussion about the pros and cons of proposing to merge the branch 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". into the 5.6 beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. @garrett-eclipse suggested seeking a champion from #design, otherwise punting it to 5.7, which, @ryelle observed, would allow us to focus on bug-scrubbing & Twenty Twenty One issues over the coming weeks.
CSS links share + Open floor
@danfarrow (me!) shared a link to a portfolio site ichimnetz.com which has a quirky “adjust CSS” slider feature which demonstrates the effect of using more or less CSS.
@danfarrow also shared an informative recent CSS Tricks article about media queries which includes a reference to a browser feature forced colors mode:
Some browsers will limit the number of available colors that can be used to render styles. This is called “forced colors mode” and, if enabled in the browser settings, the user can choose a limited set of colors to use on a page. As a result, the user is able to define color combinations and contrasts that make content more comfortable to read.
And, with that, the meeting was concluded. Thanks everybody!