Ajit Bohra 7:50 pm on December 11, 2019
Tags: core-editor, editor ( 128 ), gutenberg ( 130 ), meeting notes ( 61 )

Editor chat summary: Wednesday, 11 December 2019

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, December 11, 2019, 14:00 UTC.

Gutenberg 7.1.0

Gutenberg 7.1.0 is released.
Massive progress on full site editing experience.
Some of the feature highlights:
- New welcome UI in place of tips.
- Table captions and UI to toggle between edit and select mode.
- New fixed toolbar for mobile.
- Improved multi-block selection experience.
This is a big release with 161 pull requests merged, for details checkout release post.

Weekly Priorities

Full site editing / block content areas
Block patterns API
Improvements to the Block UI
Tightening up items

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

Trying to unblock folks/PR as much possible
Reviewed dozen of PR’s’
Working on the Button components https://github.com/WordPress/gutenberg/pull/19058 (consistency)
Working on Block Toolbar/Block UI PR’s
Continue Reviewing PR’s

@karmatosed

Working on tightening up board, reviews and also PR’s.
Get sentence case unblocked https://github.com/WordPress/gutenberg/pull/18758.
Lot of design work including navigation iterations.
Triaging.

@mkaz

Revisiting Social Links to get it moving forward
- Design Issue: https://github.com/WordPress/gutenberg/issues/19020
- Extensibility/SVG Issue: https://github.com/WordPress/gutenberg/issues/19041

@aduth

Focusing around performance, bug fixes, build test stability
Refreshed PR to move speak behavior to the Notice/Snackbar components https://github.com/WordPress/gutenberg/pull/15745
Removing the block inserter shortcuts https://github.com/WordPress/gutenberg/pull/1904

@gziolo

Refactoring to the block toolbar, including some visual tweaks
Iterations to Build Tools: Integrate DependencyExtractionWebpackPlugin in the JS build https://core.trac.wordpress.org/ticket/48154
Reviews, including some learnings about TypeScript, JSDoc, etc.
Ported wp-cli scaffold block to npm init wordpress-block – this generates ES5 JS code, I plan to provide ESNext +JSX template as an option next week

Open Floor

@gwwar asked what’s the planned schedule for the plugin release in the upcoming holidays season. Some discussion about delaying it with no decicion. Kindly share your thoughts in comments
@wpfangirl mentioned about PDF thumbnail preview there was some discussion but no decisions share your thoughts on the issue https://github.com/WordPress/gutenberg/issues/15097
@paaljoachim mentioned about having a way to align instances of a reusable block in various layouts https://github.com/WordPress/gutenberg/issues/17640#issuecomment-556866662
@aduth metioned the following pull request https://github.com/WordPress/gutenberg/pull/14715 as it works on bringing consistency to how the reusable blocks behave with the rest of the editor.

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

Jorge Costa 3:29 pm on December 11, 2019
Tags: core-editor, editor ( 128 ), gutenberg ( 130 )

What’s new in Gutenberg? (11 December)

Gutenberg 7.1 is a big release with 161 pull requests merged. Thank you to all the contributors of this release!

The release contains many refactors to the code base to make future changes possible, e.g., refactors to functional components so it is possible to use new hooks that are available.

This release tries to make block development using standard features like color picking UI easier. To do that the release expands the useColors hook to have new functionalities like color contrast checking and default color detection.

There was huge progress on the full site editing work, with the merge of the template part block. Documentation efforts for the FSE (full site editing) work are now in progress.

Gutenberg 7.1 brings a new welcome UI for new users:

This release also Introduces table captions and implements a UI mechanism to toggle between edit and select modes:

The last two enhancements to note are the new fixed-mobile toolbar and the improved multi-block selection experience:

7.1 🇲🇽

Features

Adding a menu to visually switch between edit and navigation modes and announce the mode changes to screen reader users.
Support adding a caption to the Table block.
Implement a Welcome Guide modal.

Enhancements

Use a Fixed Block Toolbar on Mobile Web.
Block UI:
- Remove the parent block from the block title component.
- Remove dashed outlines for child and parent blocks.
- Remove hover styles.
Navigation block:
- Keep a single place to trigger the “Open in a new tab” option.
- Fix overflow by allowing wrapping of menu items.
- Fix double click to open the appender.
- Add a type=submit to the search suggestion buttons.
- Support justifying the menu items.
- Use correct classnames for navigation link block save output.
- Remove the inspector controls.
Improve the block multi-selection:
- A11y: Use the browser’s selection default color.
- Polish the styles.
- Responsive multi-selection.
- Allow pasting on multi-selection.
Improve the Image blocks replacement flow/UI.
Disable the HTML mode in the Cover block.
Add friendly offline error messages on Rest API request failures.
Round the focal point coordinates.
Popover & Dropdowns: Consistently and smoothly adjust the position on scroll.
Remove clearing the block selection on sidebar tab switch.
Separate editor notices by border instead of margin.
Allow drag and dropping images into the featured image box.

