CSS Chat Summary: 30 July 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. Audit Updates

No CSS audit updates this week.

Color Scheming Updates

Global vs. UIUI User interface based color naming

tl;dr – We’ve gotten sidetracked by naming!

@ryelle pointed out @kburgoine‘s comment on the color schemes ticket #49999 – it gives an excellent summary of where are now and suggests a path forward. We discussed being sidetracked by the details in naming. While that will be important for an implementation, we aren’t there yet and as @kburgoine suggested in the ticketticket Created for both bug reports and feature development on the bug tracker., we first need to figure out a set of colors to work with based on what we have learned in the audit. @ryelle referenced this part of the comment for our next steps:

Look at the default colour usage in the adminadmin (and super admin) (which has been done as part of the audit already), identify the main colours (including colours not currently included in schemes i.e background-colour) and try to whittle it down to a usable/manageable colour palette

The goal here is to create a color inventory that can then be mapped into custom properties, which can then be used to implement one of the existing color schemes. I mentioned that I got access to the WordPress Figma library which can help us with the color inventory step.

@kburgoine‘s comment refers to this post about building a dark mode on StackOverflow and @ryelle mentioned it is a great read.

Dark mode as a toggle vs. a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. for schemes

@danfarrow mentioned the concept of scheme categories makes sense to him, and @ryelle mentioned that we will likely start with default light and dark color schemes, and the others can be either. We can use some default detection for prefers-color-scheme and use the default dark scheme for users who have that preference.

But…this is all getting ahead of things again 🙂

I summarized our next steps for color schemes to be:

CSS Latest and Greatest Link Share

@danfarrow shared CSS Sweeper, an implementation of MineSweeper using only CSS and HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.!! This uses the Space Toggle trick to manage state without 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/.. So cool!

#core-css, #summary

CSS Chat Summary: 23 July 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. Audit Updates

@isabel_brison had a few updates to report!

  • Audited CSS in JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files
  • Values/counts for font-family and letter-spacing (only 3 for the latter!)
  • Values/counts for z-index

This data can be seen in the audit report Google Doc. It looks like the remaining items are media query counts and the history of CSS coding standards and the stylelint configuration. @isabel_brison suggested collecting related documentation and tickets for this history piece, and using @ryelle‘s css-audit tool to accommodate the media query counts.

List of data to track on a recurring basis

For the CSS audit of wp-adminadmin (and super admin), #49582, we have discussed running recurring reports, and this agenda item was to determine what data should be tracked in a recurring report. We decided that, for now, we can place to include the same data we are including now where the collection is automated with the css-audit tool or stylelint. These items can be seen in the audit report Google doc.

Color Scheming Updates

Themes vs. Modes

One outcome of the meeting previous to this one was the concept of color “themes” vs. “modes”. I started off the conversation with this question:

Do you see a distinction between the nature of admin color schemes and something like dark mode, in the way we treat colors? For example:

  • Ectoplasm – Dark
  • Ectoplasm – High Contrast

(where “Ectoplasm” = any of the admin themes)

@tellthemachines said that she saw “dark mode” or “high contrast” to be a collection of themes that support that criteria. We discussed that “modes” are most like a way to categorize themes, and are not a separate implementation.

I shared a link @youknowriad posted during the last meeting to a prototype of dark mode in the editor. In this prototype, dark mode is a separate toggle that can be applied on top of themes. I also shares a code snipped @youknowriad posted before as an example of themes and modes treated separately:

.button {
   color: var( --wp-admin-theme-color );
   background: white;
}

.is-dark-mode .button  {
   background: var( --wp-admin-theme-color );
   color: white;
}

.my-admin-scheme {
   --wp-admin-theme-color: blue;
   // potentially other variables
}

