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

Editor features for WordPress 5.5

In Slack recently, contributors to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor component were encouraged to focus on features merging into WordPress 5.5. The question arose around which specific tasks required focus. The goal of this post is to communicate the features that will be included and to highlight other features that need help to be included too.

Definite inclusion

Features that need your help

To test the following features, turn them on within 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/ 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 Experiments screen.

If you’re uncertain about how to contribute to any of these features, please comment below. There are many issues that focus on a single feature, so while the work is spread out, there are several paths for contributing.  We need additional help testing these features in the plugin, reviewing PRs which can be done using http://gutenberg.run/, and leaving important feedback.  Thank you for contributing!

Thank you to @andreamiddleton, @annezazu, and @chanthaboune for their feedback on the content and phrasing of this post!

#5-5, #editor, #gutenberg

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

Ways to keep up with Full Site Editing (FSE)

As work on Full Sitesite (versus network, blog) Editing continues, it’s important that communication around the project is made explicit so everyone can follow along appropriately. Each person will have their own unique needs in keeping up with a project of this scale so what follows is more of a catalogue of ways to keep up rather than a recommendation for how to do so. 

Yearly:

The WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Roadmap with Four Phases of 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/ updated by @chanthaboune and/or @matt. This is the highest level overview of the changes coming to WordPress.

Quarterly: 

Quarterly Updates from Contribution Teams, coordinated by @chanthaboune. These updates give an overview on what each team is working on, struggling with, and how to get involved.

Monthly: 

“What’s Next In Gutenberg?” posts. These updates are wrangled by the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team and highlight what’s planned for the coming month of work on Gutenberg. 

Block Based Themes Chat. These chats are currently wrangled by @kjellreigstad in the #themereview 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 and are dedicated to sharing FSE changes that will specifically impact themes. Agendas and summaries are shared on the make/themes blog

Biweekly: 

“What’s New In Gutenberg?” posts. These updates are wrangled by the Core Editor team and focus on what’s been released in each biweekly Gutenberg releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Currently, they tend to mimic a changelog.

Weekly: 

Core Editor chats. These chats are wrangled by volunteer members in the #core-editor Slack channel. Agendas and summaries are shared on the make/core blog. They focus on task coordination and relevant discussions around Gutenberg releases. There is an Open Floor period in each chat where people can suggest topics to discuss.

Weekly Gutenberg Design Updates wrangled by @mapk. These posts capture the big discussions and work being done in the design of Full Site Editing and Gutenberg in general.

Weekly Theme Related Gutenberg Updates (new initiative) wrangled by @kjellr. These posts are focused on themes, including everything from current discussions to recent changes, as well as helpful resources for theme authors. 

Daily:

Checking in on FSE PRs and FSE issues on 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/. This will give you a nearly real-time understanding of what’s being worked on by the developers and designers. 


Each of these are reliable ways of keeping up with the ongoing work on the new Full Site Editing feature coming to WordPress. A big thank you to everyone helping with these various initiatives!

Feedback welcome

What kinds of updates or communication might be missing? What might 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). these current updates and chats easier to follow? Share your ideas and feedback in the comments below! A next step to this work will be refining these communication pathways based on the feedback collected here and elsewhere.

Thank you to @itsjusteileen @andreamiddleton @paaljoachim @mapk for giving me feedback on this post.

#full-site-editing, #gutenberg

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

Editor Chat Agenda: 13 May, 2020

Facilitator: @andraganescu. Notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for 2020-05-13 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/..

  • 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
  • Monthly Plan & Weekly Priorities
  • Task Coordination
  • Open Floor

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

Editor chat Summary: 6 May, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 6th May 2020 held in Slack. Facilitated by @paaljoachim.

Monthly Plan

What’s next 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/? (May)
https://make.wordpress.org/core/2020/05/06/whats-next-in-gutenberg-may/

A summary from @youknowriad
Let’s do aa small recap about the previous months and the next one:
– We did some good progress about the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Patterns on the last month
– FSE Sitesite (versus network, blog) Builder screen is getting closer in terms of parity with the post editor, there’s still some work left
– FSE: we worked on the 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., it was a bit more complex than originally anticipated but we landed something
– Navigation screen continues to improve
– Implemented several Global Styles config per block (colors, line height,…)
The priorities remain mostly the same because most of these are big projects we’re polishing and improving.

Some highlights to come:
– Query Blocks
– More iterations to the patterns (categories)
– Sibling inserter redesign maybe
– Continue on Site Builder and Navigation Screen
– Expand theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. capabilities

Task Coordination