Bug Fixes

Prevent resized Image blocks from overlapping the boundaries of the block.
Fix wrong link to attachment page after replacing images.
Fix Media & Text block: “Crop image to fill entire column” reset on image change.
Fix the Snackbar notices position.
Save the Verse block line breaks as single characters.
Remove has-background-dim-NaN classname from the Cover block.
Normalize the keys of the apiFetch preloaded data to avoid unnecessary Rest API calls.
Fix CSS styles of the ColorPicker component.
Update the Inspector slots to use the bubblesVirtually slots Fixing RichText usage in Inspector controls.
Move the Modals and Popovers to the right position in the DOM.
Fix alignment of date picker days when used in block.
Fix alignment of ToggleControl label.
Fix the toggled state in the block toolbar buttons.
Fix the multi-select inspector padding.
Fix the behavior that allows writing by clicking anywhere in the canvas.
Prevent private posts with a future date from becoming public on update.
Fix useColors crashes if contrast checkers are not specified.
Render metaboxes as a single seemless unit to fix styling issues for themes with colored backgrounds.
Fix the FontSizePicker custom option.
Fix reusable blocks showing up as too tall.
Fix Drop Cap + alignment producing a gap between paragraphs.
Fix Cover to Image block transform when no image is used in the Cover block.
Ensure empty classname is not output onto table element.
Fix scrolling the sidebar on mobile.
I18: Fix the Code block example string.

APIs

Support a disabled prop in the RichText component.
Add a new CustomSelectControl component.
Add a new TextHighlight component.
Add a new CustomGradientPicker component.
Add useViewportMatch React hook to the wordpress/compose package.
Allowing changing the aXe config in the wordpress/just-puppeteer-axe package.

Experiments

Block Content Areas:
- Add a demo templates directory.
- Add the Template Part block.
- Add documentation for the current state of the experiment.
Widgets screen:
- Clear the block selection when clicking outside the widget areas.
APIs:
- Add a new __experimentalResolveSelect API to the data package.
- Add color detection and contrast checks support to the useColors hook.

Documentation

Improvements to the Getting Started documentation.
Include TypeScript type checking in Testing Overview.
Add JSDoc recommendations.
Reintroduce NodeJS LTS support commitment.
Typos and tweaks: 1, 2, 3, 4, 5, 6.

Performance

Avoid rerendering the EditorRegions component on each click.
Flatten and simplify the align hook rendering.
Shim the meta attribute source on block registration.

Various

Storybook: Add StoryShots integration to generate unit tests.
Work on the stability of e2e tests: 1, 2, 3, 4, 5.
Use consistent theme colors and font sizes in e2e tests.
Travis: Skip the deploy stage on PRs.
And a Travis job to check the IE11 compatibility of the produced JavaScript builds.
Avoid usage of editor store on block editor reusable blocks inserter.
Replace the fs-extra dependency with rimraf.
RSS block: Remove PHP 5.2 compatibility code.
Update the Columns block to use the Patterns API.
Refactor the BlockToolbar component to use React hooks.
Refactor the BlockDraggable component for a simpler React tree.
Refactor the BlockHTML component to use React hooks.
Refactor the BlockList component to use React hooks.
Refactor the BlockInsertionPoint component to use React hooks.
Split @wordpress/urls into multiple modules/files to allow better tree-shaking.
Improve the Storybook setup to allow updates on style changes.
Enforce consistent usage of Button and ToolbarGroup components.
Use the colors hook in the Paragraph block.
Add missing actions and tests for lockPostAutosaving, unlockPostAutosaving.
Collapse passed tests in Travis jobs.
Add side effects property to the @wordpress/components package to allow tree-shaking.
Add a script to perform patch releases for old npm package versions.
Reuse the URLInput component in the Social Links block and disable suggestions.
Improve and simplify reusable block styles.
Refactor the Gallery edit component to be semi-cross-platform.
Run tests using the same environment version used for development.
Add CPU/Network slowdown configuration options to the e2e tests setup.
Enable Type checking for the @wordpress/token-list package.
Move the changelog.txt and readme.txt files to the Github repository.

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 7.1.0	7.45s	88.56ms
Gutenberg 7.0.0	6.84s	94ms
WordPress 5.3	6.33s	75.19ms

#core-editor, #editor, #gutenberg

Riad Benguella 1:36 pm on December 3, 2019
Tags: core-editor

What’s next in Gutenberg? (December)

This is a monthly update containing the high-level items that Gutenberg contributors are focusing on for the next month. Join us in our efforts.

