CSS Chat Agenda: 28th May…

CSSCSS Cascading Style Sheets. Chat Agenda: 28th May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 28, 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 update
  • Color Scheming Updates
  • Open floor

#agenda, #core-css

CSS Chat Summary: 21st May…

CSSCSS Cascading Style Sheets. Chat Summary: 21st May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1590094908056800

I (@notlaura) facilitated the meeting.

CSS audit updates

@isabel_brison had a couple of questions, and we clarified some items mentioned in the report outline:

For “List of unique values for each of a list of properties, and number of occurrences:” we discussed that margins, padding, top/left/bottom/right, transforms, and typography related properties would be useful for standardizing our units of measurement. @ryelle‘s audit tool would certainly be useful for that.

The other question was to do with the item “Units: instances of px/em/rem/%age and count of use with properties”. We discussed that that should be limited to areas that affect responsive/zoom behavior, or properties where px unit are used but and probably shouldn’t be. Extending this to more than those cases might be beyond the scope of the audit and difficult to automate. Part of the original intent of that item was to identify “brute force layout”, but we discussed that basically the entire wp-adminadmin (and super admin) is brute force layout and auditing that would require manual inspection. Also, that is a subjective item and perhaps a conversation more appropriate for a CSS coding standards discussion after following the audit.

Color Scheming Update

@kburgoine has been doing lots of prep work and reading through historical tickets to get a good understanding of the problem with the current color schemes. She mentioned that the most pressing issue is not necessarily backwards compatibility, rather, the number of colors in use.

We discussed some more about design tokens, and I updated that I elaborated on my idea for the implementation in @ryelle‘s Gutenberg PR, and in a new comment on the “Iterating on Admin Color Schemes” ticketticket Created for both bug reports and feature development on the bug tracker..

I also mentioned some recent activity on the ticket for Dark Mode – which is potentially a conversation we can participate in since the intent behind re-vamping color schemes it to be able to support something like Dark Mode.

Open Floor

@peterwilsoncc jumped in at the end with a question about #46090 and including the X-UA-Compatible headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. for IE detection.

That was all for this week!

#core-css #summary

CSS Chat Agenda: 21st May…

CSSCSS Cascading Style Sheets. Chat Agenda: 21st May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 21, 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 update
  • Color Scheming Updates
  • Open floor

#agenda, #core-css

Chat Summary: 14th May 2020…

Chat Summary: 14th May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1589490207487100

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

@isabel_brison ran a check for dead code using Purge CSS (and there’s not too much of it!) and added results to the Google Doc.

We discussed running checks on CSS in wp-includes as well as in wp-adminadmin (and super admin), and that seems like a good idea. @isabel_brison mentioned there is some inline CSS in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files – including some inline !importants 🥺. It seems like a useful data point for the audit to include a list of non-CSS files that contain CSS so we can flag those instances for improvement later, and I added that to the Google Doc.

Color Scheming Updates

I added a comment to the Iterating on Color Schemes Trac ticket with some details on how design systems handle theming with abstractly named tokens, and added a few comments to @ryelle‘s Gutenberg PR that contains a prototype for color schemes using PostCSS themes. We discussed the importance of determining an approach for browser support and getting some experiments started early.

wordpress/postcss-plugins-preset

@kburgoine asked about a default PostCSS setup for WordPress which led nicely into this agenda item. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor team requested feedback on this PR adding support for building CSS in the wp-scripts package.

WCEU Online Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor day will be held online on June 4. It is an opportunity to contributors know about #core-css since it is a new group, and we could create a short list of tasks new contributors can help with on the CSS audit, or perhaps point them to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ CSS tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). I volunteered to find out some next steps for this.

That was all for this (last…) week!

#summary #core-css

CSS Chat Agenda: 14th May…

CSSCSS Cascading Style Sheets. Chat Agenda: 14th May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 14, 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!

#agenda, #core-css

Chat Summary: 7th May 2020…

CSSCSS Cascading Style Sheets. Chat Summary: 7th May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1588885269423200