@karmatosed
Different blocks in navigation: 22096
Sub-nav improvements: 22087
Ellipsis and movers: 22089
All my other focus is on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., “needs design” and “design feedback” label has replies.

@nosolosw
I’ve worked on style things at various levels:
– theme.json: convos & reviews about its role to control the editor.
– Global styles: expose style presets (font-size, color, gradients) as CSSCSS Cascading Style Sheets. vars.
– Editor styles: fix for font-sizes.
Also contributed to some misc things such as convos and PR about the 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/. version we support, and provide feedback on switching the JSDoc parser we use for our API docs tool.

@mkaz and @annezazu
Working on a plan to improve block editor docs.

@youknowriad
– Worked a little bit on some follow-ups to the Patterns UIUI User interface (search support)
– Worked on some small refactorings PRs, 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 performance.
– Planning to focus more on the categories support for patterns.

@andraganescu
– I am mostly working on the new nav screen project.
21557 PR in progress of adding a new feature to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data entities delete.
– I constantly try to do more reviews!

@nrqsnchz
– I continue to work on iterations to the Welcome Guide.
– Starting to take a dive into Full Site Editing with Inserting existing saved template parts.
– Started to put together a matrix of pattern categories in a spreadsheet found in other site builders so we can get a better idea of what categories we’d want to have in the inserter.

@pstonier
I’ve been finalizing adding the functionality to 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. the Latest Posts block by author and added the ability to show the author in the list: 16169

@michael-arestad
– Posted a prototype of a page switcher when editing site. (could use some feedback)
– Iteration on template partial creation – (needs dev)
– Proposed persistent block navigator.
Next up:
– Iterate on template partial insertion.
– Explore transforming template partials.
– Could use help with implementation of multi-entity saving.

@mapk
Search block enhancements.
Block mover explorations.
Helping to push scheduled post PR forward with @earnjam.
Providing feedback where I can.

@retrofox
First approach on improving tips. Looked at contextual tips issue.
The idea is being able to register tips defining description, scope, etc.
Related issues
Add rotating block-specific tips to the inserter’s help panel.
Compile a list of possible block-specific tips.
Consider adding adding a rotating Tips area to the block sidebar.
Blocks: Contextual tips tied to specific search queries.

@brentswisher
Hoping to finish adding storybook stories for components this week.
Hoping to review: Storybook: Add DateTimePicker.

@marek
Improving the post scheduling process by showing you what dates you’ve already scheduled for. Needs feedback/reviews.

@zieladam
Working on visual improvements to the navigation block (#22107) and experimenting with making menu items editable in the inspector on the experimental nav menus page (#21948).

@Zeb
Table of Contents block.
Done: Added multipage post support. Ability to toggle if all multipage headings are listed.
Needs: technical reviews/feedback, 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) and copy reviews. A G2 icon.
Heading block H1-H6 level control. Needs: design and technical reviews.
– Custom HTML block polish PR that could use another design review.
– PR: Enable backspace to remove empty Navigation links. Needs help to fix issues and how to handle certain scenarios like removing a Navigation Link with children.
– PR: List block: add color controls. Stuck: Editor style conflicts.
Resolving this PR would open the door to adding color controls to other blocks that use HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. lists (e.g. Latest Posts or Table of Contents).
– PR: PreviewOptions: remove chevron from button. What should the button look like, since it’s text/border styles are inconsistent with the Save Draft button.
– PR: Embed: use same SmugMug URL regex as core. Needs: Review.
– PR: Refactor reusable block edit component using hooks and Refactor ReusableBlockEditPanel to use hooks (and add type info) both need reviews.
– PR: Polish block wrapper elements file. Needs: Review.

Open Floor

Discussing the need to find additional people to review PRs.

@youknowriad
We have 137 on the 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/ team on Gutenberg that can approve PRs. How can we increase the confidence level of these people to actually review and approve PRs?
@earnjam
…Work on more areas = more confident 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). a decision regarding those things.
@aduth
It’s something I was really hopeful CODEOWNERS approach would help with. Where people can specialize in certain areas of the codebase, and it’s fine to focus in those areas. At this point, I think Gutenberg has scaled to such a size that no single person can possibly know how it all works.
@karmatosed
Ideas from experience with triage:
Open sessions for learning how to review PRs. During these go through a few and pick out gotchas and gain confidence through doing.
Mentoring/pairing on PR reviews.

@owoce
Asked for interest in..
Multi-select: add a toolbar with formatting options when multiple blocks are selected. Owoce started some work on this as a 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 (repo) but she is hoping to get something like this into the editor itself.
@youknowriad
Riad shared an example from an older multi select PR that stalled.
@paaljoachim and @youknowriad
Both mentioned that it would be good to create a Github issue when questioner is ready to do so as to continue discussion in an issue.
In the mean time check out her Gutenberg-multi-edit plugin currently at alpha stage.