We discussed that the rigidity of this approach will be restrictive for other themes and accommodating they variety of user needs required for 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). In this case, the text for .button in dark mode will always be white, but we need to accommodate lower contrast dark mode themes as well. @tellthemachines mentioned that the “decisions not options” motto of WordPress, and that regarding accessibility, it should be the opposite (and after the meeting @ryelle followed up with the phrase “options not restrictions” … nice!).

So, to conclude here:

  • The notions of “dark mode” and “high contrast” seem like categories for color schemes – they are characteristics of a color scheme, not separate features.
  • In order to provide options, not restrictions, regarding accessibility, it will be important to have control over all colors in the implementation of color schemes.

CSS Latest and Greatest Link Share

I shared a link to CSS Scroll Snap – the possibility of slider-like interfaces with only CSS is not so far in the future!

#core-css, #summary

CSS Chat Summary: 16th July 2020

CSSCSS Cascading Style Sheets. audit status updates

What is the purpose of recurring reports, and what data is useful in recurring reports?

To summarize input from @isabel_brison and @ryelle, the purpose of recurring reports is check on the health of our CSS code regularly, and to monitor the code-base to ensure known problems do not recur. @ryelle‘s CSS audits tool seems like the right one for this job. We discussed stylelint which is good for ensuring issues aren’t committed, but the wp-adminadmin (and super admin) CSS code-base is such that we would have to disable too much for it to be useful. That said, @ryelle pointed out that the potential to write our own rules for autofixing with stylelint.

In terms of what data is useful, @isabel_brison suggested:

  • new values for e.g. colors, margins, etc. are being introduced as little as possible;
  • avoiding use of px units;
  • specificity isn’t increasing.

Action item: Add a comment to the CSS audit ticket with a list of what data should be tracked.

Additional Updates

@ryelle took a look into how Dashicons are added in CSS, but found the need for many edge cases that it would be futile to attempt to standardize. Considering that, and the fact that the icon font is slated to be replaced with SVG, it seems a clear decision to exclude Dashicons from the CSS audit, unless the use of pixels impacts responsivity or 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).

Color scheming updates

Is it useful to distinguish custom properties implementation work as #49930 and keep #49999 for iteration and naming exploration?

I started this conversation by clarifying the question as whether this experimental PR adding custom properties to color schemes in wp-admin based on 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/ implementation was a separate initiative from than the further reaching color scheme work we have been discussing in #49999. We had some differing opinions here – where the implementation work could serve as an MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia for color schemes, but on the flip side, it is not addressing the goals of the color scheme initiative, which are:

  • 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

@youknowriad expressed that any scheme will require a main color, so this implementation does get us closer, and @ryelle expressed that we can’t expect a system designed around a main color and variations to work in every color scheme (see this example) when we are looking to support things like dark mode and high contrast color schemes.

The goal of the Gutenberg color scheme implementation was to support admin color schemes in Gutenberg components and UIUI User interface, and using custom properties to solve issues of duplication in the CSS. By adding this approach to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., @youknowriad believes we can have more consistency in the way existing color schemes are used (they are currently not consistent).

Review screenshots annotations with options for naming

I shared these *rough* mockups for a start on how we might name colors that would apply consistently across color schemes:

Given they are very rough mockups, aspects like a namespace and other details will come later – I pointed to the aspects like base__text and base__text-active for feedback. @youknowriad expressed that he does not think that a color name should include its context because the design of wp-admin can change over time, while @ryelle (and I) think the opposite – that it should be possibly more specific that these are menu colors so that they are not unintentionally used in non-menu contexts.

We then discussed an example when changing the menu background color. With this approach, it would be assigning a new value to a variable like --color-menu-bg, but @youknowriad pointed out that that wouldn’t work because all the menus use color: white across admin schemes, which @ryelle pointed out is not the intent for #49999. The intent is that the color would also be controlled by a variable and updated accordingly.

