Editor Chat Summary: 27th May, 2020

This post summarizes the latest weekly Editor meeting (agendaslack 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, May 27, 2020,14:00 UTC and was moderated by @itsjusteileen.

Quick Announcements

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. This led to a quick discussion that the 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 can soon leave the experimental state!

@matveb chimed in to share the following later on to highlight that there’s plenty to do beyond the main projects that are underway if people want to/can help:

I wanted to mention that while many groups are focused on larger pieces of work (FSE, global styles, navigation, etc) 5.5 will require some focus on ensuring what exists right now is in good shape. That includes shipping the new design, patterns, the new inserter with new categories, new APIs and deprecations, etc.

Gutenberg version 8.2

Gutenberg RC candidate 8.2.0 was released this week with the stable release launched just after this meeting ended. Update your sites and check out what’s new.

Monthly Plan

There was limited discussion on the specifics of the current monthly priorities.

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.

@poena

  • Flagged this issue as needing a decision about the dynamic content with @matveb chiming in to say that there needs to be closer parity with the current theme experience as a start.

@paaljoachim

@nosolosw

  • Focusing on a new iteration of theme.json and early documentation for it.
  • Helping with reviews and other PRs, mainly in the areas of styles & 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. registration.

@michael-arestad

  • Dropping a new figma prototype very shortly on inserting saved (and new) template parts that deviates from previous designs and the current implementation. 
  • Planning to create a new issue with designs/discussion around a vertical grid for template building (and general layout things).
  • Planning to update the end to end full site editing prototype (i4).

@sageshilling

  • Working with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-media data flow, design gallery, image block, gallery patterns.

@mapk

  • Working on the widgets screen with @jorgefilipecosta.
  • Updating UIUI User interface issues/PRs with Figma label.
  • Providing feedback on FSE work.
  • Redesign of spotlight mode with @youknowriad.

@karmatosed

  • Focusing deeply on navigation with a side order of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..

@andraganescu

  • Various work on the navigation screen
  • Added new suggestion types to LinkControl
  • Continued the work on adding delete to Entities

@nrqsnchz

  • working with @michael-arestad on inserting saved (and new) template parts (FSE).

@zebulan

  • Add RichText split-at-end/merge/remove behavior.
  • Add usePrevious hook to @wordpress/compose package.
  • Use toolbar exclusively for heading level controls in Heading Block
  • PR to replace instances of Lodash.includes with native JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. [].includes in the block-editor package is awaiting reviews.
  • PR to refactor ReusableBlockEditPanel to use ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 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. is awaiting reviews.
  • PR for the Table of Contents Block needs technical help/feedback in order to progress along with 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.
  • PR for the Reusable Block edit component has made progress thanks to feedback/help but has one remaining behavior issue that’s blocking it.
  • Polish Custom HTML block PR is ready to go, assuming the stylistic changes are okay. Please provide design feedback.
  • Started a PR to update the Quote Block to use a light block wrapper but got stuck and need technical help to move forward. Solving this will help other blocks use light block wrappers.
  • Started a PR to add color controls to the List block but running into problems with style conflicts on most default WordPress themes.
  • Started a PR to add a heading level checker to the Heading block, based on prior efforts in this issue.

@itsjonq

  • Adding Padding controls
  • Working on video Background position controls
  • Working on cover image auto dominant colour detection

Open Floor

@youknowriad shared helpful guidelines for folks creating PRs to make the changelog easier to automatically compile.

  • When working on experimental screens and features, apply the [Type] Experimental label instead of Feature, Enhancement, etc.
  • When working on new features to technical packages (scripts, create-block, adding  react hooks, etc), apply the [Type] New API label instead of Feature, Enhancement, etc.
  • When fixing 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. or making an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to an internal tool used in the project, apply the [Type] Build Tooling instead of Bugs, Enhancement, etc.
  • In PR titles, instead of describing the code change done to fix an issue, consider referring to the actual bug being fixed instead. For example: instead of saying “Check for nullable object in component”, it would be preferable to say “Fix editor breakage when clicking the copy block button”.
  • Take the time to choose the right [Type] label for your PRs. With some updates to the changelog command (type priorities), we should be able to support multiple types on a PR for some of the examples above.

Next step: @annezazu will look into updating both triage documentation and contributor documentation as appropriate.

Will core-editor participate in Contributor Day and should this be mentioned to participants? Raised by @itsjusteileen.

Yes! @youknowriad is planning to do a quick zoom chat to help people setup a Gutenberg environment at the beginning of the day. To come prepared, please have “Docker” + Latest node.JS LTS setup. This is also mentioned above under announcements.

Listing names in the code owners document to better understand who can be pinged for help/a review. Raised by @paaljoachim.

Paal encouraged everyone to review this document and keep it up to date. @karmatosed mentioned that relying on solid labeling alongside bringing in specific people from that list will likely help more for getting everyone to see issues appropriately.

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

Core-Editor Dev Chat May 20, 2020

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, May 20, 2020, 10:00 AM EDT. These meetings coordinate collaboration in the development evolution of 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/ project. You can find today’s agenda here. Facilitator: @pbrocks

Recap

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 5.5 — Checkout the Planning Roundup here

Gutenberg items to ship:

  • 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. UIUI User interface Redesign
  • Block Patterns
  • Hundreds of small improvements and  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

Gutenberg items we hope will ship but we’re not certain yet due to the deadlines:

  • Navigation screen and block
  • Widgets screen block-based
  • Global styles

Gutenberg version 8.1

Released last week containing:

  • Pattern searching
  • Copy block
  • Iterations on experimental screens
  • Embed transform to paragraph block.

Monthly Plan

What’s next in Gutenberg outlines the goals for May. There was no additional discussion around the current goals.

Task Coordination

@sageshilling

  • working with core-media data flow, design gallery, image block, gallery patterns…block_id

@mkaz

  • Diving into docs and addressing needs highlighted here Issue 22151

@karmatosed  

  • My main priority right now is navigation, navigation and oh yes navigation! I am working with some awesome peeps there.
  • I have a side order of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and ensuring any tickets I touched have feedback.

@andraganescu

  • As part of the ongoing work on the experimental navigation screen, I have added a _delete_ functionality for core data entities. If you are someone who uses entities this is interesting to get right so any feedback is welcome:

@youknowriad 

  • I’ve worked on a new CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. command to automate performance tests across branches/versions
  • Fixing some bugs related to Color palettes
  • Looking at some UI parity work between edit-post and edit-sitesite (versus network, blog)

@q

  • I’m continuing to help improve the Cover block, mostly around customization and the UI/UXUX User experience of those controls.
    • Adding Padding Controls
    • Improving Color controls
    • Improving Background controls

@ajlende 

  • I’m working on getting the first pass / rough draft of rich image editing now that it’s unblocked again. Still need to know how best to limit for testing as experimental and where it should live. 

@michaelarestad

  • I’m working on template part flows, how they could fit with a site-wide column grid, and hopefully flows for setting up a new template.

@nrqsnchz

  • Merged the new Welcome Guide design, which includes support for prefers-reduced-motion
  • Worked on and merged a couple of block patterns
  • Fight Travis tests, as I usually do

@nosolosw

  • My main focus was the managed CSSCSS Cascading Style Sheets. PR. It’ll remain my main focus for next week.
  • 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. docs generation: audited & updated the list of packages (some are up for grabs, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me if you’re interested in helping and don’t know how to do it) and documented the steps.
  • A bunch of other things: help with reviews, enable only stage-4 JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. syntax, etc.

@nfmohit 

  • I’m still working on a vertical style for the Buttons block.

@isabel_brison (tellthemachines)

  • working on a prototype for moving blocks between nesting levels with the keyboard and would love some feedback and testing on it! Also addresses the inability to move between nesting levels in navigation mode.

Open Floor

@zeb asks for review of the PRs listed in the agenda comments 

@annezazu The form for the Full Site Editing outreach project is open until May 22nd now: 

@mkaz

I’ve got one with regards to documentation I think we should revisit the idea of publishing off 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. tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.), and instead be versioning at the unit level. For example, the core docs include the version and changelog for each function. 