Block Content Areas

The previous weeks saw a lot of iterations towards building the block content areas APIs and the full site editing experience (Post content, Post title, Site title blocks landed, an early demo is now included in the plugin). In the next weeks, contributors will be working on expanding on this work:

Work on a UI to save multiple entities (post, site, template…) from the same interface. 18029.
Nested template areas. (Template parts). 18736.
Support for a view-only mode for non-admins. 18760, 18772.
Start working on a Full-site editing view/mode.
Start working on documentation and calls for testing.

Block Patterns

Block patterns are a way to provide a predefined set of blocks you can select for a given container block (Columns, Group, Media & Text) or without any container block as a way to insert a pre-made design into the editor. Some parts of the initial API are already available. In the next weeks, we’ll focus on implementing block patterns for several blocks and exploring UI to insert these patterns. 17335, 16283.

Tightening up

Existing interactions and blocks will be iterated on:

Polishing the Navigation block and addressing early feedback Projects/31.
Custom gradient picker 17603.
Improvements to the Media Flows. 16200.
Iterations on the block interface and the block toolbar 18667, 18686.
Toolbar Accessibility improvements 18619.

While these are our focuses don’t forget you can always help with triage, ‘needs testing’ and reviewing PRs

#core-editor

Jorge Costa 1:01 pm on November 28, 2019
Tags: core-editor, editor-chat ( 20 ), meeting ( 34 ), summary ( 279 )

Editor chat summary: Wednesday, 27 November 2019

This post summarizes the weekly editor chat meeting on Wednesday, 27 November 2019, 14:00 WET held in Slack.

Gutenberg 7.0

Gutenberg 7.0 was released. It brings the navigation block out of the experimental state. The release was possible thanks to the efforts of 51 contributors. More details about this release can be checked on the release post.

Weekly Priorities

November priorities post: https://make.wordpress.org/core/2019/10/29/whats-next-in-gutenberg-november/

The priorities should remain pretty stable I think: Block Content Areas, Nesting Selection Tool, Navigation block will continue to be improved based on feedback. Gradients are almost “finished” and we may start thinking about improvements to the block interface based on this great issue https://github.com/WordPress/gutenberg/issues/18667.
@youknowriad

Task Coordination

@youknowriad

Worked on PR’s Edit/Navigation Tool, Fixed Toolbar on mobile, and Add a header menu to switch between edit and select tool. Hopes to continue a trend of 50% reviews and triage and 50% code.

@jorgefilipecosta

Gave support on the forums, triaged issues, rebased and updated some PR’s, submitted and merged several bug fixes, and worked on a PR that may increase the performance of the editor by caching styles https://github.com/WordPress/gutenberg/pull/18763.

On the next week:

Plans to review and help some media-related PR’s, namely the refactor to the gallery, to increase reusability with the native mobile APP.
Wants to finish the remove editor module usages in block-editor by applying changes to the reusable blocks and rich-text.
Update the release tool to move readme and changelog files to the Github repository.

@noisysocks

Finished the work on adding a welcome guide modal, which is now ready for review.

Intends to spend the rest of this week playing with wordpress/env, seeing if we can deprecate local-env, and writing docs for this all.

@retrofox

Helped to finish the first approach of the Navigation block. Emphasize this comment: Navigation block will continue to be improved based on feedback.

@karmatosed

Contributed to the following tasks:

PR for Sentence case: https://github.com/WordPress/gutenberg/pull/18757.
Proposed an experimental PR to make everything sentence case https://github.com/WordPress/gutenberg/pull/18758.
Navigation PR for styles is now merged: https://github.com/WordPress/gutenberg/pull/18553.

Is looking at iterations for navigation, going through design feedback in Tightening Up board, and seeing what needs work or is blocked, and is working on docs for the triage team.

@mapk

Worked on some reviews and triage, namely the NUX modal PR for @noisysocks.

@paaljoachim

Looked closer at this issue https://github.com/WordPress/gutenberg/issues/17640#issuecomment-556866662. Might need to create a new issue to bring a better focus on what he brought up.

@gziolo

Attended WordCamp Łódź, helped people on forums, worked on some triage based on reports from people. This week will resume the work on Block Patterns API.

@bph

Working on End User Documentation and connected with @melchoyce on her project to replacing gifs with videos.

Open floor

@scruffian brought the topic of how we handle Full Site Editing blocks for non-admin users.

@youknowriad referred the precedent we have in media blocks to allow/disallow features based on user capabilities, and @noisysocks referred the API we have to query user permissions.

@scruffian shared some questions he had on his mind:

Is the API change I suggested in https://github.com/WordPress/wordpress-develop/pull/120 sensible?
I see a change in the block itself in the PR not the API and it seems reasonable.
How does the design of the block change when a non-admin see it – does it need a special treatment?
This is probably a per-block problem as you might have access to some features in the block but not everything (think alignment of a site title block)

For the API change question, @youknowriad answered, he sees a change in the block itself in the PR, not the API, and that the change seems reasonable. For the block design question, @youknowriad answered that this is probably a per-block problem as one might have access to some features in the block but not everything.

@mrMark asked the use case Navigation Block and if it is intended to replace the menu system eventually. @youknowriad said that replacing the menu system may be a possibility but not until we allow editing the full templates in Gutenberg.

As a follow-up question @mrMark asked:

As the Block Editor encroaches onto the realm of what themes would normally handle, ie presentation layer, what’s the plan for integration between the Block editor and themes?

And then @mrMark referred that the Next Generation of Themes and how they integrate with the Block Editor should start being conceptualized.

@youknowriad referred that this is a big topic and ongoing work that can be followed on https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing. @youknowriad is also happy to answer any specific questions, and this topic will be part of the next week’s meeting. So in case, this is something that interests you, please join us and share your insights!

#core-editor, #editor-chat, #meeting, #summary

Riad Benguella 1:31 pm on November 27, 2019
Tags: core-editor, editor ( 128 ), gutenberg ( 130 )

What’s new in Gutenberg? (27 November)

More than 51 contributors helped shape the 7.0.0 Gutenberg release. It’s one of the biggest number of contributors we’ve ever had.

The release includes a big number of fixes and enhancements to the Navigation block and marks it as a stable feature.

In terms of APIs, developers will be happy to know that this PR introduced some new APIs like allowing the internationalization of strings containing safe HTML, a new Card component in wordpress/components and a few other enhancements we encourage you to try and provide feedback.

7.0

Features

Add a new Navigation block (early version)
- Highlight menu items without defined URL.
- Prevent error in Firefox when removing the block.
- Remove background color from the Navigation block and rely on the Group block.
- Remove the background shadow for the submenus dropdown.
- Rename “Navigation Menu Item” block to “Link”.
- Remove unnecessary color attributes.
- Allow addition CSS classes.
- Drop the “menu” suffix from the block name.
- Escape special characters in the frontend.
- Remove from experimental features.
- Add style variations.

Enhancements

Use gradient classnames instead of inline styles for the Cover block.
Inserter: Add keyboard shortcut styling to “/” in the default tip.
Restore the caret position properly on undo.
Add keywords to improve the discoverability of the Audio block.
Show video preview on Cover block inspector panel.

Bug Fixes

Fix hidden nested images in the content column.
Fix double border issue in the keyboard shortcuts modal.
Fix off-centered publish button.
Fix error when isRTL config is not provided in the block editor settings.
Fix full width Table block mobile regression.
A11y: Add a screen reader text label for the Search block.
Fix text patterns undo after mouse move.
Fix block drag and drop for the contributor role.
Update the link when switching the image used in the Image block.
Fix php error triggered when gutenberg_register_packages_scripts is run more than once.
Fix special characters escaping for the post title.
Fix JavaScript errors triggered when selectors are called before the editor being initialized.
Fix BaseControl component label when no id is passed.
Preserve whitespace when converting blocks Preformatted and Paragraph blocks.
Fix multiple paste issues creating unnecessary empty spaces.

New APIs

Add a new Card component to wordpress/components.
Add label support for the URLInput component.
Support the isMatch option for the shorcode transforms.

Experiments

Block Content areas:
- Add Post Title and Post Content blocks.
- Add template parts CPT and the theme resolution logic.
Widgets Screen:
- Refactor the legacy widgets block to support all blocks.
- Fix widget areas margins.
- Add isRTL setting.
APIs
- useColors hook: Enhance the contrast checking API and provide access to the color value.
- Introduce createInterpolateElement to allow translation of complex strings with HTML content.
- A11y: Refactor the accessibility behavior of the Toolbar component.
Social Links:
- Capitalize LinkedIn and GitHub properly.
- Fix frontend styling.

Documentation

Add a Backward Compatibility policy document.
Clarify the npm packages release documentation.
Add documentation for the @wordpress/env wp-env.json config file.
Typos and tweaks: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20.

Various

