Tag Archives: summary

Lara Schenck 3:47 pm on June 5, 2020
Tags: , summary,   

CSS Chat Summary: 4th June…

CSSCSS Cascading Style Sheets. Chat Summary: 4th June 2020

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

I (@notlaura) facilitated the meeting.

Acknowledging Racial Injustice

I didn’t feel comfortable leading our usual meeting without explicitly acknowledging the racial injustices that have lead to the Black Lives Matter protests in the US and around the world. I invited meeting attendees to converse in a thread during the meeting, if they wanted.

CSS audit updates

I update the Google Doc with the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 files that contain CSS, and we discussed how to approach the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files that contain CSS, and what specifically to note about the styles in PHP. @kburgoine suggested to focus on any CSS that includes colors and units of measurement that may change in the future.

Color Scheming Updates

Next week, we will have an agenda item to discuss color naming conventions with the design team, but we did have a cursory discussion this week.

@ryelle has been experimenting a PostCSS plugin she mentioned last week that will pull out all colors and replace them with custom properties named according to their selector and property. While it has promise, there will need to be some manual work involved since it creates so many properties and very long property names due to long selectors.

@michael-arestad outlined a couple of alternative approaches that may reduce the amount of the custom properties, but may require selective overrides and may be more difficult to understand. We went back and forth a bit exploring these options and that it would be valuable to have foreground and background colors paired together, and perhaps there is a way with the concept of design tokens to achieve that.

We concluded that a next step would be getting an idea of the scale of actual color values required, and @squarebracket shared a very interesting approach for programming Sass-like color functons with custom properties that would could incorporate into our iteration.

CSS Latest and Greatest Link Share

The clamp() function has very good browser support these days! Here is a great blog post about it – just look at that huge Less/Sass mixin we no longer have to write!

Also, @netweb is doing some work on getting the Stylelint config and tooling into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for #wceu 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/.! Very cool.

That was all for this week!

#summary #core-css

sageshilling 4:52 am on June 5, 2020
Tags: chat, , dev, summary   

Dev Chat Summary: June 3, 2020

@whyisjake facilitated on this agenda. @sageshilling is the author of this summary, and @marybaum is your marginally faithful editor.

Announcements

@chanthaboune had three: 

  1. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has two brand-new team reps – @francina and @audrasjb! See more here.
  2. @chanthaboune will host office hours with Matt at WordCamp Europe this weekend.
  3. Release squads for the rest of 2020 are pretty close to final, with one update outstanding.

@whyisjake pointed the group to the latest Gutenberg news, which included a near-weekly releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.–this time to version 8.2.

Upcoming releases: 5.4.2

@whyisjake shared the status of the next minor.

After a smooth release-candidate launch just hours before devchat, he confirmed, “We are looking really great for a release on the tenth.” Check the Trac milestone here and you’ll see for yourself!

Component Updates

@swissspidy expects to share a merge proposal for sitemaps next week 🙂 based on this pull request. He commented that folks are “adding the finishing touches here and there until we have something we believe is ready to merge.”

@audrasjb reminded the group that two weeks ago the Plugins and themes auto-update feature got merged, and so far the feedback is pretty good.

The coders on the ticketticket Created for both bug reports and feature development on the bug tracker. are adding a few more hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and @audrasjb pointed to two relevant tickets that need copy review by Friday, when @audrasjb will submit them for final review. @m_butcher, @yvettesonneveld and @marybaum are on the task.

The two tickets are #50215 and #50268. If you’re reading this, you too can look at the copy and add your suggestions!

Open Floor

(Ed. note: Got a pressing topic for Open Floor? Add it to the agenda post as a comment, and come to the chat. It’s in 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/., so you don’t even have to comb your hair! )

From comments on the agenda:

@glorialchemica asked for an update on the full-sitesite (versus network, blog)-editing, or FSE, for short, project.
@chanthaboune responded.

So, the form to show interest has been closed, and I believe that the process of reaching out to everyone has started. The point at which actual feedback outreach and processing begins is a little fluid, since it’s tied to development timelines but it should get going in the next month or so if I recall correctly. In my absence, @annezazu will be driving the bulk of that work.

@chanthaboune

@annezazu announced that she was in the process of inviting everyone who’d signed up to a private Slack chat where folks could try things out and communicate efficiently; a lively discussion followed, with several keepers of WordPress history reminding the group of relevant incidents in the history of the project.