@nickthegeek

Looking for comments/help with this Issue 22332 Add screen reader only text format

@noisysocks asked for comments and review on Navigation

`A few of us (@talldanwp @andraganescu @isabel_brison @zieladam @karmatosed) have been building out a rudimentary replacement for nav-menus.php which is based on the Navigation block UI. This new screen is in a semi functional state and you can see it by switching on the Navigation experiment in the latest Gutenberg.

A new [Feature] Navigation Screen label tracks issues to do with this new screen, and the Navigation in 5.5 project board tracks work that we think is important for this feature to land in WordPress 5.5. If you’re interested in helping out with this project, please feel free to pick up one of the tasks in the project board. You can also ping me (@noisysocks) if you have questions or need guidance! `

@zeb expressed concerns with the current navigation interface, specifically referencing wanting to see the following issues addressed;

  • Issue 22089 Navigator iterations: ellipsis and movers
  • Issue 22297 Block Navigator/Navigation: Drag & Drop

The in-depth conversation can be followed in Slack archives. With the team in agreement to continue the conversation in 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/ with @karmatosed noting the navigation feature is still under an experimental flag and is in an iterative design process.

#meeting-notes #core-editor-summary

Editor Chat Summary: 13th May, 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, May 13, 2020,14:00 UTC and was 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/ 8.1.0

