Josepha 3:57 pm on June 3, 2020  

WordCamp Europe Office and Listening Hours

@matt and I are looking forward to seeing everyone this week, either at 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/. or in the great line up of scheduled sessions. One of the highlights of these events is the time to be together and share our stories, and not be able to be in person makes that a little harder.

This year, Matt and I are offering office hours together! If you would like to grab some time with us, please sign up with Calendly. A Zoom link will be added to your calendar invite after booking.

I will also be offering additional office hours on Saturday, June 6th. You can sign up for one of those sessions here. All appointments will be 15 minutes with a 5 minute break to allow for transition time.

See you soon!

annezazu 8:18 pm on June 4, 2020
Tags: ,   

What’s next in Gutenberg? (June)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for the next month. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Sitesite (versus network, blog) Editing project. 

Full Site Editing (FSE)

Work on this major focus is ongoing and is expected to continue iterating over the next months. Right now, we’re wrapping up the major work needed to build the technical foundation of this project and are soon moving towards expanding the UX & UI:

We’re watching the Theme Experiments repo as well to see how themers are attempting to build 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 themes. Thank you to everyone participating there as it’s a super useful way for us to determine prioritization. 

Follow along:

The high level, important tasks have been split into sections and highlighted on this overview issue.

Global Styles

As a reminder, Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. The Global Styles work remains a major focus for this month. The important tasks for the month are:

Follow along:

You can follow the progress of this focus in this overview issue.

Navigation Screen

The new Navigation Menu screen and Navigation block will continue to be iterated on and polished. In particular, work is being done to create a true drag and drop experience and to explore improving the selection/focus experience (feedback welcome). In an effort to expand the functionality allowed within navigation, work is being done to explore adding different kinds of blocks other than links.

Follow along:

You can follow the progress of this project on this project board.

Refining the interface

The previous releases saw a big UI update for the editor canvas and the inserter. The team will continue to iterate based on the remaining tasks and the user feedback. The remaining tasks here include:

Follow along:

You can follow the progress of this focus in this overview issue. 

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. Screen

As part of expanding the block editor to other screens in the adminadmin (and super admin), work continues to improve the widget screen including finding bugs in the legacy widget block, ensuring synchronization, and more. Depending on the work done here, the screen should be ready to leave the experimental state and receive additional feedback soon. 

Follow along:

You can follow the progress of this focus by reviewing issues with the [Feature] Widgets label.

Areas to be aware of:

Block & 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

@aduth just merged this pull request to update default block categories which should be available in next week’s plugin 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 could be particularly impactful for block implementers, since the default categories have changed. For now, please review this drafted devnote here as a point of reference for this change. 

Theme Developers

@epiqueras recently broke down all template tags alongside their block equivalent in order to lay the groundwork for Full Site Editing: 

“The idea is for everyone in the community, especially those very familiar with traditional theme development, to contribute to this list. There might be things we are missing. There might be things we could lose.”

Please check out this overall issue and share what might be missing. 

Ways to Help:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. If there’s anything we can do 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). contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

#core-editor #gutenberg-next

Lara Schenck 6:50 pm on June 4, 2020
Tags: ,   

CSS Chat Agenda: 4th June…

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

This is the agenda for the upcoming CSS meeting scheduled for Thursday, June 4, 2020, 5:00 PM EDT. I am posting it very late…sorry 🙁

This meeting will be held in the #core-css channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Acknowledging racial injustice
  • CSS Audit Updates
  • Color Scheming Updates
  • CSS Latest and Greatest Link Share

#agenda #core-css

Eileen Violini 12:55 am on June 4, 2020  

Editor Chat Summary: 3 June, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core-editor 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 on Wednesday, June 3, 2020, 10:00 AM EDT and was facilitated by @itsjusteileen.

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

  • WordCamp Europe and Contributor Day are coming up June 4-7.
  • For contributor day, @youknowriad is planning to do a quick zoom chat to help people setup a 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/ environment at the beginning of the day. To come prepared, please have “Docker” + Latest node.JS LTS setup.