Given this example, @youknowriad mentioned that this capability seems beyond the scope of admin themes and more like a “mode”. And perhaps the different admin theme colors should support a mode. I summarized this as something like Ectoplasm – Light / Ectoplasm – Dark. @ryelle expressed that all of this, regardless of the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. semantics, needs to be part of the same infrastructure in order to support the flexibility required to implement both high contrast and low contrast color schemes.

That was all for this week!

#core-css, #summary

CSS Chat Summary: 9th July 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

There were no specific audit updates this week. I suggested starting a conversation about next steps for the audit since we have a good amount of data collected in the Google Doc, but that is not an ideal format for presenting the data. @ryelle indicated that once we figure out what data format will be useful, we can iterate on the CSS audit tool so that it can be run as a report.

@kburgoine asked about the purpose of regular audits – is it just about the numbers, or are there other conclusions we 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). based on a regular report?

For now, we can think about what purpose regular audits would serve, and what data we would like to regularly audit (e.g. for tracking a certain initiative or progression in the codebase).

Color scheming updates

@youknowriad reported that has worked on a PR implementing the system of custom properties used in 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/ for wp-adminadmin (and super admin), and summarized the work in a comment on ticket #49999. @ryelle clarified that the intent of that ticketticket Created for both bug reports and feature development on the bug tracker. was to rethink color schemes to be fully flexible vs. re-doing current color schemes with custom properties. @youknowriad explained that having the variables working at least with one color can get us closer to a full featured system that can support dark mode.

@kburgoine asked if an overall strategy for using custom properties had been defined, and @youknowriad said that the deeper discussions are still to be had, but that having a concrete PR can be useful. He is looking for feedback on the PR regarding the base color, the naming (decided by the implementation in Gutenberg), and iteration / discussion on subsequent variables as needed. @ryelle mentioned that the naming is a sticking point since we have been discussing ways to rethink the naming system.

I asked how, in the Gutenberg mixin, the primary color had been selected since it was not based on a specific variable in the existing color schemes. @youknowriad replied that it was chosen as the most important colors of the color scheme, and @ryelle mentioned it likely had to do with contrast.

CSS Latest and Greatest Link Share

@danfarrow shared a run of CSS Stats on WordPress.org 🙂

I shared Style Stage, a project that is a reincarnation of “CSS Zen Garden” with modern CSS.

That was all for this (last) week!

#core-css, #summary

Dev chat summary, July 8, 2020

@whyisjake hosted from this agenda, edited by @marybaum.

Announcements

WordPress 5.5 beta 1 landed yesterday! Tell everyone you know to download it, test everything and try to break all the new features—that’s what 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. releases are for.

@audrasjb  shared some stats: as of Beta 1, WordPress 5.5 has 190 new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.! A lively discussion followed, covering stats and going back several years, in some detail. Check it out here.

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.5 is live!
https://make.wordpress.org/core/2020/07/03/whats-next-in-gutenberg-july/

This is the last Gutenberg 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. going into WordPress 5.5 and is the major focus for this month.

From now until the final release of WordPress 5.5, Gutenberg is also in a feature freeze. That means the only tickets that will move on are 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 and code regressions; everything else will get punted to 5.6 or a future release.

Another result of the feature freeze is that TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and the Gutenberg should both see fewer last-minute commits. So look for the Beta 2 release party to start a little earlier next week (July 14) in a bow to our European contributors’ schedules.

@pbiron  #50449 could use some 
from those who are knowledgeable about RTL
#50449: Sitemap style for RTL sites

Component check-in

@marybaum announced a schedule change for the about page. She’ll attach the copy and layout to the ticketticket Created for both bug reports and feature development on the bug tracker. for 5.5 on Friday. She issued shoutouts to new contributors @abhanonstopnewsuk and @yvettesonneveld for their research with folks in the Marketing team, and @estelaris for in-depth research in design.

@justinahinon updated the group on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 5.5 and issued a call for writers. You can see progress on the Trac notes on this Google Sheet  and Gutenberg-related notes here on GitHub.   

Open Floor