Refactor the RichText component: Remove the inner Editable component.
Integrate the Gutenberg Playground into Storybook.
Increase WordPress minimum supported by the plugin to 5.2.0.
Refactor the Paragraph block edit function as a functional component.
Refactor the Cover block edit function as a functional component.
Add new components to Storybook.
- RadioControl component.
- TabPanel component.
- Popover component.
- BaseControl component.
- Tip component.
Include WordPress eslint plugin in React eslint ruleset in wordpress/eslint-plugin.
Block PRs on mobile unit test failures in Travis.
Polish the PostSchedule popover styling.
Fix the API documentation generation tool when spaces are used in folder names.
Add missing @babel/runtime dependency to the wordpress/jest-puppeteer-axe.
Refactor the Layout component to separate the UI from the content.
Align Dropdown and DropdownMenu components styling.
Remove max-width style from the Image block.
Remove the CollegeHumor embed block.
Add unit tests:
- Ensure consecutive edits to the same attribute are considered persistent.
- Test the core-data undo reducer.

Performance Benchmark

Version	Loading Time	KeyPress event (typing)
Gutenberg 7.0.0	5.1s	67.7ms
Gutenberg 6.9.0	6.6s	53.5ms
WordPress 5.3	6.3s	61.44ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Andrés 8:02 am on November 21, 2019
Tags: core-editor, editor-chat ( 20 ), summary ( 279 )

Core Editor Summary for November 20

This post summarises the weekly editor chat meeting (agenda), held on Wednesday, November 20, 2019, 14:00 UTC in core-editor Slack channel.

Moderator: @jorgefilipecosta
Notetaker: @nosolosw

Weekly Priorities

Slack transcript.

See November Priorities post. Good to focus on these things as the month wraps to an end and start thinking on next steps.

Block Content Areas: expected to still be a focus for a while.
Navigation block (board): is close to get out of the experimental phase into the plugin.
Tightening up (board):
- Polish to blocks and different parts of the UI is continuing.
- Gradients are coming along nicely.
- Some progress is being made to the Block Selection Tools.
- Add color to specific text inside RichText (16014) is blocked by 17617 It’d be good to unblock those.

Triage role for GitHub

Slack Transcript.

GitHub has recently created a few new roles with more fine-grained permissions. One of those is the Triage Role that enables people to manage issues and pull request, and well as other actions. There was a consensus that this new role could help onboard new contributors and less technical folks who are not part of the Gutenberg group already.

Tasks:

@youknowriad to create the GitHub team
@karmatosed and @nerrad to collaborate on documenting what it means triagging, how one can do it, and how the group can organize to do triage sessions. Master issue.

If you’re interested in joining the Triage group, please, leave a comment in the agenda or the GitHub issue.

Task Coordination

Slack Transcript.

More people reviewing open PRs and triagging issues. It’s never too late to help! @mapk @youknowriad @karmatosed @jorgefilipecosta @andraganescu @noisysocks
Media:
- A Media Flow Component that can be reused by blocks. Needs review @andraganescu
- Link images in media + text. Needs review. @andraganescu
Navigation block:
Misc:
- A fix to focus on clicking the inserter and the movers. Needs review. @andraganescu
- Remove clearing the block selection on sidebar tab switch @andraganescu
- Welcome guide modal. In progress. @noisysocks
- Landed a refactor to the Layout component @youknowriad
- Add a header menu to switch between edit and select tool @youknowriad
- Open a PR about aligning the styles of our Dropdown components @youknowriad
- Keep an eye on WP 5.3 regressions. So far, @youknowriad reported (and fixed):
  - One JS error that can be triggered by some plugins (fix in the work)
  - Scrolling issue in Microsoft Edge
- Dove into a bit of full-site editing page switching concepts. @mapk
- Support on WordPress.org forums @jorgefilipecosta

If you’re reading this asynchronously, please, add your notes as comments.

Open Floor

Slack Transcript.

Welcome feedback on this exploration of hover/selection states for Full Site Editing concepts by @shaunandrews

Request For Comments experiment. A few months ago Gutenberg started doing a RFC for major features following this post. @youknowriad noted that it didn’t get as much traction as expected. Many agreed. To close this experiment and the open RFCs is being considered.

If you have any feedback about the RFC experiment, please, comment on this post or reach out to people involved. Feedback channels will be opened until next week when a decission will be made.

#core-editor, #editor-chat, #summary

Ella van Durpe 8:41 pm on November 13, 2019
Tags: core-editor, editor ( 128 ), gutenberg ( 130 )

What’s new in Gutenberg? (13 November)

In this newest release of Gutenberg, block content areas and the navigation block continue to be iterated upon. An experimental block pattern API has been added, and themes can now define custom gradient presets!

The navigation block, demonstrating newly improved horizontal block movers.

The block editor provides default gradient presets. Now, a theme can overwrite them and provide its own:

add_theme_support(
    '__experimental-editor-gradient-presets',
    array(
        array(
            'name'     => __( 'Vivid cyan blue to vivid purple', 'themeLangDomain' ),
            'gradient' => 'linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%)',
            'slug'     => 'vivid-cyan-blue-to-vivid-purple'
        ),
    )
);