Gutenberg 8.1 RC was released on May 11th and is on track for a final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. 8.1 is focused on performance improvements, 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 multiple enhancements around several areas of the editor and the experimental screens/features. Outside of those focuses, there are also new features like new transforms, pattern search, and a new testimonials pattern.

Weekly Priorities

There was limited discussion on weekly and monthly priorities@andraganescu noted that the new navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. screen is coming together! Overall though, Full Sitesite (versus network, blog) Editing (FSE) is a major focus right now and can be followed here with the overall plan shared here.

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.

@nosolosw

  • Main focus has been “Global Styles”. Currently, iterating on some framework tasks that need to be to unlock before resuming work on the UIUI User interface. This will be the focus for this week too.

@aduth

  • Working on some documentation and framework-level improvements, largely summarized in this slack convo.
  • Refreshing and splitting off work around renaming 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. categories.
  • Next up, continuing work on renaming block categories plus follow-up work around block context.

@youknowriad

  • Did two zoom chats to help contributors (one in #core-editor, one in French WordPress slack).
  • Trying to land categories support for patterns.

@nrqsnchz

@retrofox

  • Made progress in the Tips approach. It’s now possible to register tips defining the scope, descriptions, and other parameters.

@earnjam

  • Handling some PR reviews to help with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. starting with the list of non-draft PRs with no review, less than 2 comments, and sorted by least recently updated to try to find anything that has slipped through the cracks.

@mapk

  • Spent time triaging issues.
  • Search block enhancements.

@itsjonq

  • Continuing to add features to Cover block via new control UIs (“Design Tools”). In doing so, also building a set of incredibly robust and feature rich control primitives (e.g. Input).
  • Longer termer goal would be to (hopefully) refactor/replace existing controls within Gutenberg with these ones. These components would of course be available for 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 authors as well, enriching the UI experience of the Gutenberg ecosystem as a whole.

@vindl

  • Working on allowing extensions/replacements of editor close button which is part of this issue. It’s already merged for the site editor, and now I’m looking to expand it to the post editor too.
  • After the above work wraps up, will return to site editor UI tasks

@michael-arestad

  • Working on template part creation/manipulation design patterns. Right now, exploring how they might work as sections. This could be really slick when building templates.
  • Continuing on this path this week and will likely spin up some zooms if anyone wants to help or just watch! Links will be shared in #design.

@sageshilling

  • Working on the image and gallery blocks.

@andraganescu

  • Working on the navigation screen– just merged menu location management.
  • Will continue to work on various issues on this project for the next week.

@zieladam

Working on the experimental navigation screen, in particular:

Open floor

Do we instead of listing packages and versions, need to list components and versions? Raised by @paaljoachim.

This discussion point was raised in reaction to a comment from @clorith in this trac ticket on adding Gutenberg plugin version information to the Site Health section. Right now, this tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. issue needs feedback to keep the issue moving. It was agreed that there’s no easy solution to this partially because WordPress versions includes features and bug fixes of various versions of Gutenberg. This makes handling bug reports tricky for example.

Next step: Taking the discussion back to the track ticket!

Do we need to apply a max height for the style placeholders in the inspector? Raised by @munirkamal.

The problem right now is that placeholders need to have a preview so if the block is quite large the the preview is too. @matveb chimed in to say that previews are loading example content now so this decision is up to the block author. However, if an example is not provided it falls back to actual block content which is where a max-height could be useful.

Next step: A “Needs Design” Label was added to the issue for design to explore further.

What time and day would work for the discussion about full-site editing and the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. customize component? Raised by @dlh.

The original proposed date and time was 20:00 UTC on May 25th but this time may not work well for the people working on Full Site Editing. @youknowriad suggested meeting more around 15UTC/16UTC but wants to hear from others. Tied to this, @aduth noted that May 25th is Memorial Day in the United States which

Next step: If you’re interested in attending this meeting, please share in the comments below what time might work best. Notes will be taken and posted either way if you can’t 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.

Can we add a block ID to each block that is unique and stable to help connect server data to client data? Raised by @sageshilling.

This came up as part of work done on the image and gallery blocks (full context here). There have been various discussions about this historically in the early days of Gutenberg. These discussions always concluded that while there is a need for this from time to time we don’t want to pollute markup and/or we don’t want to keep two separate things in sync. Before discussing anything technically, it was agreed that a case needs to be made for why it should go in core and why extension-based solutions are not apt.

Next step: @sageshilling will collect use cases and details in a post 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. to propose this idea.

#meeting-notes, #core-editor, #editor, #gutenberg

JavaScript Chat Summary – April 28th, 2020

Below is a summary of the discussion from this week’s JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. chat (agenda, Slack Transcript)

Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Agenda: Changelogs for npm packages (@gziolo)

Slack

Discussion was around:

  • How 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 easier to distinguish unreleased changes.
  • Can we somehow inform about the estimated date of the next npm 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.?
  • Possibility of adding linting rules.
  • Possibility of using a standard format (such as keepachangelog or atlassian changesets).

Action:

Some proposed next steps are:

  • Revisit some of the changelog verification work (@aduth)
  • Create a proposal for very standardized formatting of changelogs.

Agenda: ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Fast Refresh (@gziolo)

Slack |Github comment

React Fast Refresh is coming to React ad Greg was wondering if we should start testing it with wp-scripts start as well.

Actions:

  • Potentially experiment with things like React Fresh Refresh by putting it behind an env flag to start.

Agenda: Restoring TypeScript Types (@aduth)

Slack |Github

Of note is that with the work in the linked pull, it was decided that the project would be using React types directly rather than trying to abstract them through @wordpress/element.

For most consumers I hope it’s a detail most folks won’t even notice. It’s particularly important when doing more complex type operations. React exposes a lot of mapped types (think of functions on types) that will be necessary in some cases, but for the most part folks will continue to do import { Component } from '@wordpress/element'; and get all the right types.

Jon Surrell

Open Floor:

News Roundup

This roundup contains a few links 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/ and JavaScript related news curated (and commented on) by @nerrad

Other Random Stuff

#javascript, #meeting-notes

Editor chat summary: Wednesday, 29 April 2020

This post summarizes the weekly editor chat meeting on Wednesday, 29 April 2020, 14:00 UTC held in Slack.

WordPress 5.4.1

@jorgefilipecosta said WordPress 5.4.1 was released on the last Friday and that the RC includes all the editor fixes expected on the final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Concluding that unless we discover something critical until the release in some hours, he does not expect any additional task on the editor side. The editor fixes included in WordPress 5.4.1 can be checked at https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+sort%3Aupdated-desc+label%3A%22Backport+to+WP+Core%22+is%3Aclosed.

@jorgefilipecosta gave public kudos to @whyisjake or handling the tasks needed for the release!

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

@aduth shared the following update regarding Gutenberg 8.0.0:

The 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). was released on Monday. There were a couple of bugs that were discovered between then and today and will be included as part of today’s release. Everything is looking okay on my end as far as releasing Gutenberg 8.0 today.