@desrosj has a post coming soon that will focus the ongoing discussion of exactly which bugs and tasks get the ticket love in two periods: the beta-to-RC period (for 5.5, that’s now: it started July 7 and will run until RC1 lands on July 28) and the RC-to-release period (for 5.5, the two weeks from July28 to August 11).  

For now, you can see earlier discussion on the topic here.

Finally, @whyisjake brought up a pull request that got his attention because of licensing issues it raises for part of the contributor toolchain.

#5-5-2, #devchat, #summary

#5-5

CSS Chat Summary: 2nd July 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. Audit Updates

@danfarrow made some formatting updates on the Google doc containing the audit data, and added an image of the longest selector on a mug:

Longest CSS selector found in WordPress on a mug

Brilliant!

@isabel_brison added an audit of z-index values to the list as well.

Color Scheming Updates

We discussed the ticketticket Created for both bug reports and feature development on the bug tracker. #50504 for a modern/higher contrast color scheme in 5.5 (mistakenly referred to it as a high contrast scheme, but it is higher contrast). @afercia asked what problem this new color scheme will solve, and why it is using the Sass variables instead of CSS custom properties. @ryelle indicated that we are moving slowly with this initiative, and that for now any new schemes should continue with existing conventions.

The rationale for the new color scheme is a conversation for the design channel, but @youknowriad understood it was meant to modernize the look/feel of WordPress adminadmin (and super admin), and to possibly be the default theme later. @ryelle mentioned it would also be a good pairing with dark mode. In terms of implementation, @youknowriad discussed that there will still be a need for Sass variables, and to be cautious about what values are exposed as CSS variables since it is a runtime APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. A CSS variable for the main admin color makes a lot of sense.

@youknowriad noted an issue with the color schemes not applying to secondary buttons (secondary is a term used in 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/ though not in wp-admin, and refers to the outlined style of button) that he is working on in ticket #50537. @ryelle noted that that may be intentional for color contrast, and that a specific variable for secondary/default button colors would help with this issue. @youknowriad indicated the colors are adapted for secondary buttons in Gutenberg, and this should be consistent with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. @afercia noted that a related change was submitted in 5.3 but reverted. It is unclear if that was specifically about the button color or possibly inputs, but in any event, the functionality is inconsistent with core and Gutenberg.

I asked if there are any notes from this incident that we should take into account with the color scheming work, and @afercia mentioned that styling changes in the 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. editor that are intended to be adopted in core, should be discussed in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. vs. GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. I proposed an idea that the same CSS variables that are now used Gutenberg should be used in wp-admin. @youknowriad said this would be great for post-5.5 work.

We then discussed a bit of the distinction between wp-admin CSS and Gutenberg CSS, and the history of the #core-css channel. The #core-css channel came about at the beginning of this year as a avenue for discussing how to use more modern CSS practices in wp-admin. The Gutenberg CSS architecture conversations occurred in the #core-js channel.

@ryelle asked if anyone was actively owning the task to annotate screenshots, and I committed to coming up with at least a starting point to discuss at the next meeting.

CSS Latest and Greatest Link Share

@kburgoine shared “a latest but maybe not greatest” link for CUBE CSS, a new CSS methodology that’s been floating around. Like any methodology, it depends!

That was all for this week. I’m super late posting these notes, but better than not posting them!

#summary

Devchat meeting summary: July 1st, 2020

@whyisjake led the chat for this agenda

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

A few blog posts and announcements were shared by @whyisjake

@azaozz recently published a plan to update the version of jQuery that is shipped with WordPress: ‬Updating jQuery version shipped with WordPress‬‬

@sergey‬ published this proposal last week to change some of the closure statuses in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.: Proposal: Rename “invalid”, “worksforme”, and “wontfix” ticket resolutions. ‪@sergey‬‪ shared that he is waiting on more feedback and will summarize this weekend or so.‬‬

@audrasjb recently published ‬WordPress 5.5: Better fine grained control of redirect_guess_404_permalink()