Note that this feature is currently experimental and subject to change.

6.9 🇦🇷

Features

Support changing the image title attribute in the Image block.

Bugs

Fix invalid Pullquote blocks when setting a color from the palette presets.
Fix the columns left/right full-width margins.
Prevent fast consecutive updates from triggering blocks reset.
Fix block movers for floated blocks.
Fix Radio buttons styling in meta boxes.
Fix the default image sizes used for featured images displayed in the editor.
Prevent the unsaved changes warning from popping-up when deleting posts.
Revert img and iframe styles to block editor container scope.
Block Merge: guard for undefined attribute definition.

Enhancements

Inserter: Immediately insert block when only one block type is allowed.
Update the list of the default available gradients.
Disable indent/outdent buttons when necessary in the List block.

New APIs

Add theme support API to define custom gradients presets.
Mark the AsyncMode data module API as stable.
Mark the mediaUpload @wordpress/block-editor setting as stable.
Add a wpenv.json config file support for @wordpress/env.

Various

Refactor the way HTML is escaped by the RichText component.
Refactor and simplify the block margins CSS in the editor.
Use HTTPS git clone in the Gutenberg release tool for more stability.
Update ExternalLink, BaseControl and FormTokenField components to use the VisuallyHidden component for the screen reader text.
Add several components to Storybook:
- Spinner,
- Draggable,
- RangeControl,
- FontSizePicker,
- Modal,
- Snackbar,
- ToggleControl,
- ResizableBox.
Refactor the block-directory search to insert as an Inserter plugin.
Improve the experimental useColors React hook.
Upgrade Puppeteer to the last version.
Update to the last version of npm-package-json-lint.
i18n: Fix string concatenation in the Verse block example and add translators string.
Change Detection: Add an e2e test case for post trashing.
Fix the e2e tests watch command.

Experimental

Block Content Areas:
- Support loading block templates from themes.
Navigation block:
- Add default frontend styles for the Navigation block.
- Use RichText for navigation menu item instead of TextControl.
- Add block navigator to the inspector panel.
- Use an SVG icon for the color selector.
- Add a new API for horizontal movers and use it for the navigation block.
- Add a new Link creation and edition UI and use it for the navigation block.
- Add an appender to the block navigator.
- Add a block placeholder.
- Various fixes and refactorings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15.
Add ResponsiveBlockControl component.
Add initial API for block patterns.

Documentation

Add an introduction README for Storybook.
Typos and fixes: 1, 2, 3, 4, 5, 6.

Performance Benchmark

Version	Loading Time	KeyPress event (typing)
Gutenberg 6.9.0	11s	77.36ms
Gutenberg 6.8.0	11s	74.78ms
WordPress 5.3	10.6s	80.85ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

andraganescu 3:03 pm on November 13, 2019
Tags: core-editor, editor-chat ( 20 )

Core editor chat summary November 13th, 2019

This post summarises the weekly editor chat meeting, agenda here, held on Wednesday, November 13th 2019, 13:00UTC in Slack, moderated by @jorgefilipecosta, notetaker: @andraganescu

Next week’s Core editor chat time: 14 UTC

Because of DST there was a decision to move the meeting one hour later. The async discussion is still open until Monday, November 18th to decide if people, other than those present at he core editor chat want it differently.

WordPress 5.3 was released yesterday

@youknowriad: Big kudos to all the contributors. It’s a huge release for the block editor

@jorgefilipecosta I would like to thank all the people that contributed and made all this improvements and bug fixes possible!!

There is some current effort to iron out issues that may appear.

Gutenberg 6.9 will be released today

A Release Candidate is already available at https://github.com/WordPress/gutenberg/releases/tag/v6.9.0-rc.1

@aduth and @ella are working on that (release post and performing the release)

Weekly priorities

The main priorities are the same ones highlighted in the November post What’s next in Gutenberg? (November) – Make WordPress Core

Also, one of the priorities is to fix WordPress 5.3 regressions as they come up.

Task coordination

@youknowriad

I was AFK for some days post WCUS
I worked on the WordPress 5.3 release a little bit
I’ll be focusing on support, triage and reviews for the next week.

@karmatosed

Navigation block: styling, reviews and testing
Triage: I want to dig in a bit and try and clear down low hanging tasks
Begin working out sprints for Tightening Up board. I have an idea to for 1-2 weeks focus on an area, move on and repeat.
Support is for me next week so last point won’t happen until week after.

@retrofox

Navigation Block. Wrangling blocking issues. Reviewing / Testing / Tackling issues
Dashboard project: https://github.com/WordPress/gutenberg/projects/31

@getdave

I’ve been focused mainly on Nav Block related PRs.
In particular, I’d draw attention to this one I created to allow parent Blocks to “consume” the toolbar of their children via InnerBlocks https://github.com/WordPress/gutenberg/pull/18440

