CSS Chat Summary: 18th June…

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

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

I (@notlaura) facilitated the meeting.

CSS audit updates

@isabel_brison updated the Audit Google Doc with some unique counts of layout and typography related properties with a focus on those than overuse px in a way that effects responsive behavior, and added a list of all properties using px values.

We then discussed @joyously‘s suggestion from a few weeks back that we create a task list for the audit. The doc is useful, but very informal and might be hard to follow for anyone who doesn’t have existing knowledge about the initiative. There was general agreement that a specific task list would be useful. I mentioned that it seems like we are nearing completion of the smaller audit tickets (Create a Report Outline and Determine Methodology Recommendations), and that in a few weeks we will want to discuss what’s next. Exciting! I volunteered to take stock of the remaining work and update the main audit ticket.

Color scheming updates

Last week we discussed naming conventions with the design team, and I mentioned that the notes from that meeting are a good overview of the color scheme initiative for newcomers.

@isabel_brison pointed us to a message that @youknowriad shared a PR adding admin color schemes to Gutenberg. Pretty cool that folks are dropping PRs in our channel!

I mentioned that, in the last meeting, we determined a next step of creating annotated screenshots to start iterating on the color names and abstraction names, and wondered if we should proactively seek out help from the design team for this. @isabel_brison mentioned that whatever the solution, the naming needs to work for designers and devs, and @kburgoine suggested we could propose some names and ask design for feedback. Overall, it will be a collaborative process and doesn’t need to be done by a specific team. We also discussed what exactly would be in an annotated screenshot – a full page? A specific module? I suggested that we start small, maybe with a widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. or the toolbar.

CSS Latest and Greatest Link Share

I shared a new property I learned about that has good browser support: max-inline-size

@kburgoine shared a lovely tool that shows sorted named CSS colors.

That was all for this week!

#summary #core-css

Devchat meeting summary – June 17th, 2020

@davidbaumwald led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

@davidbaumwald shared a few blog posts and announcements:

Meeting notes

@jeffpaul and @timothyblynjacobs called for particular attention to the Experimental Endpoints (REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. team). It needs a decision, and it could use input from a variety of experienced reviewers who understand what’s at stake:

Other meeting notes:

Upcoming releases

WordPress 5.4.2

WordPress 5.4.2 shipped with the help of our amazing contributors). This version packs six security fixes and lots of 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. fixes. More details about what is inside are on the version page.

@whyisjake took a moment to thank everyone that was part of the 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. team’s huge group of contributors, both on the security front and in bug fixing.

He also called special attention to the fact that the release team decided to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the changes in how comments are handled to WordPress 5.1/5.2/5.3. See the related dev note for more.

As a reminder, the WordPress project’s security policy is publicly available on GitHub.

WordPress 5.5

WP 5.5 Release coordinator @whyisjake shared that 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. 1 is roughly four weeks away, and there are still around 250 open tickets in the milestone.

Of special note is this GitHub project that the #core-editor team has been working on.

@davidbaumwald reported that he’s added 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) scrubs to the Bug Scrub Schedule for 5.5.

The Accessibility team needs help and feedback on these tickets:

@marybaum announced that there’s a team assembled to work on the About page. @davidbaumwald has opened ticketticket Created for both bug reports and feature development on the bug tracker. #50416 to handle About page development.

Following up on her announcement, @marybaum suggested promoting WP 5.5 in the current version’s dashboard for a couple of weeks in the release-candidate period in a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user..

@desrosj answered that if something is important enough to receive its own area on the dashboard of every site before it is released, the best way to do that would be in a post on the News blog.

Components check-in and status updates

@flixos90 asked the Media team for feedback on #50367.

@timothyblynjacobs would like feedback on a possible batch-processing endpoint for the REST API: #50244, on the particulars of the 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. and on the ergonomics of it.

@mikeschroder requested feedback on whether (and what) filters would be helpful for opcode cache invalidation: #36455.

Open Floor

@paaljoachim pointed out ticket #16020, which aims to introduce custom avatars for user profiles. The ticket has a patch; it needs review and final validation from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team.

@enrico.sorcinelli called the group’s attention to ticket #21676, and @sergeybiryukov confirmed that ticket is already on his review list.

#5-4-2, #5-5, #core, #summary

CSS Chat Summary: 11th June…

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

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

I (@notlaura) facilitated the meeting.

Discussion on color naming with the design team

We started out by reviewing some goals of this color scheme initiative with regards to wp-adminadmin (and super admin):

  1. Easily create full-feature color schemes that apply to the entire wp-admin (e.g. dark mode)
  2. Improve existing wp-admin CSS

@joyously asked if this applies to properties like CSS filters and blend mode, and @kburgoine and I indicated that it would likely be limited to defining a base color palette and color values.

I then asked how the designers currently name colors in designs – @michael-arestad replied that he uses hex codes, and for colors named according to intent, it is only the accent color. @ryelle linked to this WordPress Colors CodePen. @nrqsnchz agreed that we should aim to use names that specify the use of the color vs. the color itself.