@brentswisher
Github is having their satellite conference virtually and free this year here: https://githubsatellite.com/schedule/ if someone is looking for learning opportunities.

@kjellr
NB! A heads-up to label issues and PRs that impact theme styling or markup with the label: [Feature] Themes

#core-editor, #core-editor-summary, #gutenberg

Editor Chat Agenda: 6 May, 2020

Facilitator and notetaker: @paaljoachim.

This is the agenda for the weekly editor chat scheduled for 2020-05-06 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/..

  • Monthly Plan & Weekly Priorities
  • Task Coordination
  • Open Floor

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

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

What’s new in Gutenberg (29 April)

In this 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 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, there is a continued effort to refine the experience around the new blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. patterns feature. Additional formatting options for subscript and superscript text have been added, and the code editor has been improved to be more like how one would expect a code editor to look and feel.

Patterns Inserter

To allow a user to browse and insert block patterns, a new tab-panel interface has been added to the Block Inserter. In order to afford additional space for browsing patterns, the top-level inserter has been redesigned to appear as a panel that appears adjacent to the block list when toggled.

Animation inserting a block pattern using the inserter

Inline Formatting

Previously, the availability of formatting options was constrained by the limited space available in a block toolbar. The inclusion of a collapsible dropdown list of formatting options opens the possibility to add a variety of new formatting options for more niche use-cases. This release adds two new formatting options: subscript and superscript.

Animation formatting text of chemical formula using subscript

Code Editor

This release improves the code editor by embracing what it is: a code editor. The Code Editor now uses a monospace font for the title, and the editor resizes to the viewport.

Screenshot of code editor as it appears in Gutenberg 8.0

8.0 🇧🇬

Features

  • Add subscript and superscript formatting options. (21819)
  • Move the Block Patterns UIUI User interface to the inserter. (20951)
  • Improve layout and usability of code editor. (21643)

Enhancements

  • Add inserter previews to more blocks. (21740)
  • Performance improvements:
    • Import from individual reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/.-dates component. (21914)
    • Upgrade showdown Markdown processor library. (21862)
  • Allow title and button-based appender to inherit styles. (21749)
  • Output float clearing for all centered blocks. (21608)
  • Update ‘Welcome Guide’ illustrations. (21515)

New APIs

  • A new Block Context API has been partially implemented, currently limited to block settings and editor APIs. PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 APIs will be implemented 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 releases. (21467, 21868, 21921)
  • Add new “G2”-styled icons to the Icons package. (21209)

Bug Fixes

  • Change wp_make_content_images_responsive to wp_filter_content_tags to resolve warnings in WordPress 5.5-alpha. (21514)
  • Collapse selection to end after link insertion. (17126)
  • Fix selected categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. on existing Latest Posts blocks. (21359)
  • Fix overlapping column contents for embeds. (21570)
  • Fix focus styling for date picker calendar days. (21600)
  • NPM Packages
    • Fix “Cannot find module ‘../utils'” error. (21609)
    • Types: Hide element, primitives, icons declarations. (21613, 21784)
  • Inherit font styles in block appender placeholder. (21725)
  • Allow default pasting behavior in FontSizePicker. (21812)
  • Prevent negative custom text sizes. (21815)
  • Fix image center alignment behavior. (21911)
  • Fix centered buttons margins. (21947)
  • Revert the button block to the previous markup. (21923)
  • Avoid using inline RichText element for navigation link. (21856)
  • Ensure resetEditorBlocks is synchronous. (21839)
  • Fix the button outline style for the old button markup. (21816)
  • Fix default attribute on audio preload. (21735)
  • Fix gradient picker double-click 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.. (21732)
  • Fix broken links in handbook. (21686)
  • 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). useMediaQuery return the correct value on the first render. (21682)
  • Fix visual issue on windows with 782px. (21661)
  • Allow wrapping for Navigation block links. (21632)
  • Remove redundant margins from the columns block. (21615)
  • Fix media Text padding on inner blocks. (21612)
  • Restore floated image margins. (21500)
  • Fix URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org display for scheduled posts. (21410)
  • Test keycode modifiers for keyboard event as exclusive set. (20733)
  • Fix focus loss for Guide “Finish” button in Internet Explorer. (20599)
  • Replace incorrect Snackbar label attribute with aria-label. (20540)