@desrosj recently published External Library updates in 5.5: call for testing

What’s new in 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/

@whyisjake noted the amazing new image editing capabilities (with gifs!) : What’s new in Gutenberg (24 June)

As a follow up, ‪@Andrei‬ posted the editor chat summary earlier today: Editor chat Summary: 1st July, 2020

@whyisjake pointed out that for anyone interested in contributing to closing some 5.5 tickets, ‪@ella‬ has a GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ board tracking issues for the net 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..

@desrosj wants help to test SimplePie and PHPMailer! All 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 authors that utilize these libraries should receive an email alert. The updates have been in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. for at least a few weeks now, and no issues have been found yet. @ipstenu has picked it up and just needs a clone.

Upcoming Releases

WordPress 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 is right around the corner: WordPress 5.5 Development Cycle @whyisjake noted that from this point on, no more commits for any new enhancements or feature requests in this release cycle, only 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 and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point, and can be picked up for commit again at the start of the WordPress 5.6 development cycle.

Components Check-in and Status Updates

APAC Scrub @davidb‬‪ provided an update on the ‬APAC scrub last night. With Beta 1 approaching, the deadline for Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. type tickets is at that point.@audrasjb congratulated everyone on bringing the number down this past week. @whyisjake ‪asked what the process would look like between now and ~next Tuesday for these tickets? @davidb said ‬triaging while pinging owners/maintainers as much as possible for updates. Monday and Tuesday will probably see a lot of punting though, if these tickets don’t move between now and then‪. @whyisjake then asked if a ticketticket Created for both bug reports and feature development on the bug tracker. doesn’t see movement, do we normally move to Future Release or 5.6? @davidb said mostly Future Release with a comment that the owner/maintainer/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. can update to the current milestone when they assume ownership to avoid the “kick the can down the road” issues of the past.@whyisjake gave major props to @davidb and everyone else that takes the time to keep the ticket garden tidy.‬‬

@francina mentioned that there has been a lot of discussion in 5.3 and 5.4 about what bug fixes can be fixed. Group asked if we should revisit or continue as we did until she finds the time to write the proposal?

@audrasjb noted that ‪#48751 was intentionally punted to 5.6 and not Future release and should be left in its current milestone‬‬

@marybaum team is on track to attach rough layout and copy for the About page to the ticket on track with Beta 1 and then commit by RC1, so polyglots can have the full period to translate. She gave props to ‪@estelaris‬, ‪@yvettesonneveld‬ and ‪@abhanonstopnewsuk‬ for art direction, help with the message brief and outreach to the marketing team.

@francina gently reminded all the component maintainers that we are 6 days away from Beta 1 and ask for help if needed.

@whyisjake provided a link for the list of components, with the maintainers: Component Pages – 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). WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@whyisjake mentioned that WordPress 5.5 introduced a new sitemap component.

@Carike mentioned that there is still a significant difficulty that some components have a large number of maintainers, while only one is currently active. It prevents people from volunteering. @francina and ‪@yvettesonneveld‬ talked about the possibility of mentoring new contributors to avoid burnout.

@Carike mentioned that one couldn’t triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets properly without maintainer status. @clorith said anyone can triage tickets, it’s also possible to have gardener capabilities without being a maintainer. @johnbillion seconded this and said maybe the status is not set on Trac @whyisjake posted the link to some docs around bug gardening: Bug Gardening @sergey also posted the link to a good overview for anyone interested in triaging/gardening @‬desros ‬has a new related post in his drafts and will try to wrap that up and get it published next week!‬

@audrasjb gave a few updates from the components he’s working on:

  • Everything is fine from Widgets and Menus components. The biggest remaining ticket is #48170 and it’s only waiting for review.
  • Everything is fine from Plugins and Themes auto-updates. We have few remaining tickets but no blockerblocker A bug which is so severe that it blocks a release..
  • From 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) focus: we’ll start punting to Future soon. We still have two remaining bug scrubs to handle the remaining tickets.