@youknowriad shared that the highlights of the release are:

  • Patterns moved to the inserter and the inserter as a panel
  • Add subscript and superscript formatting options

@jorgefilipecosta said that the last coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. releases included ten Gutenberg releases. Gutenberg 8.0.0 is the fifth Gutenberg release since WordPress 5.4 so more or less half of the things WordPress 5.5 editor is going to include are already out.

Monthly Plan & Weekly Priorities

Soon we are going to have the monthly plan for may. Regarding the April plan available at https://make.wordpress.org/core/2020/04/01/whats-next-in-gutenberg-april/, @mapk said he thinks everyone did really well and @youknowriad agreed and said we’re on a good pace these days and we’ll need to start thinking about the High-level priorities for May.

Task Coordination

@youknowriad

Has been working on some follow-ups to the Patterns and Inserter work:

  • Support search
  • Rename APIs
  • 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). the core patterns translatable

He said there are still a lot more follow-ups there. H will continue there and will also keep an eye on the FSE work in general.

@aduth

Has been focused on:

  • 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. context: The first iteration landed last week. It still needs follow-up work to flesh out the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 APIs.
  • 8.0 release: Wrangling, also made changes to and helped land a new changelog generator tool which will be helpful to expedite the process for future releases.

@mcsf

Has been involved in PR reviews and issue discussions in

  • Pasting, transforms
  • Block content, versions
  • Full-sitesite (versus network, blog) editing and block-based themes

@nosolosw

In the past week, his main focuses were:

Next, he is going to resume work on the block style system, global styles, etc.

@q

Has been focused on:

  • Cover Block: Continuing work on padding controls and alignment tools

@sageshilling

Working on the gallery, looking at keeping the current gallery block, while building out a pattern(s) for the gallery, as a container with block images. Working on the data flow, design flow, and then build out from there. 5.5 will have both the current gallery block, and the pattern gallery(ies).

@andraganescu

Has been AFK for a week. Attended some of his open work about the new navigation menus screen, refactored the author block, and re-added setting post author from it.

@nrqsnchz

Is working on Iterations on the welcome guide and will soon start helping with FSE work, mainly Inserting existing saved template parts and Edit Site: Creating a new template from scratch.

@michaelarestad

Is focusing on:

@mapk

Is following up on a few PRs:

  • Clearing the publish date with @earnjam
  • Labels on buttons with @nicolad
  • Looking at drag n drop and mover interactions a bit more.

@jorgefilipecosta