I (@notlaura) facilitated the meeting.

CSS audit updates

It’s not specifically part of the audit inititive, but let’s celebrate: CSS for unsupported IE versions was removed in commit 47771. 🎉

Color Scheming Updates

@ryelle experimented with custom properties for color schemes in a Gutenberg PR and left comments on the Iterating on Color Schemes ticketticket Created for both bug reports and feature development on the bug tracker., and mentioned that @nrqsnchz & @joedolson will be working on the design and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) side of color schemes.

Also for reference is the Dark Mode project which was not merged due to the difficulty in overriding CSS in parts of the adminadmin (and super admin). Part of the work to do regarding the color schemes initiative is to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it so that we can have dark mode, and a solution that allows control of all colors in the admin.

I mentioned the design systems practice of abstracting colors (the design tokens) into contextually named custom properties, and offered to add a comment to the ticket.

That was all for this week!

#summary #core-css

CSS Chat Agenda: 7th May…

CSSCSS Cascading Style Sheets. Chat Agenda: 7th May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 7, 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 update
  • Color scheming update
  • Open floor

#agenda, #core-css

CSS chat summary: 30th April 2020

Full meeting transcript 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/.: https://wordpress.slack.com/archives/CQ7V4966Q/p1588280435384600

I (@isabel_brison) facilitated the meeting. 

CSSCSS Cascading Style Sheets. audit updates

I reviewed and helped to update a patch for removing ie7/ie8-specific styles.

Color scheming updates

@ryelle created a ticket for discussion of current color scheme limitations and improvements needed. It has been brought to the awareness of the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team, and we agreed to ask the design team for input too. The goal is that this be a cross-team project to create color schemes with different accessibility features.

Call for volunteers

Is anyone keen to help @notlaura and myself with running this weekly chat? It would be great to have someone else, even if only to step in occasionally when neither of us can makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it.

@ryelle has kindly volunteered to help with note-taking.

That was all for this week!

#core-css, #summary

CSS Chat Agenda: 30th April 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for 30th April, 21:00 UTC.

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!

Agenda

  • CSS audit status update
  • Color scheming status update
  • Open floor

#agenda, #core-css

Chat Summary: 23th April 2020…

Chat Summary: 23th April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1587675646270300

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

No CSS audit updates this week.

Color Scheming status update

I proposed having this as a recurring agenda item since it is a long term and far reaching initiative – meeting attendees were in agreement that it should be.

@kburgoine created the ticketticket Created for both bug reports and feature development on the bug tracker. “Replace wp-admin color schemes with CSS custom properties” #49930 and mentioned there hasn’t been much traction. We discussed possible next steps for the ticket. @ryelle mentioned a need to break down the need for color schemes, and @kburgoine mentioned researching and outline some potential approaches, perhaps with proof of concept Codepens and some prototypes.

@ryelle indicated that the root issue might be that we need a different approach to color schemes and that custom properties might be part of the solution, but not the whole thing. There are currently has 206 unique colors in wp-adminadmin (and super admin), and the current implementation of color schemes requires any overriding of default colors to be just as specific. To summarize this message, standardizing colors and switching them all to custom properties would remove the need for color scheme authors to write new CSS to override the default colors. So, specificity resulting from the current color scheme handling is an issue. @isabel_brison suggested that a ticket to track the current issues with color schemes would be useful.

@netsassprodsr asked about IE support, and @isabel_brison mentioned that we would need some sort of flagging / indication to users what color schemes are IE friendly.

I outlined a couple of next steps for the color scheme ticket based on the conversation:
1. research/list some problems that are caused due to the current color scheme implementation
2. research/list some approaches for colors schemes in the ticket

@ryelle offered to take on #1 and to create a ticket for it if one doesn’t already exist.

Open Floor

@isabel_brison has created a label in the Gutenberg repo for CSS issues – very cool! This will hopefully be helpful for folks who want to contribute to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ with their CSS skills.

That was all for this week! @isabel_brison will be filling in for me and facilitating the next CSS chat on 30 April.

#summary, #core-css