New 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.-based menus page: @Andrei‬ and a bunch of other folks have been working on a new, block-based, menus page (nav-menus.php) and think it’s time to start syncing with everyone else on how things evolve. They will host a weekly chat in #core about the current evolution and state of the new navigation screen. The meeting will happen in #core every Wednesday, July 1, 2020, 12:00 AM PDT, starting next week, on Jul 8th. In general it will be a triage around issues in GitHub labeled with either [Feature] Navigation screen or [Block] Navigation but also completely open to exploring any subject around improving the navigation creation process in WordPress, increasing compatibility with the incoming FSE and also maintaining backwards compatibility.

@sabernhardt mentioned that #50120 could benefit from more attention

Open Floor

@Hareesh asked, with regards to ticket #50503 (linked #40039), if it is conventional to make such changes for all bundled themes all the way up to Twenty Ten? @williampatton @whyisjake @audrasjb agreed it was and @whyisjake said the team normally coordinates with ‪@ianbelanger‬ who pushes those same changes to the non-bundled versions that are the in the theme repo.

@enrico.sorcinelli raised ticket #21676, based on the analysis ‪@sergey‬ he thinks that is definitively the time to take a decision for this 8-year old ticket and long awaited simple feature. ‪@sergey‬ asked everyone to read the recent comments on the ticket and share their thoughts

#5-5-2, #dev-chat-2, #summary

CSS Chat Summary: 25th June 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

I added a summary comment with remaining items to the main CSS audit ticket, and confirmed with the group that we were in agreement to remove auditing CSS comments from the list. I also added property counts for letter-spacing and font-family to go along with the other typography-related properties.

There was general agreement that the “Determine methodology recommendations” sub-task ticketticket Created for both bug reports and feature development on the bug tracker. is complete since we have been using @ryelle excellent CSS audit tool. The next step will be determining how to automate the results, and @isabel_brison suggested that be a separate ticket. In addition to an automation ticket, I added that we will want to have a ticket to determine the display of audit data.

Color scheming updates

@ryelle mentioned the merged PR 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/ that successfully applied the adminadmin (and super admin) color scheme using a single base color with accompanying Sass mixin vs using the post-css themes approach we’ve looked at previously.

@danfarrrow mentioned the possibility of computing the color values in native CSS using custom properties. There was agreement that this would be ideal, but that Sass or PostCSS would be required at least in part, and we would need to test out some approaches, including something like outlined in this blog post. @youknowriad mentioned an issue with the approach outlined in the blogblog (versus network, site) posts ties the colors APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to HSL values, and we would want to have the colors available in a more generic form. Still, some experimenting is in order before we fully rule out the possibility!

CSS Latest and Greatest Link Share

I shared the gap property that can be used for horizontal and vertical spacing between elements for both flexbox and CSS grid. While support is not green across the board yet, recent versions of Chrome have full support, so we are getting close and this blog post of mine gives an overview of using the gap property with a fallback.

#core-css, #summary

Media Meeting Recap – June 25, 2020

Here’s a summary of the #core-media chat from June 25, 2020. Weekly media meetings happen on Thursdays at 14:00 UTC; see the full transcript here, in the Make WordPress Slack.

Attendees: @paaljoachim, @joemcgill, @desrosj, @chaion07, @cdog, @sageshilling, @antpb, @afercia, @swissspidy, @JJJ, @pbiron

Discuss Media 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/. endpoints

The below post was discussed as an effort to bring visibility to the changes in image editing. Please take a moment if you haven’t to consider any Media implications of the changes. Many great ideas have been documented in the post.

Ticketticket Created for both bug reports and feature development on the bug tracker. #50105: Remove infinite scrolling behavior from the Media grid

