CSS Chat Summary: 25 February 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @ryelle suggested she could run a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-specific 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. scrub next week, ahead of the upcoming release – thanks @ryelle!

Project updates

CSSCSS Cascading Style Sheets. Audit (#49582)

There was a discussion about whether the time is right to share this project with the wider community:

  • @notlaura suggested adding container audits would bring the project to that point, although the tool does fulfill the objectives of the original audit ticketticket Created for both bug reports and feature development on the bug tracker.
  • @ryelle suggested also an introductory post on make/core and moving the repo into the WordPress 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/ org, preferably after the 5.7 release

There was discussion of how “dead” CSS could be deprecated & eventually removed

  • @ryelle observed that helper tools (e.g. for the adminadmin (and super admin) colours reduction project) help mitigate the risks of removing CSS
  • @williampatton suggested measuring the potential impact of particular CSS deprecations on 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 developers by performing regex searches on plugins in the directory
  • @notlaura shared a Google doc from earlier in the CSS audit process with some preliminary results using purgeCSS to find redundant CSS in core
  • @ryelle pointed out that about.css has a whole section of deprecated code that could be used to test out a CSS deprectation flow

Color Scheming (#49999)

  • @notlaura reminded us that next week we’re hoping to see some CodePens / sandboxes of approaches to naming custom properties for colours in the buttons – details here in Slack
  • @ryelle shared ticket #52623 which proposes adding a CSS custom property to represent the height of the WordPress admin bar
  • Introducing this custom property into core, along with its tooling & documentation requirements, would be a great opportunity to get the ball rolling

Visual 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. testing (#49606)

  • We had intended to remove this from the agenda but as it was mentioned @williampatton asked for some clarification on the current state of the ticket
  • Briefly, the visual regression tool in @tellthemachines’ PR is intended to be run on a person’s local machine, rather than running on CI & adding screenshots to the repo

With that @notlaura realised that we had run out of time & the meeting closed.

Thanks everyone!

#core-css, #summary

CSS Chat Summary: 18 February 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @ryelle volunteered to run next week’s 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. scrub (Thursday 25 February @ 21:00 UTC) – thanks @ryelle!

Discussion: Deprecation flow for base styles

  • Last week’s bug scrub brought up this Gutenberg issue about an SCSS variable that was removed from the wordpress/base-styles npm package
  • The issue asks if a deprecation policy & notice period exists, or should exist, for SCSS variables, since they may be used by developers in contexts other than coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • After some discussion @ryelle suggested the #core-editor meeting might be better equipped to delve into this issue
  • @notlaura offered to bring this up at the next #core-editor meeting (Wednesday 24 February @ 14:00 UTC)

Updates

Color Scheming (#49999)

CSSCSS Cascading Style Sheets. Audit (#49582)

Visual 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. testing (#49606)

Open Floor + CSS Link Share

With that the meeting drew to a close.

Thanks everyone!

#core-css, #summary

CSS Chat Summary: 11 February 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • Happy Birthday CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Chat! We shared a pleasant moment reflecting on & celebrating the achievements of the group’s first year
  • @kburgoine asked for somebody to raise the profile of upcoming 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. scrubs by posting a note an hour before in #core (for TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.) & #core-editor (for 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/). @notlaura offered to do this
  • @tellthemachines offered to announce the regular bug scrubs in the APAC dev chat, and
    @kburgoine offered to do the same in the EMEA dev chat

Discussion, continued: Introducing CSS Custom Properties to WP Adminadmin (and super admin)

  • @notlaura summarised last week’s discussion where there was general agreement that an abstraction layer was the way to move forward with custom properties, starting with a small piece and prefixing the property with --experimental to indicate caution to 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 developers
  • @notlaura suggested starting with a variable from the abstraction layer as outlined in @ryelle’s blog post, for example the button abstraction
  • Discussing the colour scheme colours required by buttons, @notlaura identified 5:
    • Background regular
    • Background hover/focus
    • Text regular
    • Text hover/focus
    • Border focus
  • A helpful next step would be to mock up a button with custom properties in Codepen or similar, in order to iterate on naming decisions
  • The discussion briefly touched unifying admin styles and Gutenberg styles which, while not formalised, we tentatively agreed should be a long term goal

Project updates

CSS Audit (#49582)

Open Floor + CSS Link Share

The meeting ended with virtual slices of Core CSS birthday cake. Thanks everyone!

#core-css, #summary

CSS Chat Summary: 04 February 2021

The meeting took place here on Slack@notlaura facilitated and @danfarrow wrote up these notes

Housekeeping

  • The next bugscrub (Thursday February 11, 9pm UTC) will be for 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/ issues with the styling label
  • UPDATE @kburgoine has agreed to run the bugscrub

Discussion: Introducing CSSCSS Cascading Style Sheets. Custom Properties to WP Adminadmin (and super admin)

  • @notlaura shared some links to provide context for the discussion
  • @joen outlined two high level hopes for the project:
    • Start simple – it’s easier to add complexity than to remove it
    • Build on the work already done on 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
  • @joen expressed concern about the number of variations in @ryelle’s base colour palette
  • @ryelle clarified that the palette is intended as a set of Sass variables to be compiled into a smaller set of function-based, public colour variables
  • If we followed that approach, the final choice of public colour variables would form the public 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. which would require ongoing support, so choices should be made carefully
  • @joen shared details of how the block editor uses a single focus style which adds a “spot colour” border – in dark mode a white halo is added to ensure sufficient contrast
  • @notlaura suggested a simple starting point for adding an abstraction layer: introduce 1 or 2 abstractions into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and track their success over a fixed review period
  • The initial abstraction variables could be hidden behind a feature flag or prefixed as --experimental
  • Time was running out but the discussion will continue in future meetings

Project Updates

CSS Audit (#49582)

  • @notlaura reported having added a comment to the ticketticket Created for both bug reports and feature development on the bug tracker. summarising progress in recent months
  • There were no updates for Color Scheming (#49999) or Visual 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. Testing (#49606) this week

Open Floor + CSS Link Share

On that polarising note the meeting closed. Thanks everybody!

#core-css, #summary

CSS Chat Summary: 28 January 2021

The meeting took place here on Slack@notlaura facilitated and @danfarrow wrote up these notes

Housekeeping

  • @paaljoachim suggested that the bi-weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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.-scrubs alternate between TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets & Gutenburg 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/ issues
  • @tellthemachines agreed & suggested triaging issues under the CSS styling label
  • @notlaura suggested doing this at the next bug-scrub which is scheduled for 11th February

CSS Audit (#49582)

  • @ryelle reported that the CSS Audit report is now updating & being generated automatically with changes to core – the automated commits reveal changes to core CSS as they happen
  • @notlaura suggested generating the report as JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. first, to enable changes to be tracked over time, to which @ryelle suggested adding a second action that generates a JSON report
  • @notlaura observed that this news will be a great update to add to the CSS audit ticketticket Created for both bug reports and feature development on the bug tracker.

Color Scheming (#49999) & Visual 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. Testing (#49606)

Visual Regression Testing

  • @tellthemachines reminded us that her PR is still open & has received some review feedback
  • She plans to add more tests in the coming week, followed by tests for mobile breakpoints
  • She is also considering the basis on which the tests should be automated with Github Actions

Open floor & CSS link share

Thanks everybody!

#core-css, #summary

Media Meeting Recap – January 28, 2021

The following is a summary of the weekly Media component meeting that occurred on Thursday, January 28, 2021 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @paaljoachim, @hellofromtonya, @joedolson, @ricjcs, @audrasjb, @mista-flo, @mkaz, @chaion07

Open Floor

This meeting’s focus began with an open floor for discussion on outstanding tickets and issues members wanted to address.

#47839: Extended file management in Media Library – @ricjcs brought up this ticketticket Created for both bug reports and feature development on the bug tracker. containing design samples of what folders could look like in the media library. Discussion occurred around what this feature would entail from a backwards compatibility perspective.

#52372: Ability to Replace image on the “attachment details” screen – This feature has been explored and ultimately closed after this comment in #49096. Per @antpb, “This is another one where I don’t think it’s a bad idea, in fact, it’s great, but it’s very much in 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 territory to make the decisions for your individual site. What may be good for one site may not be good for all. Offering the ability to replace media by default offers folks ways to unintentionally break old content.”

5.7 Tickets

#52192: 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/.: Add batch image editing This ticket is currently in review with @antpb and is aiming to be committed before alpha. It was discussed that this endpoint is low risk as it does not impact any existing endpoints and adds new ones.

#50025: Media Library not showing new uploads when filtering by date – This ticket is currently in review after it was found to have issues with the classic 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. media flow. @antpb is testing and will be aiming to commit before alpha.

#39004: Alt attributes should be searchable in media library – This ticket was discussed as being close to ready for commit, but talks after the meeting indicate it may need further testing with larger media libraries.

#52387: adjacent_image_link returns a link with no accessible text@antpb has given an initial review and is aiming to commit soon after more testing.

Bug Scrub

There are a number of enhancement tickets that still need to be scrubbed. 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. scrub has been scheduled for Monday, February 1 at 16:00 UTC to go over these tickets. Please join us if you would like to contribute!

Props @antpb for proofreading and final review.

#core, #media, #summary

Editor chat summary: 27th January 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-01-27 14:00 UTC in Slack. Moderated by @andraganescu

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/ 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 Release

  • Gutenberg 9.9 RC has been delayed for January 29th 2021, to sync with the upcoming 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 release of WordPress

WordPress 5.7 Beta 1

  • WordPress 5.7 Beta 1 is due for release on the 2nd February 2021.
  • Beta 1 will represent the cut-off point for new commits/features for 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.
  • The deadline for changes is Gutenberg 9.9 RC on the 29th January.
  • There is a WordPress 5.7 project board where you can follow along and keep up to date with progress.
  • WordPress 5.7 will include versions 9.3 to 9.9 of Gutenberg

Monthly Plan & Key Project updates

  • We requested updates on the key projects.

Full Site Editing

Global Styles

  • not many updates but issue 27506 is a good starting point to gauge GS status 

Block based 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. / Navigation Editor

@andraganescu provided an update for the widgets editor:

@mkaz added an update on the ongoing additions to the Navigation block:

  • The Navigation Block tracking issue is here, though we are also working on issues raised for items needed to help develop themes. So that list my get supplemented with a few additional issues. (edited) 

@grzim added an update about the navigation editor:

  • The work on menu name edit is back on track Issue 24581 . There is an ongoing discussion in #feature-navigation-block-editor about moving name edition to a side panel.
  • UXUX User experience and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues have been fixed Issue 28183 , Issue 24369
  • Also inconsistencies in e2e tests are being fixed.

Task Coordination

@hypest provided a

short update about what the native mobile folks have been up to:

  • Reusable blocks rendered in-editor (only available in DEV builds for now)
  • Audio block close to merge
  • Fix for blocks auto-scroll when the keyboard appears
  • Fixes for issues resulting from some GB-web side changes
  • Fix for File block’s automated test.

@bernie will continue to work on some release tooling automation soon. Afterwards, there are two things on the automated testing front that I’d like to work on:

  • Run e2e tests in FF (draft PR).
  • Visual diffs (to avoid block regressions) (issue)
  • Anyone interested in helping with those? Experience with puppeteer would be especially helpful for the e2e tests!

@annezazu is working on the “What’s Next” post for February and the FSE program. For the FSE program, I’m trying to find creative ways for more people to help through sharing various roles for the program (helping write calls for testing, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. feedback, etc), updating documentation with more information about the process I’m loosely following/creating, and sharing an idea around how we can include polyglot communities! I wasn’t here to announce the how to triage in GitHub course is live on LearnWP too! Working on another course this week/next week for more 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/ basics 

@paaljoachim is Working on consolidating setup local dev environment + testing instructions for Gutenberg and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Triaging Design and Gutenberg issues.
Working on a Dev site for support structure. Experimenting with the design for Learn and more. 

@mcsh updates:

  • Fixed a fatal infinite recursion issue in Reusable Blocks (@gziolo now fixing the same in Template Parts)
  • Code reviews
  • Too many conversations to name, but recently: with @ella about Footnotes, with @ntsekouras about focus bugs and other issues related to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. refs, @gziolo about how we do e2e testing, table of contents block, etc.

@andraganescu did mostly code review and testing on widgets and navigation editors

@joen has been working on a bunch of small navigation block user experience related things:

  • Menu item word wrap
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org cutoff
  • Menu item overflow menu polish
  • Button block appender
  • Space between

@itsjonq is Continuing his efforts to work on integrating the new Component System into Gutenberg (working on it directly as well as coordination). He is also tinkering with new UIUI User interface tools for Gutenberg in parallel, focusing specifically on background/color tools at the moment.

@ntsekouras updates:

  • Lot’s of triaging and GH reviews with some fixes
  • `Preferences` modal is probably ready to merge (PR /28329) – thanks @joen for the styling polish there

Open Floor

Will there be Global Styles also in the Post Editor? Or is that only to be for the Site Editor?

The general consensus on @paaljoachim‘s question was that the post is a place which lacks enough visibility for the impact the changes would have so most likely the answer now is no.

What’s Next post for February

@annezazu brought up the next focuses:

  • Preparing for 5.7
  • Global Styles
  • FSE
  • Block-based Widget Editor

Global styles in WordPress 5.7

@mcsf mentioned that whatever pieces of GS that may land in 5.7, they will concern the theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. structure and won’t impact users. At best, there will be experimental APIs that devs may use in Core, following in the footsteps of the well-known add_theme_supports extensions

AMA session about FSE and a dedicated FSE feature channel

@annezazu proposed to great enthusiasm an AMA session about FSE and also the creation of a dedicated feature channel for FSE.

A plan to standardize the use of feature channels

@priethor suggested a plan to standardize the use of feature channels:

  • Gather feedback on the overall feeling about these channels, whether folks think this segmentation improves communication or makes it more difficult.
  • If feature channels are agreed to be an improvement, create feature-specific channels for other feature projects such as FSE.
  • List these channels on the Feature Projects Overview page and promote them in automated welcome messages, as suggested by @annezazu.

@francina mentioned that “having multiple channels dilutes the attention of contributors, issues are not developed in a silo and are interdependent, so I am not sure having a myriad of channels is really helping, but willing to try”.

Internal 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 Yoast on February 5th

Also @francina mentioned:

We are doing an internal Contributor Day at Yoast on February 5th. Let me know if there are some PRs that need developers and/or users testing

This is a great opportunity to bubble up things in need of testing or extra development hands!

Input wanted on the editing of a menu’s name in the navigation editor

Lastly @grzim called attention on PR 25343 where editing a menu’s name is added to the navigation editor, for sharing opinions on the approach taken there to make it as user-friendly as possible.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting-notes, #summary

CSS Chat Summary: 21 January 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes (I’m trying a more bullet-pointy format this time – hope you like it!)

Housekeeping

@kburgoine has volunteered to lead next week’s 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. scrub which will begin at 9pm UTC on Thursday 29 January.

CSSCSS Cascading Style Sheets. Audit (#49582)

  • @ryelle is ready to merge some recent PRs on the audit tool [UPDATE now done, thanks!]
  • @notlaura is considering ideas for restructuring the property-values audits within the config file
  • @notlaura later mentioned that the !important audit report probably satisfied the requirements of #26350 and suggested that @kburgoine could bring it up at next week’s bug-scrub

Color Scheming (#49999) & Visual 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. Testing (#49606)

  • @ryelle has had some feedback on her reduced colours PR and is hoping for one more nod from Design so she can commit in the next few days
  • @ibdz kindly offered to provide feedback this weekend
  • Next step for #49999 would be more CSS cleanup, plus picking up the previous conversations around design system, tokens & custom properties
  • @tellthemachines PR for #49606 is ready for testing – let’s go!

Open floor & CSS link share

  • @ryelle brought up #51763, a ticketticket Created for both bug reports and feature development on the bug tracker. about moving from node-sass to dart-sass, which needs a 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.. @desrosj has offered assistance and @ryelle is happy to partner with anyone interested in helping
  • @notlaura shared a link to this CSS WG thread discussing ideas for expressing @media conditional values more tersely
  • @notlaura also shared this CSS WG thread about SCSS stats in the wild, with data analysis based on 300K SCSS stylesheets revealing that “inline if() is the second most used function (after darken() ) and accounts for 14.5% of all function calls

Thanks everyone for attending this week!

#core-css, #summary

Editor chat summary: 20th January 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-01-20 14:00 UTC in Slack. Moderated by @get_dave.

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/ 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 Release

  • At the time of the meeting the latest release was 9.7.4.
  • The release was underway for 9.8.0 during the meeting.
  • @bernie provided us with an update:
    • Not a lot of “big” new features.
    • …but some nice enhancements.
    • Semi-transparent Spacer 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..
    • Block Switcher now shows variation icon.
    • Major changes to the Full-Site Editing framework (see full updates below).

Preparation for WordPress 5.7 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

  • WordPress 5.7 Beta 1 is due for release on the 2nd February 2021.
  • Beta 1 will represent the cut-off point for new commits/features for the Block Editor.
  • The deadline for changes is Gutenberg 9.9 RC on the 27th January.
  • There is a WordPress 5.7 project board where you can follow along and keep up to date with progress.

Monthly Plan & Key Project updates

Full Site Editing

Global Styles

@nosolosw provided an update via the agenda post:

@itsjonq also provided an updated on Global Styles UI:

  • Working through the integrations and improvements to the Component System for Gutenberg.
  • Came up with some design/interaction ideas for the Global Styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. experience. I’ve documented them as a comment in this Github issue.

Block based 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. / Navigation Editor

@andraganescu provided the update:

Task Coordination

Open Floor

New Slack channel for block based Navigation screen

  • @danr mentioned in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dev chat that work on the block-based Navigation screen has picked up again.
  • There’s a new channel for anyone interested in following/contributing – #feature-navigation-block-editor.
  • There’s a Github project for it too.

More native mobile integration/e2e tests on Gutenberg’s PR CI

  • @hypest asked about adding more more native mobile integration/e2e tests on Gutenberg’s PR CI.
  • Some regressions recently that would have been caught with some simple automated tests before their PRs got merged.
  • Adding tests will increase the run time of the CI jobs, not much but, you know, it adds up.
  • @youknowriad recommended defaulting to adding the tests and figuring out speed improvements if needed.
  • @gziolo suggested a more detailed mobile test suite executed after every commit to 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"..

Stale Issues/PR bot in Github repo

  • @mkaz followed up on last week’s stale issue topic.
  • Posted on Make and already received great feedback and comments there.
  • We plan to leave open until end of month and then will create a PR with next steps.
  • So if you have any thoughts not already captured, please comment on the post.

Custom Post types and Full Site Editing

  • @ndiego noted how he started diving into custom post types in the FSE and custom templates, but hit a lot of deadends.
  • Is this something else one is actively working on, or still well down the road in terms of FSE development?
  • @youknowriad said he did work a bit on custom templates recently (page templates) but not much custom post types. I’m sure there’s a few things we need to figure out there though.
  • Agreed to open Issues or PRs as required.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting-notes, #summary

CSS Chat Summary: 14 January 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

@notlaura pointed out that we missed a scheduled 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. scrub today which started a short discussion about how to make them consistent.

The outcome was that the lead for each scrub should be established the week before which @notlaura will check in with to make sure the scrub can go ahead as planned. If necessary an upcoming scrub can be skipped and removed from the meetings calendar.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported having made a PR to reorganise the audit tool’s HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. report directory structure with the goal of simplification. He also moved the report stylesheet into /src and added a command to copy it into /public, which means that files inside /public need no longer be edited manually.

@notlaura noted that the property values reports issue still needs to be resolved. She linked to this related github issue as a place to discuss & keep track of ideas.

Color Scheming (#49999) & Visual 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. Testing (#49606)

@isabel_brison shared her PR to add visual regression tests for wp-admin pages which is now ready for review/testing. This will be a very useful addition to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing suite, particularly for CSS.

@ryelle reported that she shared her reduced colours branch in dev chat and is hoping for more feedback, from design especially. To encourage this she also added needs-testing to #49999. The branch is available here – please have a look.

Open floor & CSS link share

@isabel_brison shared a link to Web Directions’ call for speakers for their upcoming CSS conference. The deadline is the end of this month so get those proposals in!

@notlaura shared a useful reference for logical CSS functions min, max and clamp.

@danfarrow shared a piece of CSS esoteria: an ugly hack for rounding values down with two decimal places.

This prompted wry speculation on the usefulness of 0.01px precision, and with that the meeting concluded. Thanks everyone!

#core-css, #design, #summary