During the last week, helped/reviewed the tasks needed for 5.4.1. I submitted many bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and also some enhancements to the 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. For the next week, he wants to continue some enhancements to the widget screen and to work on undo-redo and make sure it works as expected on the three screens: edit-post, edit-site, edit-widgets (it seems we have some issues on the last two). Lastly, he plans to continue interactions on some PR’s he has, namely CSSCSS Cascading Style Sheets. vars for predefined colors, as that PR is impactful for global styles.

@gziolo

Plans to continued on block editor features and last week did the following tasks:

  • worked on CSS support for build and start commands from wordpress/scripts
  • landed a few smaller bug fixes
  • helped @ajlende to land debugging support for unit and e2e tests

@karmatosed

Her main focuses are navigation and design triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. Said that we are getting in a good place with nav-menus.php thanks to so much amazing dev work. Shared that the navigation project board is a great place for dropping in for feedback there and testing as the release surfaces.

Open Floor

Code debugging

@john said:

I’m confused about how to debug custom gutenberg blocks when you need to see and play with the gutenberg source code. If the docs are unclear, and I need to poke around in the source code, I can’t because all the packages are run via build files. So if I was to run a “console.log” to see what happens in the getSaveElement filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.… nothing happens.

Is there a proper way to access the entire codebase so I can see what’s happening inside functions that gutenberg provides 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? I’m not skilled enough to just READ the code. I need to actually be able to run console.logs inside the Gutenberg core while developing a plugin. But I can’t find a way to do that.

@youknowriad referred that maybe nothing happens because it’s not executed at all. And made some questions to better understand the problem.

@aduth said:

@john Instead of using the plugin from the plugin repository, you can clone the source code from 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/ to your wp-content/plugins. From there, you can treat it like you would when developing in Gutenberg itself, starting the build process with npm run dev or npm run build from within Gutenberg. You should see any changes to the source reflected in the plugin running on your site.

https://github.com/WordPress/gutenberg/blob/master/docs/contributors/getting-started.md

Asset Licences

In the agenda of the meeting @poena said:

If there has not been one, there needs to be a license review of all third party assets.

I was not able to find any information for the included images (for example, block patterns and FSE demo content) and icons (social media).

Licence must be considered when any such element is included in the plugin.

I am not familiar with how you review licensing for third party scripts, but I am not able to find a list of licenses and copyright anywhere.

@aduth said that there is a license check tool used for all third-party dependencies installed through NPM. And @youknoriad said he knows that all images used in patterns and block examples are public domain images and that each time we want to use a new one we create a 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. ticketticket Created for both bug reports and feature development on the bug tracker. for it and check the license there.

@poena asked if it is correct to not even credit the public domain images?

@aduth and @youknowriad both said that although they are not lawyers they believe public domain does not require any attribution.

@poena followed up the question and asked about the icons.

@youknowriad said wordpress/icons are a mix of Dashicons and custom-built icons so he believes all of them are WP made. I know some might have been inspired by Material ones.

@poena said that when people take something from core/GB and place it elsewhere, We can’t just say that the images have the same license as core/plugin because core/plugin is GPLGPL GNU General Public License. Also see copyright license. and some images may be public domain for example.

@nrqsnchz said that this was why we decided to go with text-only patterns for now. We couldn’t find a good library of images that was also compatible with WP’s license.

@aduth said It would be good if it could be communicated something consistent like “all images and content distributed through patterns are [a: public domain][b: distributed as GPL]”.

@youknowriad said if a plugin/theme is GPL, it can just reuse anything WP provides if not, you need to check per case. @poena followed up saying It’s not that simple and that we know that from twenty nineteen.

@poena concluded the topic by saying that she just wanted people to be mindful when they make their pull requests.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting, #meeting-notes

Dev Chat Summary: 29th April, 2020

@francina facilitated the latest weekly Dev Chat on this agenda; here’s the Slack transcript.

Announcements

@whyisjake announced the official release of WordPress 5.4.1.

The group took a moment to cheer this second 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. accomplished during the pandemic. To quote @whyisjake

“Thank you all for helping get out this release. It’s an amazing example of the collaboration, dedication, and spirit of open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.. Releases like this really 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). the web a better place.”

@whyisjake

Upcoming Releases

Work is underway for WordPress 5.5 – and has been, since the 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". at 5.4 RC2. This is prime time for you to actively develop, test, give feedback and more. @davidbaumwald has scheduled the first 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 for Tuesday, May 5, 2020, at 18:00 UTC and has already published it on the meetings page

Highlighted/Blogblog (versus network, site) Posts

These posts need your feedback, as soon as you can get your thoughts together:

5.4 Retrospective – Call for feedback – Deadline April 30

Please focus your feedback on processes only. Next week @francina will collect it all and publish a recap much as she did for 5.3.

So far, chat participants noted there hasn’t been a whole lot of feedback from 5.4 – why not? Speculation included:

  • the release went particularly smoothly, 
  • privacy concerns,
  • the state of the world,
  • some combination of the above! 