#50105 was discussed and there is some help needed testing the most recent 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. to remove the infinite scrolling behavior in Media grid. Separately from this issue, a new 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. was found that needs some attention. The unintended consequence of the changes were that the number of items counted for the “Load More” button are incorrect as they calculate images that do not render. The ticket at minimum before 5.5 needs a more accurate count to better represent what is left to load. An issue to track this can be found in #50410.

Media Meeting Continued June 26 at 14:00 UTC

One topic that did not get a chance to be discussed was #16020 “Upload custom avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. for user in Dashboard” which was recently commented with a recommendation to remove from the 5.5 scope. Given the timeframe and wide range of complexities, this needs some time to:

  1. Discuss tomorrow at 14:00 UTC to determine next steps
  2. Collaborate with the Privacy team to ensure this is done in the best way for everyone and in a featured 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.

Please feel free to continue the momentum of this issue join in on the discussion tomorrow.

#core, #core-accessibility, #core-media, #media, #summary

Devchat meeting summary – June 24th, 2020

@whyisjake led the chat on this agenda.

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

A few blog posts and announcements were shared by @whyisjake and others:

  • 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.4 has been released: What’s new in Gutenberg – June 24, 2020
  • A date/time has been solidified for APAC specific triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions: New date and time for APAC triage sessions
  • @audrasjb announced that @ryokuhi was elected to replace him as 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 RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts., alongside @nrqsnchz.
  • @jorbin has recently published a proposal on moving git repositories away from master as the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". name to using trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.: Proposal: Update all git repositories to use trunk instead of master. This work is already on track.
  • @sergeybiryukov published a proposal to change some of the workflow related keywords to be more inclusive: Rename “invalid”, “worksforme”, and “wontfix” ticket resolutions

Upcoming releases

WordPress 5.4.3

WordPress 5.4.2 has been simmering for a few weeks now, and milestone 5.4.3 is open on Trac.

Right now, the majority of the tickets are related to theme updates, with one regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. As there is less than 2 weeks before WordPress 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, the main effort is currently concentrated on milestone 5.5.

WordPress 5.5

WP 5.5 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. coordinator @whyisjake shared that beta 1 is roughly two weeks away (July 7, 2020), and there are still around 230 open tickets in the milestone.

@davidbaumwald will bump the remaining early tickets at the end of the week. There are currently 13 tickets marked as early in the milestone. He also shared a general reminder: Beta 1 is the deadline for Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. type tickets.

@desrosj shared a list of all feature request and enhancement tickets currently in the 5.5 milestone (88).

@pbiron asked if “enhancements” to the three feature plugins merged in WP 5.5 are allowed to be committed after beta 1. @clorith answered Feature plugins should not need enhancements post-merge. However, small enhancements can be labelled as a 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., for example if the enhancement aims to reduce false positives, like #50437 does.

@sergeybiryukov also recommended to branch the next milestone (5.6) right after Beta, so enhancements and other bug fixes could go to trunk for 5.6 and not loose their momentum.

Components check-in and status updates

@antpb shared the Media team next meeting agenda.

@azaozz asked for help with the Test jQuery Updates plugin. Feedback are welcome ont the text/explanations in it, and with the readme file, etc. 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 is expected to be officially released very soon.

Open Floor

@joyously pointed some tickets that may benefits to plugins and themes auto-updates feature. Her proposal is to add more information to the auto-update email notifications. In the case of themes, adding information from the changelog. @audrasjb 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). sure to raise those points during the next auto-updates team meeting.

@carike asked to consider removing coreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/. channel from the channels that are auto-joined for Slack. It would be less stressful to try to orientate new users in an environment that is less technically-focused and/or not quite as large as core Slack channel. Everyone agreed this proposal makes sense. @aaroncampbell proposed to use a welcome channel that is locked but had a message with the main channels for each group for people to click to join. A ticketticket Created for both bug reports and feature development on the bug tracker. is about to be opened on 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. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to handle ad discuss this task.

#5-4-3, #5-5, #core, #summary