WordPress 5.5 Upcoming 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. 

The planning roundup for 5.5 can be found here. There are several features that are under an experimental flag in Gutenberg, and to have a chance to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it for 5.5 they’d need to be out of experimental by July 7th.  @mapk put out a great post encouraging contributors to focus on features merging into WordPress 5.5 Everyone is invited to take a look if you are looking for a way to contribute.

Gutenberg Version 8.2.1

Gutenberg 8.2.1 was released 28 May.

Monthly Plan

The May monthly priorities are posted and @youknowriad and @annezazu are working on the post for June.

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@youknowriad

  • Iterating on the Inserter PR 21080
  • If you have thoughts on what a “writing mode” should be, check this PR 22494
  • Trying to review and unblock forks as I can
  • Getting ready for Contributor Day
  • Try a very opinionated spotlight mode PR 22494

@paaljoachim

  • Improve “Visibility” and “Publish” labels in Post Settings Issue 470
  • Add option to set as feature image to image/cover 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. Issue 13795
  • New block: Accordion Block Issue 21584
  • Plan to help with docs: Create a Block tutorial PR 22831

@aduth

  • Fixing and trying to improve patterns around end-to-end test stability Issue 22804
  • Proposing a package to lazily install dependencies to try to reduce initial download size PR 22684
  • Trying an approach to enqueue only scripts/styles relevant for blocks present on a front-end page PR 22754
  • Automating 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/ pull request comments to warn when a save.js change isn’t accompanied by a deprecation PR 22767
  • Prompting during the release tool if there are still open issues or pull requests in the milestone PR 22764
  • Helping flesh out some of the architecture documentation that Riad started PR 22751

@nosolosw

  • Spent some time creating clarity about the work related to the Block Style System: updated the master issue, created a new issue to track style attributes (also closed a few others).
  • Prepared some fixes for presets PRs 22668, 22526, 22671.
  • Global Styles: merged a PR that uses the block.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. to detect support for style features.
  • Helped with reviews.
  • For next week, my main focus is going to be adding 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. to edit-sitesite (versus network, blog). I believe that we’ve now landed all the necessary framework pieces to make this work.

@sageshilling

  • Gallery/image and block media

@desaiuditd

  • I’m working on the Embed block.
  • One PR is in progress to convert the edit component to function component. Functionality done. e2e tests are broken. I’ll work on fixing them. Would love some feedback on it PR 22846
  • Second PR will be to add Convert to Link option in the block toolbar menu.
  • On the side, I would like to move this PR forward. It allows extensibility on the Document label in the sidebar PR #17311
  • I will also try to see if I can pick up any PRs to review.

@getdave

After taking some time out, I’ve been back working on some Navigation block related PRs:

  • Create Navigation blocks from existing WP Menus – technical review appreciated PR 18869
  • Fix 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. in the Link UIUI User interface where “Recently updated” was shown even if there were no recently updated Pages PR 22856

@gziolo

  • Still working on block registration on the server
  • Helping to finalize work on a new block types 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/. endpoint
  • Trying to figure out the final shape for block.json to make it easier to create blocks for Block Directory

@andraganescu

  • continued the work on the new navigation screen
  • code reviews and just a bit of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

@nrqsnchz

  • Helping @michaelarestad with FSE working on exploring how to make the template menu more intuitive.