@pbrocks

I connected with the Meta team about creating a Slack channel for Notetakers, which hasn’t happened yet and also correcting the spelling mistake on the plugin page. https://wordpress.slack.com/archives/C02QB8GMM/p1573591282156800

@michaelarestad

starting in on full site editing – largely research/information gathering at this point

@mapk

Helped review some of the Nav block work.
Worked on the Media replace flow.
Reviewed linking media in Media+Text block.
Helped @michaelarestad with some full site editing research.

@andraganescu

continued on the navigation block
need a code review on the media replace control here: https://github.com/WordPress/gutenberg/pull/16200

@nerrad

I continued working on createInterpolateComponent (thanks @aduth for additional reviews 🙂 ) https://github.com/WordPress/gutenberg/pull/17376

@jorgefilipecosta

I finished a big refactor for the legacy widgets, made some improvements on the custom gradient picker, worked on some PR reviews, continue the work around having configurable inner block settings to allow a parent block to absorve the child, and continued the iterations on some PR’s I had open.
For the next week, I’m hoping to merge the simulated media queries mechanism; I want to get involved again in the navigation block work, so I hope to do many reviews there and maybe pick up some tasks, besides that I will continue the buttons block and innerblocks UI work.

@tellthemachines

For task coordination: I’ve mostly been reviewing nav-related PRs this week and will be away from the 14th to the 24th November. (In case anyone wonders why I’ve gone strangely silent :D)

@noisysocks

I’m still looking at nav-related PRs and working on the Welcome Guide as time permits.

@gziolo