WordPress 5.5: Call for Tickets – Deadline April 30

Please add the tickets you most want to see land in 5.5 to the comments of this post.

Of course, please remember that there are no magic bullets – nobody can guarantee your ticketticket Created for both bug reports and feature development on the bug tracker.’s inclusion in the next release. With that said, the team (which does include you!) can only fix what we know is wrong. So please bravely share!

Proposal: Core Team Rep Elections 

@francina and several others admitted they were confused about whether this post is for adding nominations or getting feedback on the idea of a nomination process ahead of a second post to come, to add nominations. After some discussion,  the group decided to ask @jeffpaul for a separate nomination post. He agreed, and it’s up!

WCEU Online 2020 Contributor Day

Thanks to the confusion around Team Reps, since that’s who works with the 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/. squads of every WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., the group tabled the discussion of WordCamp Europe Contributor Day until next week.

REST API: Decision on Introducing a dashboard namespace 

In the words of the post, “the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. team has decided on giving major features their own namespace. For example, wp-sitesite (versus network, blog)-health and wp-customize.” This should help all sorts of people find these features and hook into them a lot more easily.

Components Check-in

@garrett-eclipse announced that Privacy + Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site will share a focus in 5.5 to bring the relevant tools to multisite. Teamwork makes the dream work!💥

@azaozz has been investigating the best way to update jQuery: https://core.trac.wordpress.org/ticket/37110#comment:105. The work will take three WordPress releases and can start in 5.5. Please review his plan! 

@desrosj is planning to update the SimplePie library and, possibly, PHPMailer in 5.5. He welcomes your reviews and thoughts on both.

@audrasjb updated the group on Plugins & Themes Auto-updates. This week the merge proposal goes live on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. — and patches on the tickets, too.

Discussions

How long do we let a merge proposal percolate?

@whyisjake asked: in light of the auto-updates work, how much time do we normally let a merge proposal percolate before moving forward? A lively discussion followed, with resident historians @azaozz and @jorbin chiming in and concurring: it obviously depends on the proposal, but generally speaking, 1-2 weeks and a blog post is reasonable.

What are the plans for 5.4.2?

@asif2bd asked when 5.4.2 might be released. The answer: only if necessary.

If nothing major comes up in the next couple of weeks post 5.4.1, we’ll move onto 5.5. Now, @desrosj did create a 5.4.2 milestone when it became clear 5.4.1 wouldn’t include a bundled-theme update, in case we need it for backporting later. For now, there are no compelling reasons to do another minor — but stay tuned! Things can always change. 

Friendly Reminder

Finally, @francina reminded the group that you don’t have to wait for devchat to raise issues for discussion. In fact, you should really start the conversation ahead of time.

Here’s how: 

  • Post something on the blog – async conversations starts
  • Schedule an extra meeting here or in the relevant channel and advertise it far and wide so people can attend
  • Post a recap in the blog
  • Rinse and repeat as necessary.  

Take care!

#5-4-1, #5-5, #meeting-notes, #devchat

JavaScript Chat Summary: Tuesday, April 21, 2020

Below is a summary of the discussion from this week’s JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. chat (agendaSlack transcript).

Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Package updates and type checking support

@aduth shared the following announcement:

There was a round of WordPress NPM packages updates published last week. These were the first to include first-party TypeScript types :tada: Unfortunately, there were some unforeseen conflicts with a few of them, and some had to be quickly backed out temporarily and will be republished later.

More about the issues can be found here: https://github.com/WordPress/gutenberg/pull/21613.

Including follow-up tasks: https://github.com/WordPress/gutenberg/pull/21613#issuecomment-615314861

@jonsurrell added that we conflicted with 3rd party types from DefinitelyTyped. In isolation, there was nothing strictly wrong with the new types. In the future, the DefinitelyTyped types would be replaced by packaged (1st party 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/) types, but in the short term, it’s in everyone’s best interest to remain compatible.

The solution to remain compatible with DefinitelyTyped is not yet clear. @jonsurrell created the following issue to discuss it https://github.com/WordPress/gutenberg/issues/21767. Feel free to leave your thoughts there.

Ongoing WordPress packages tasks

@aduth collected and shared the following list of tasks happening around WordPress packages:

@adamsilverstein said that for the underscore to lodash work, the biggest win would be to remove the underscore dependency from the media library. @adamsilverstein volunteered to work on the task.

Regarding the on-demand installation of Puppeteer, @aduth demonstrated great excitement with the change. Saying it will reduce the installation time for new development environments pretty significantly, especially because it’s also part of the general-purpose wp-scripts. @aduth concluded this improvement in new setup time would be useful in contributor days.

#core-js, #javascript, #meeting-notes