@zebulan

  • Add heading level checker for heading block PR 22650 — Needs design and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) feedback. Also need technical feedback to make it work with headings that aren’t in blocks.
  • Add Table of Contents block PR 21234 — Needs all kinds of feedback/reviews to proceed. No progress in a month.
  • Polish Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block PR 21711 — Needs design feedback.
  • Refactor ReusableBlockEditPanel to use 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. PR 21181 — Needs review.
  • PreviewOptions: remove chevron from button PR 21192 — Needs feedback on how to move forward.
  • Block editor: use vanilla JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. Array.prototype.includes instead of Lodash PR 21063 — Needs reviews.
  • Refactor reusable block edit component to use hooks PR 21427 — Needs technical help to progress.
  • List block: add color controls PR 21387 — Needs technical help to progress. Blocked by theme editor-style conflicts. Solving this will make it easier to add color controls to other blocks like Archives and Categories.

@michaelarestad

  • Updating Full Site Editing end to end Figma prototype
  • Iterated on template part insertion
  • Planning to go through all 5.5 issues and provide any design help needed (particularly the ones that are on the fence)
  • Write up some thoughts on template editing vs full site editing
  • There are now 12 issues ready to build in the FSE project board

Open Floor

Table of Contents Block

Issue 22874 was created to extend the conversation on technical aspects of the Table of Contents block.

Group Block UI

Feedback was provided by Lu for UI on selecting Group Blocks part of Issue 20955. @michaelarestad invited those with comments to provide additional context in the #design channel. Rowan Remi Friedman mentioned other blocks also have the same selection challenge. @zebulan suggested persistent Block Navigator interface would make it easier to select nested blocks as found in PR 22113.

@youknowriad pointed out it isn’t possible to add virtual paddings or borders because the canvas need to match the frontend as closely as possible. This makes nested selections challenging and it’s a problem we’ll continue to iterate on over time

@matveb gathering feedback on the similar parent block selector which could help improve the UXUX User experience/UI. @zebulan suggested adding drag-and-drop functionality to the Block Navigator, to help situations when moving something from one nested group/column to @matveb gathering feedback on the similar parent block selector which could help improve the UX/UI. @zebulan suggested adding drag-and-drop functionality to the Block Navigator, to help situations when moving something from one nested group/column to another.

Accessibility 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. in the New Block Inserter

@afercia is logging several issues under PR 21080 around accessibility regressions in the Block Inserter. There are several PRs for the inserter but the team decided PR 21080 was the best place to consolidate newly noted items. 

Expose Reusable Blocks in the Inserter

@zebulan added a new Issue 22860 for discussion around ways to better present reusable blocks in the inserter which @matveb indicated should be addressed before WordPress 5.5.

#core-editor, #editor-chat, #gutenberg

Jb Audras 3:46 pm on June 3, 2020
Tags: ,   

WordPress 5.4.2 RC 1

WordPress 5.4.2 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). 1 (RC 1) is now available for testing!

There are two ways to test the WordPress 5.4.2 release candidate: try the WordPress Beta Tester 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 (you’ll want to select the 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. nightlies option), or you can download the release candidate here (zip).

What’s in this release candidate?

5.4.2 Release Candidate 1 features 20 bug and regression fixes on both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and default themes.

WordPress Core updates

  • #49956 – Spammers able to share unmoderated comments
  • #49749 – Registering rest routes with a slash-prefixed namespace give inconsistent results
  • #49798 – Default WordPress favicon in dark mode browsers
  • #49808 – WordPress 5.4: Deprecated: tag_row_actions is deprecated since version 3.0.0
  • #50121 – About page: correcting the order of headings
  • #50131 – Absent custom favicon triggers wp-adminadmin (and super admin) .htaccess/.htpasswd prompt on frontend in FIrefox
  • #49353 – button padding issue in edit plug on small device

Theme updates