Experiments

  • Add experimental useEditorFeature hook to simplify access to editor features. (21646)
  • 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. page:
    • Try a fixed toolbar in the navigation page. (21340)
    • Fix panel collapsing in navigation page. (21633)
    • Fix mobile layout for navigation menu page. (21638)
    • Delete empty spaces in menu 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 strings. (21453)
  • Edit sitesite (versus network, blog):
    • Add current theme to template switcher. (21578, 21768)
    • Declare attributes for Template Part block in block.json. (21796)
    • Update end-to-end test for multi-entity saving in site editor. (21363)
    • Add preview options component. (21309)
    • Improve template parts resolution and saving behavior. (21766)
    • Support REST API 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. queries. (21851)
    • Add extra validation when loading template parts. (21636)
  • Block directory:
    • Add InserterPanel around block directory results. (21748)
  • Widgets:
    • Fix legacy widgets z-index issue. (21586)
    • Fix legacy widgets visual issues. (21585)

Deprecations

  • Add deprecation notice to useApiFetch hook. (21723)

Code Quality

  • Remove nested breakpoint in fullscreen mode CSSCSS Cascading Style Sheets.. (21496)
  • Update npm-package-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.-lint from 4.0.3 to 5.0.0. (21597)
  • Update npm dependencies that warn. (21596)
  • Fix license check script to ignore sub-dependencies of ignored packages. (21606)
  • Package TypeScript types improvements:
    • Mark addQueryArgs arguments parameter as optional. (21926)
    • Relax i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. sprintf arguments type. (21919)
  • Update PHPCS to latest version. (21680)
  • Unify how editor alignments are applied across blocks. (21822)
  • Remove obsolete editor alignment classes. (21906)
  • Remove old icons. (21821)
  • Implement block.json for blocks. (21794, 21783, 21782, 21775, 21787, 21774, 21792)
  • Use register_block_type_from_metadata in Latest Posts block. (21788)
  • Polish RSS block code. (21773)
  • Move camelCaseDash to the package where it is consumed. (21736)
  • Improve URLPopover code from review comments. (21621)

Documentation

  • Remove duplicate sentence in glossary documentation. (21565)
  • Update wp-env docs to reflect current functionality of package. (21809)
  • Extract Block Transforms into its own handbook page. (21734)
  • Update the index of Block APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to reflect current contents. (21726)
  • Clarify attribute type documentation. (21694)
  • Add location for components style.css. (21654)
  • Fix the JSDoc return type for getEntityRecords. (21630)
  • Update triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. links to new document. (21629)
  • Update Getting Started instructions for remote server. (21625)
  • Update the “patterns” to reflect “user interface” instead. (21562)
  • Create document for contributing with triage. (21350)
  • Update triage.md to add more clarity and relevant links. (21802)

Project Management

  • Update bug report template to help identify the editor version. (21564)

Various

  • End-to-end tests:
    • Add test for template part block creation and insertion. (21849)
    • Add test that template part block customizations are loaded from slug and theme attributes. (21852)
    • Fix tests by removing unnecessary assertions and properly install dependencies in @wordpress/api-fetch. (21780)
    • Add end-to-end test for pinned 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. items. (21652)
    • Add test which verifies reusable block after refresh. (20605)
  • Update cleanForSlug() to remove additional non-word characters. (21007)
  • @wordpress/scripts:
    • Support debugging with test-unit-js. (21631, 21861)
    • Install Chromium on demand together with test-e2e script. (20215)
  • @wordpress/create-block block scaffold tool:
    • Make it easier to provide most popular CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. options. (21751)
    • Split 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/. source files into parts for ESNext template. (21750)
  • @wordpress/env development environment:
    • Expose port 3306 of MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. container. (21545)
  • @wordpress/eslint-plugin:
    • Add the recommended Prettier config to enforce WP coding styles. (21602)
    • Fix no-unused-vars-before-return JSX identifier reference. (21358)
  • Navigation block:
    • Revert changes to data fetching mechanics. (21721)
  • Bundle the block autocompleter in the block-editor package. (21534)
  • Storybook:
    • Add FormToggle component. (18085)
  • Simplify Reusable Block description. (21470)
  • Build tooling:
    • Install Composer dependencies as pre-lint step. (21537)
    • Configure Webpack to watch only build files. (21489)
    • Exit with non-zero status on docgen failed parse. (21690)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36000 words, ~1000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version Loading Time KeyPress event (typing)
Gutenberg 8.0 9.8s 31.4ms
Gutenberg 7.9 12.0s 36.0ms
WordPress 5.4 9.2s 29.4ms

#core-editor, #editor, #gutenberg, #gutenberg-new