The result: @annezazu immediately made a public space for FSE and will take the private one down shortly.

@timothyblynjacobs asked for feedback from the Build/Test Tools maintainers on #50251. @jorbin took a look and said, Looks good. I’m going to commit it

@francina reminded the group about 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/. at WCEU!

@joyously mentioned there was a meeting about the editor and CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., and FSE.  She asked if there will be another one? 

@desrosj I think that meeting was more to help the Customizer maintainers shape their expectations of where their expertise would be needed throughout the FSE process. 

@whyisjake ended the meeting at the top of the hour.

If you’d like more depth about anything the Core team discussed, you can read the full chat transcript here.

#chat, #core, #dev, #summary

Lara Schenck 1:51 pm on June 2, 2020
Tags: , summary   

CSS Chat Summary: 26th May…

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

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

I (@notlaura) facilitated the meeting.

CSS audit updates

No CSS audit updates this week, but @joyously suggested we have a task list – perhaps we have enough direction now that updates are oriented around more concrete items vs. general updates.

Color Scheming updates

We discussed using 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/ as a sandbox for color schemes since it already has PostCSS tooling setup, and it can be a good place to prototype what we would eventually change in wp-adminadmin (and super admin). @ryelle is working on a PostCSS plugin that would automate renaming colors to custom properties named based on their selectors. A current challenge is keep the property names to a reasonable length, and there may be a need for some human intervention there.

@joyously brought up some concerns with the second-level custom property names in the code-base. These “second-level names” are the variable names that would actually be used in the code-base, and the goal would be to minimize them as we figure out the conventions e.g. we can use --button-color in multiple places instead of both --super-specific-selector-button-colorand --another-super-specific-selector-button-color. The concern is that it this second level adds unnecessary complexity, and 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). browser support more difficult.

@ryelle also shared some work on a high contrast color scheme shared in the a11yAccessibility 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) meeting.

I mentioned that we should explicitly sync up with the design team to discuss the design tokens and how they are thinking about naming conventions and variations for the colors. I volunteered to attend the design chat this week.

Open Floor

I suggested that we conclude our CSS Chats with a recurring “Latest and greatest in CSS” knowledge share so that we can keep up with changes in the language and browser support. The intent would be simply knowledge sharing – not intent to implement new features per se, but discussing progressive enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. / hypothetical implementation as well is welcome. We can start this next meeting!

That was all for this week!

#summary #core-css

sageshilling 6:12 pm on May 28, 2020
Tags: , , summary   

Dev chat summary: May 27, 2020

@francina facilitated on this agenda. @sageshilling compiled this summary; @marybaum edited.

Celebration: WordPress turns 17!

@francina asked the group: What’s the next 17 years of WordPress look like? And then commented, “Futuristic I hope, maybe some steampunk.” 

Which led to this barrage from the group:

  • Radio buttons everywhere.
  • Marquees.
  • Blink tags, it’s all about attention grabbers.
  • Even more adminadmin (and super admin) messages.
  • More animated gifs? I’m going to have nightmares. (edited) 

And this commentary:

  • Well that’s me not sleeping tonight.
  • No dancing baby unless it’s Leo [son of a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.]

Announcements

@francina got the meeting underway by pointing out two Highlighted/Need Feedback Blogblog (versus network, site) Posts:

What’s new in Gutenberg? 

As often happens on a Wednesday, just before devchat, the Editor team issued a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.. This week: 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/ 8.2.0 featured blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. patterns and significant speed boosts, plus a long list of other enhancements.

To quote @francinadirectly: “Really, kudos, Gutenteam!”

 Team Reps. You still have time to vote

Through the rest of today, May 28, 2020. @jeffpaul has been shepherding this process and will announce the new reps.

5.4.2 update

@whyisjake  will lead 5.4.2 and confirmed he’s planning on this minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. in two weeks.

Last week the group agreed on releasing a public betaBeta 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. June 3 and the full releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. June 10th.

@whyisjake added that there is one ticketticket Created for both bug reports and feature development on the bug tracker. left in the milestone, and it has security implications. In the interest of making the web safer, the folx working on that ticket are thinking of backporting it to version 5.1 – which would be an exception to the project’s current policy

Components

@audrasjb gave his 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) update: two of three 2020 projects will 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 into 5.5. The first of those, Alternate Table Views Choices, will likely be ready to discuss next week.

Open Floor