The following updates were made to the default themes. You will not receive these updates if updating using the WordPress Beta Tester plugin. You must download the RC 1 package directly.

  • #37926 – Twenty Eleven & Twenty Twelve: Dropdown categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. 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. exceeds parent div when strings are long enough
  • #45865 – Twenty Nineteen: Consider decreasing the font size for widget titles
  • #48803 – Twenty Twenty: Custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. that doesn’t support author, shows author
  • #48916 – Twenty Twenty: anchor links don’t work in mobile menu
  • #49088 – Twenty Twenty: Add icon for g.page links (Google business profile)
  • #49316 – Twenty Twenty missed license for images.
  • #49320 – Twenty Twenty: aligncenter>figcaption missing text-align: center; feature
  • #49322 – Twenty Twenty: Submenu items disappear underneath the Cover 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.
  • #49435 – Twenty Twenty: inconsistent top and bottom margins for .alignwide and .alignfull on Chrome vs Safari (cross browser issue)
  • #49699 – Twenty Nineteen: Center- and right-aligned heading accents appear broken
  • #49793 – Twenty Twenty: Images in list blocks are not positioned correctly
  • #49893 – TwentyTwenty: TikTok and ResearchGate Social Icons
  • #49932 – Small Typo in Twenty-Twenty

What’s next?

Committers: The dev-reviewed workflow (double 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. sign-off) still applies when making any changes to the 5.4 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"..

The official 5.4.2 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. is still scheduled for Wednesday, June 10, 2020. Happy Testing!

#5-4-2, #minor-releases

Jeffrey Paul 2:17 pm on June 3, 2020
Tags:   

Core Team Reps for 2020+

Now that voting for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps has concluded, I’m pleased to announce that the new Core Team Reps for 2020 (and beyond) are Francesca Marano (@francina) and Jb Audras (@audrasjb)!

Francesca Marano

Francesca is the WordPress Community & Partnerships Manager at SiteGround, one of the largest independent web hosting companies where the quality of service stands above it all. Francesca is also part of the global WordPress Community Team and co-led 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. of WordPress 5.3 and 5.4. One of the things she is most proud of is her blogblog (versus network, site) C+B, which helped many creative female entrepreneurs find their path throughout the years. As an accomplished educator, community leader, and public speaker, you can find her around the world talking about hosting, WordPress, community, open-source, women in tech, and small businesses.

Jb Audras

Jb hails from Ardèche, France and is currently CTO at Whodunit, a well-known French WordPress agency. He started using WordPress in 2007 and became Widgets and Menus components maintainer a few years ago. Jb served as 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 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. over the last 2 years, took the role of release leadRelease Lead The community member ultimately responsible for the Release. on half a dozen of minor releases, and helped as focus lead on WP 5.3, WP 5.4 and now on WP 5.5. When he’s not contributing to WordPress, Jb loves to listen over and over to the same good ole Neil Young songs, learn new cool diabolo tricks and to practice bouldering.

From myself and @helen (the outgoing Core Team Reps), we’re excited to see these two wonderful contributors step up to their new role and are looking forward to a fruitful and productive year ahead for the team!

#team-reps

Jake Spurlock 10:54 pm on June 2, 2020  

Dev Chat Agenda for June 3rd, 2020

👋 Howdy, y’all. Here is the agenda for the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat happening tomorrow: Wednesday, June 3, 2020, 1:00 PM PDT

Announcements

  • 2020 WordPress Release Squads
  • Core 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. Announcements

Recent 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)./Core Posts

WordPress 5.4.2

  • RC planned for June 3rd, 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.

Component Check-In and Status Updates

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration
  • 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 Updates for 5.5.
    • Core Auto-updates
    • XML Sitemaps

Open Floor

Got something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

Kjell Reigstad 3:26 pm on June 2, 2020
Tags: ,   

X-post: Block-based Themes Meeting Agenda for June 3, 2020

X-post from +make.wordpress.org/themes: Block-based Themes Meeting Agenda for June 3, 2020

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

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

Paal Joachim Romdahl 9:57 am on June 2, 2020
Tags: , , ,   

Editor Chat Agenda: 3 June, 2020

Facilitator and notetaker: @ajitbohra

This is the agenda for the weekly editor chat scheduled for 2020-06-03 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.

If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #editor-chat

#agenda, #core-editor, #core-editor-agenda, #gutenberg