Editor Chat Summary: 22nd April, 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, April 15, 2020,14:00 UTCand was moderated by @paaljoachim.

WordPress 5.4.1 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.

Note: There was a miscommunication around this release and these notes originally expected the launch to happen the same day as the meeting. This has been corrected.

@jorgefilipecosta shared a comment prior to the meeting detailing the plan for 5.4.1 RC. All 5 PR’s to include were 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/ 7.9, meaning they were tested in at least one 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. This RC release is slated for Friday with the full release planned for next Wednesday per an update from @whyisjake.

Weekly Priorities

No discussion on weekly or monthly priorities

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.

@zebulan

  • Needs reviews for a Table of Contents PR. Ideally would like a G2-style 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. icon, but can merge with the current dashicon.
  • Needs technical and design feedback on a PR to update the heading level control in the Heading block.
  • Needs reviews for Two Reusable Block PRs with 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.
  • Needs reviews for a Custom HTML Block PR.
  • Needs reviews for 3 quick PRs: polishing black wrapper, new icon for navigation block, and matching SmugMug URL regex to core.
  • Stuck on a List Block Color Controls PR after running into a problem around priority with styles between the default editor and the block. 
  • Ran into an issue with a Navigation Links PR where focus doesn’t move to the previous navigation link after removing the block. 

@get_dave

  • Has been working on the ability to create a Navigation block from existing WP Menus. @karmatosed posted a new design route that we need feedback on if people have time to review.  

@marek

Open floor

Should we keep CONTRIBUTORS.md? Raised by @soean.

Only 140 people are listed, but we have more than 550 code contributors, so it is not up-to-date. We don’t use this file in other repos. 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/ -> WordPress connection is now built in on wp.org.

Discussion ticket started by @mkaz:

  • We don’t use this kind of file in other WordPress repos. 
  • The file overall is a bit confusing and it doesn’t seem to be a great way to acknowledge all contributors currently. 
  • There are inconsistencies in who is added with some long term contributors missing.
  • The file itself seems to be for highlighting non code contributors to the project.
  • The contributors tracking that GitHub provides only shows contributors for specific timeframes. 
  • @soean shared this neat project https://allcontributors.org/ that might be interesting to explore.

Next Steps: @mkaz will update the file to provide a link to the code contributors listed on GitHub, followed by the list of non-code contributors. If people have other thoughts, please add to the ticket to discuss. 

Is using `render_callback` a good solution for handling conditionally loading assets? Raised by @mkaz.

This question is based on a long standing but stalled out ticket trying to address this within Gutenberg automatically. @mkaz wrote a post examining `render_callback` but this approach  requires each plugin/block to set it up. If this is determined to be a best practice to move forward on, we should likely update documentation to encourage developers to take a similar approach. 

Next Step: We didn’t have enough folks online to have a robust discussion about this so @mkaz will create a discussion ticketticket Created for both bug reports and feature development on the bug tracker. to carry the conversation forward. 

Problems with the Drag & Drop Experience explored in this ticket. Raised by @jules-colle.

There are general concerns around how the current experience is continuing negative perceptions of Gutenberg for end users. Right now the problems are adding up leading to both a rough experience and an overwhelming set of problems. Right now, it seems the issues would benefit from being broken down into smaller pieces.  

Next Step: Thoughts are welcome on this main ticket.

Should we give more folks access to @here abilities in slack?

At the beginning of the meeting, we realized no one had permissions to @here in slack to alert folks to the meeting. This led to a quieter meeting this time around but we likely should expand access to those who run meetings so we can ensure better meeting engagement.

#meeting-notes, #core-editor, #editor, #gutenberg

#core-editor-summary

Editor chat summary: Wednesday, 15 April 2020

This post summarizes the latest weekly Editor meeting, 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, April 15, 2020, 14:00 UTC.

WordPress 5.4 Adderley was released and Issue/PR’s for WordPress 5,4,1 are being kept track of using “Backport to WP Core” label.

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

Gutenberg 7.9.0 was released which introduces 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. design tools, new block patterns, lighter block. Check out 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. note for more details.

Priorities

The priorities are still the same though and available here

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

  • Working on the new inserter UIUI User interface, hopefully, it will land in the next 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
  • PR reviews Cover Alignment, Block Context 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. and more
  • Triaged and closed issues
  • Worked on various fixes for 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 &button block
  • Continue work on the inserter UI

@zebulan

@sageshilling 

@itsjonq

@michael-arestad

  • Progress on end to end full sitesite (versus network, blog) editing prototype
  • Working on multi-entity saving iterations
  • Working on navigating pages within the editor
  • Will be working on the home page indicator for templates
  • Proposed iterations on inserting existing or new template areas (partials) – [issues: 1 2]

@brentswisher 

  • Continue to work on adding storybook stories and the story shot-addon.
  • Work on a PR to remove the story shot integration, which should speed up and simplify the story creation process, as well as 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). the js unit-tests in Travis more stable