@michael-arestad linked to a couple of example projects where colors were organized into “sets”: the main colors (5-10 most common), a primary accent color, additional accent colors. Here is one example with multiple levels of abstraction and an older version.

I mentioned another goal – or perhaps an elaboration of what “easily create color schemes” means – is that creating a new color scheme should be a matter of updating a predefined set of variables with different colors values. One should not have to write any new CSS (save custom property definitions at a high level) to create a new color scheme, and to achieve this, multiple levels of abstraction will be required (e.g. assigning #FFF to --button-color, and thencolor: var( --button-color );).

@michael-arestad noted the importance of providing a range of lighter/darker versions of a colors to ensure folks aren’t coming up with slightly different shades of the same color, even though providing those options is important.

We discussed a next step of annotating some designs with potential color palettes and names – for example, a screenshot of wp-admin with the default color scheme and a screenshot in dark mode, with a Figma palette with the colors used in each. The intent of the annotations is not to determine specific color names yet, but to get an idea of the higher level “color buckets” or categories (e.g. color-primary, color-accent), and the UIUI User interface elements they may be applied to (e.g. --button-text-color, --sidebar-background-color).

Next, we talked about options for naming the variations in the colors – a couple of approaches mentioned were using terms lightest/lighter/light/dark/darker/darkest or using number 100-900 to allow for middle ranges. @ryelle mentioned another approach where 50 was used as a cutoff and above or below 50 indicated contrast with white/black, and we discussed the ideal of a naming system that would help ensure proper contrast ratio between colors. I shared an example of how we are handling our color naming at my job.

To conclude the meeting, I re-iterated / refined the goals of the color scheme initiative:

  • Creating a new color scheme should be similar to filling out a form with color values
  • All colors in the wp-admin should be controlled by the color schemes
  • Reduce the number of colors in use by providing default color palettes with varying shades

Our next steps are to start determining the “color buckets” and categories/mappings of the UI abstractions that will be used to apply the colors. We can start this process by annotating screenshots two screenshots (one of light mode and one of dark mode) with potential color names and corresponding color palettes.

Help Needed
Is someone with design knowledge up for creating these annotations? @michael-arestad offered to provide guidance and access to Figma where needed.

Latest and Greatest in CSS Link Share

@kburgoine shared Hybrid positioning with CSS variables and max() from Lea Verou (who’s website is using the default theme to great effect! 😄).

That was all for this week!

#summary #core-css

Devchat meeting summary – June 10th, 2020

@whyisjake led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

@whyisjake shared a few blog posts and announcements:

Upcoming releases

WordPress 5.4.2

WordPress 5.4.2 was planned to be released Wednesday 10th after the devchat (and successfully shipped with the help of our amazing contributors). This version includes six security fixes and many 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. fixes. More details about what is inside can be found on the version page.

WordPress 5.5

@pbiron reminded that three feature plugins will be included in WordPress 5.5. Lazy loading of images, themes, and plugins, auto-updates, and XML sitemaps.

Some tickets for enhancements/features will need some help, testing, or feedbacks before 5.5 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. 1 (targeted date: July 7th, 2020): #40351, #41750, #33161, #47456, #43738.

@audrasjb mentioned some other tickets on which 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 needs help and feedback. #49459 and #49651 need Editor team feedback and #30155, #47120 and #48170 will need feedback and expertise from the Media team.

@paaljoachim said he’s working on #16020 and would need some feedback on it.

Open Floor

@enricosorcinelli mentioned that #21676 got some new attentions, and could be a possible candidate to ship in 5.5.

@adamsilverstein reminded the group that the #core-js team is looking for an additional person to help run the weekly JavascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. chat. The chats take place Tuesday at UTC-06:00 in #core-js. Feel free to say in the channel in the next meeting if you’re interested in that.

@justinahinon said that he reached out to people interested in helping on hosting APAC devchats proposed here. There is a plan to discuss in the #core channel about the outcomes of the meetings and a possible schedule (a note about that will be published soon on 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)./CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog).

Related to that, @yvettesonneveld shared what they have been doing for marketing coffee breaks and that was very helpful in recruiting and retaining contributors. Updates for this can be found here.

@jeffpaul proposed some additions to the Releasing Major Version and Glossary handbooks. These additions are about the early ticketticket Created for both bug reports and feature development on the bug tracker. definition and how they are handled during the 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. process. This is a result of discussions at 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/. and received helpful feedback from @davidb, @desrosj, and @joemcgill. Some contributors had a discussion about that, and you can rollback to here to follow.

@enricosorcinelli reminded that they are some tickets that have been milestoned for each release since 5.0 but hadn’t received any attention in their life cycle. These are #43516, #43517.

This closed the devchat discussions to leave room for WordPress 5.4.2 release party.

#5-4-2, #5-5, #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

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-site-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

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

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

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

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 Site 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