@garrett-eclipse brought a proposed UIUI User interface change from MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., that would add a dev-note field in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:
https://wordpress.slack.com/archives/C02RQBWTW/p1590133526466800

Also from Meta, the act of adding a PR to a ticket will toggle some keywords: has-patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing./needs-patch/needs-refresh and needs-unit-tests/has-unit-tests.(meta:#5080)
Garrett thanked @dd32 for working on this, and @desrosj told the group it’s on his priority list for the next several days.

@johnstonphilip asked the group to discuss ticket #50214: Consider introducing the concept of “Editors”, and several people immediately got going in a lively thread.

@desrosj proposed a new enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. in this ticket: #50268: Improve the 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/theme auto-update emails

@Howdy_McGee asked for some eyes on his patch of #50070: ‘post_type’ query variable not set for taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. queries

Per his comment on the agenda, @apedog asked the group about avenues to overturn decisions that have already been made.

@justinahinon asked about next steps on APAC-friendly meetings, per https://make.wordpress.org/core/2020/04/29/proposals-an-apac-dev-chat-town-hall-meetings/

@carike also reminded us that Sitemaps is scheduled to be merged into 5.5.

@francina </devchat>

#core, #dev-chat, #summary

Lara Schenck 5:59 pm on May 22, 2020
Tags: , summary   

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

Jb Audras 12:04 am on May 21, 2020
Tags: , , , , , summary, ,   

Devchat meeting summary – May 20, 2020

@francina facilitated the chat on this agenda.
Meeting recap by @audrasjb and @marybaum.

Full meeting transcript on Slack

Announcements

Just a few hours before the chat, the hardworking team behind the plugins and themes auto-updates feature committed it to Core! Congrats to all!

Check out this related ticketticket Created for both bug reports and feature development on the bug tracker. that adds Help Tabs text to update-core, themes and plugins WP-Adminadmin (and super admin) screens: #50215

If you’d like to be part of the Full Site Editing outreach experiment, the sign-up deadline is now May 22. @chanthaboune noted that’s just to show interest, not a commitment yet.

Highlighted posts

Upcoming releases

WordPress 5.5

The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress is in active development (Alpha cycle).

@francina noted the team is not quite complete, but it’s confirmed that @matt will return as release leadRelease Lead The community member ultimately responsible for the Release., @davidbaumwald as co-lead in the role of Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM and @sergeybiryukov as Core tech lead. The 5.5 team will also mentor the 5.6 team.

WordPress 5.4.2

@audrasjb shared that there are 20 tickets in the milestone. Of those, 17 are closed as fixed.

@whyisjake leads this point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., and the group firmed plans for a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). on June 3 and a final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. June 10.

Components check-in and status updates

@whyisjake was exuberant that the core team was able to merge the auto-updates code today. This is going to do a great deal to help people stay on top of updates for a safer WordPress ecosystem.

The merge is just the latest significant step toward the master plan for 2020. Lazy-loading of images merged a few weeks ago, and XML sitemaps is making great progress as well.

On 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) side, @audrasjb shared that most of the accessibility team’s main projects for 5.5 are moving forward. Alternate views for posts, users, and comments lists should be ready for review soon.

@johnbillion wanted to note that weekly meetings for Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site have restarted, on Tuesdays at 17:00 UTC in #core-multisite. Come join them!

In Sitesite (versus network, blog) Health, @clorith pointed out that the Theme Review Team has implemented requirements for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 headers in themes. That move should push users in the right direction for updates.

As well, the Site Health component team has had discussions with hosting about bumping the version for Servehappy dashboard nags.

Open floor

@dlh wanted to highlight #48416. He recently encountered a use for it again. If you’re interested in the taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. component, please give it a look.

@sippis reminded everyone to register for WCEU 2020 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/., which is Thursday, June 4, 2020 at 13:00 UTC. If you don’t register, you won’t get the emails you’ll need in advance, so don’t forget to register.

#5-4-2, #5-5, #dev-chat, #feature-autoupdates, #fse, #summary, #wceu, #wceu-2020

Lara Schenck 6:08 pm on May 20, 2020
Tags: , summary   

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

Lara Schenck 2:17 pm on May 11, 2020
Tags: , summary   

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

tellthemachines 3:50 am on May 1, 2020
Tags: , summary   

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

Lara Schenck 4:03 pm on April 29, 2020
Tags: , summary   

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