@karmatosed

  • Focus on navigation for this week, Both in nav-menus.php and iterations to the block

@andraganescu

  • Worked on various issues around the navigation menus replacement experiment

@aduth

  • Progress on a new “Block Context” API
  • There have also been some interesting side-effects of this work, including an experimental (backward-compatible) revision to the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 render_callback function signature to receive the full block object, not just the attributes.
    https://github.com/WordPress/gutenberg/pull/21467

@desaiuditd 

  • Trying to move 2 PRs ahead which were stale for quite some time.
    • https://github.com/WordPress/gutenberg/pull/17413 This could potentially fix some related bugs around embeds
    • Trying to achieve new workflow suggestions https://github.com/WordPress/gutenberg/pull/17311 Have made little progress.
    • Waiting for feedback on this one introduces new ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. hook useFilters  for primitive JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. types

Open Floor

@check2020de

Fixing height hardcoding for spacer block https://core.trac.wordpress.org/ticket/49862#comment:3

  • it is not good that there is a hardcoded 20px value on the spacer
  • however, the reason is that we need a min-height to make that block selectable by tapping and for better 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) in general
  • however, it may be that the incoming block padding/margin will also solve this problem
  • needs further discussion & decision to better handle the spacer on desktop & mobile

@mboynes

 How does one petition to get 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/ issue reopened? asking in the ticketticket Created for both bug reports and feature development on the bug tracker. doesn’t appear to do the trick

Looking if/when we can get to it:

On the topic of closing issues, as a relative outsider to the project, decisions to close issues feel somewhat unilateral to me. I would like to propose a new process where closing issues requires two people (except in obvious cases, like closing as a duplicate). taking a page from the stack overflow book, the first person could add a “close-vote” label, and someone else, in reviewing “close-vote” issues could then review and close it.

We have some guidelines already about issues triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. here https://developer.wordpress.org/block-editor/contributors/repository-management/

It’s totally fine to close and reopen issues.

@joostdevalk

Pinning behavior for plugins has changed

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

@marekhrabe

Looking for a designer to confirm or update the approach on Media & Text resizing we came up a year ago and it got stale.

More info https://github.com/WordPress/gutenberg/pull/14483

#meeting-notes, #core-editor, #editor, #gutenberg

#core-editor-summary

Editor chat Summary: 25 March, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 25th March 2020 held in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Moderated by @get_dave.

WordPress 5.4 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.

  • WP 5.4 RC 4 was released yesterday (Wednesday, 24th March)
  • WP 5.4 RC 4 adds the Editor packages (Trac: 49688)
    • The editor PR’s that were cherry-picked into 5.4 can be checked on PR: 21083
    • Remaining issues can be checked and triaged on this board

Monthly Plan & Weekly Priorities

  • Revisit March master plan
  • @youknowriad Progress is good
    • Global Styles: We’ve added CSSCSS Cascading Style Sheets. vars to multiple blocks and more coming
    • Full Site Editing (FSE): still some challenges (Context 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.) and we’re improving the Edit Sitesite (versus network, blog) screen at the same time
    • Patterns: Thanks to @nrqsnchz we have a dozen patterns on the works and the UIUI User interface is being iterated on
  • Check out some of the Overview issues here for a better outlook

Task Coordination.

  • @nosolosw will work on global styles for edit-siteand reviewing related PRs
  • @youknowriad worked on CSS var support for multiple blocks, Edit Site improvements and PR reviews
  • @isabel_brison worked on Navigation 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. and Triaging 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) audit board
  • @Johnston Philip wants to help review things
  • @Jon Q has been working on adding more style controls to Blocks.
  • @karmatosed has been focusing on navigation, global styles and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
  • @Bart Kalisz has been reviewing some Good first review PRs
  • @get_dave worked with @andraganescu to allow Navigation Blocks to be created from existing WP Menus: PR 18869
  • @michael-arestad works on multi-entity saving and navigation methods within the editor
  • @Brent Swisher will continue working on storybook stories

Open floor

  • @soean asked that we announce WPBlockTalk – a free, online event for all things block editor happening on April 2nd
  • @paaljoachim asked about a progress with the Reusable Block feature. Progress can be monitored here.
  • @paaljoachim also raised awareness on PR 18718 about refactoring cover background controls.
  • @paaljoachim asked if we have a “how to create a PR info area: in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor handbook. Closest match is here.

Post Meeting discussion

There has been some discussion post meeting between @matveb, Pablo Honey and @mapk about the limitations of designing more complex block patterns.

To sum up the way forward is to provide the best patterns we can which don’t don’t suffer from the lack of tools and when we run into limitations to distill them down to improvements on the blocks themselves.

#core-editor-summary, #meeting-notes