landed experimental API for Block Patterns ( https://github.com/WordPress/gutenberg/pull/18270 )
explored Patterns API integration with Columns and Media & Text blocks
landed the playground integration with Storybook (check at https://wordpress.github.io/gutenberg/ )
reviewed and tested two huge PRs: accessible toolbar ( https://github.com/WordPress/gutenberg/pull/17875 – nearly ready to land);
card components with CSS in JS integration ( https://github.com/WordPress/gutenberg/pull/17963 – ready to land)

@youknowriad highlighted the new Storybook available at: https://wordpress.github.io/gutenberg/

It is also important to note for people reading this async: it is possible to participate on the task coordination by commenting on the agenda.

Open floor

let’s make the native mobile JS unit tests mandatory to pass on Travis, and provide instructions on how to debug if they fail: https://github.com/WordPress/gutenberg/pull/18454

Popover issue can finally be tackled now that WordPress 5.3 is out: https://github.com/WordPress/gutenberg/pull/17617#pullrequestreview-294282089

Embedding Multilingual ability as standard core functionality: seems a bit early for implementation but it’s definitely being considered.

Let’s review more PRs!

Just a note to everyone. Do please also spend a little time going through older PR’s. As there are many just hanging waiting for a comment, a review etc. We’re definitely falling behind in terms of reviews.

The number of open PR’s increasing which in part is a good signal it means the project is getting more interest, but we should try to review these PR’s as soon as possible so new contributors keep the interest in contributing and we get the features/fixes sooner.

#core-editor, #editor-chat

Riad Benguella 4:37 pm on October 30, 2019
Tags: core-editor, editor ( 128 ), gutenberg ( 130 )

What’s new in Gutenberg? (30 October)

Work on block content areas and the navigation menu block is accelerating in this release.

In the meantime, this release continues the work on Gradients support and expand it to the Cover block while relying on classnames instead of inline styles

Block Nested selection and interactions is still being improved with a new Block Breadcrumb Bar allowing to quickly navigate the block hierarchy of . the current selection.

Capture d’écran 2019-10-16 à 11 34 50 AM

6.8

Features

Support gradients in Cover block.
Add a breadcrumb bar to support block hierarchy selection.

Enhancements

Cover block: change the minimum height input step size to one.
Allow setting a display name for blocks based on their content in the BlockNavigator.
Hide the gradients panel if an empty gradients set is explicitly defined.
Do not transform list items into paragraphs when deleting first list item and list is not empty.
Replace inline styles with classnames for the gradient palette.
Preserve list attributes (start, type and reversed) when pasting or converting HTML to blocks.

Bugs

Clear local autosaves after successful saves.
Fix the columns block width overflow issue when using more than two columns.
Fix the Link Rel input not showing the saved value of the link rel attribute.
Fix JavaScript errors triggered when using links without href in HTML mode.
Move the default list styles to the theme editor styles.
Fix Invalid import statement for deprecated call in the Modal component.
Fix a small visual glitch in the Publish button.
Prevent blank page when using the Media Modal Edit Image “back” button.
Allow the shortcode transform to apply to all the provided shortcode aliases.
Fix JavaScript error triggered when using arrows on an empty URLInput.
Fix extra margins added to Gallery blocks by list editor styles.
Fix custom button background color not reflected on reload.
Preserve List block attributes when splitting into multiple lists.
Fix checkbox styles when used in metaboxes.
Make the FontSizePicker style independent from WordPress core styles.
Fix overlapping controls in the Inline Image formatting toolbar.
Fix strikethrough formatting when copy/pasting from Google Docs in Safari.
Allow media upload post processing for all 5xx REST API responses.

Experiments

Navigation block:
- Support color customization.
- Improve the Link edition UI.
Block Content Areas:
- Implement a frontend template loader based on the wp_template CPT.
- Add a temporary UI to edit wp_template CPT posts.
- Add a Site title block.

New APIs

Add VisuallyHidden component.
Add @wordpress/base-styles package to share the common variables/mixins used by the WordPress packages.
Add Platform component to allow writing platform (web, mobile) specific logic.
Add isInvalidDate prop to DatePicker.
wordpress/env improvements:
- Support custom ports.
- Support using it for themes.
Add a new experimental React hook to support colors in blocks.
Add a new experimental DimentionControl component.

Various

Storybook:
- Add a story for the CheckboxControl component.
- Add a story for the Dashicon component.
- Add a story for the ColorPalette component.
- Add a story for the ColorPicker component.
- Add a story for the ExternalLink component.

Add knobs to the ColorIndicator Story.

Several other enhancements to existing stories.
Linting fixes for Storybook config.
Fix Lint warnings triggered by JSDoc definitions.
Reorganize e2e tests specs into three folders: editor, experimental and plugin.
Cleanup skipped e2e tests.
Add a link to Storybook from the Gutenberg playground.
Optimize the wordpress/compose package to support tree-shaking.
Code Quality:
- Refactor the Button block edit function to use a functional component.
- Change the name of the accumulated variables in reduce functions.
- Remove wrapper around the Table block cells.
Fix several issues related to Node 12 becoming LTS.
Add the Block Inspector to the Gutenberg playground.

Documentation

Enhance the Git workflow documentation.
Clarify block naming conventions.
Tweaks and typos: 1, 2.

Performance Benchmark

Version	Loading Time	KeyPress event (typing)
Gutenberg 6.8.0	5.68s	47.28ms
Gutenberg 6.7.0	5.83s	47.92ms
WordPress 5.2	6.1s	63.22ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Riad Benguella 1:01 pm on October 29, 2019
Tags: core-editor

What’s next in Gutenberg? (November)

This is a monthly update containing the high-level items, Gutenberg contributors are and should focus on for the next month.

Block Content Areas

In previous Gutenberg releases, a new wp_template Custom Post Type has been created to store block content areas and enable using Gutenberg outside the post content. In the next weeks, contributors will be working on expanding on this work:

Render the frontend template loader to support wp_templates 17626.
Add a temporary UI to edit these templates 17625.
Experiment with blocks targeting site options (title) 17207.
Work on a UI to save multiple entities (post, site, template…) from the same interface. 18029.
Nested template areas.

Menu Navigation Block

The Menu Navigation is also one of an important focus for this month. You . can follow all the related work on this project and the overview issue.

Tightening up

Existing interactions and blocks will be iterated on:

Gradients support across blocks 18001.
Theme API for gradients. 17841, 18008, 18028.
Improvements to the Media Flows. 16200.
Improve nested block navigation through a block hierarchy breadcrumb and explore selection tools. 17838 17088.

#core-editor

Welcome!

Communication

Gutenberg 7.1.0

Weekly Priorities

Task Coordination

Open Floor

7.1 🇲🇽

Features

Enhancements

Bug Fixes

APIs

Experiments

Documentation

Performance

Various

Performance Benchmark

Block Content Areas

Block Patterns

Tightening up

Gutenberg 7.0

Weekly Priorities

Task Coordination

Open floor

7.0 🇷🇴

Features

Enhancements

Bug Fixes

New APIs

Experiments

Documentation

Various

Performance Benchmark

Weekly Priorities

Triage role for GitHub

Task Coordination

Open Floor

6.9 🇦🇷

Features

Bugs

Enhancements

New APIs

Various

Experimental

Documentation

Performance Benchmark

Next week’s Core editor chat time: 14 UTC

WordPress 5.3 was released yesterday

Gutenberg 6.9 will be released today

Weekly priorities

Task coordination

Open floor

Let’s review more PRs!

6.8 🇮🇳

Features

Enhancements

Bugs

Experiments

New APIs

Various

Documentation

Performance Benchmark

Block Content Areas

Menu Navigation Block

Tightening up

7.0

6.8