Riad Benguella 10:53 am on February 6, 2019
Tags: core-editor, editor ( 96 ), gutenberg ( 89 )

What’s New in Gutenberg? (6th February)

@mapk said earlier that the Gutenberg repository is on fire 🔥, he was not lying. More than 52 contributors participated in this release.

This release is also the first release dropping support for WordPress versions prior to 5.0.

As part of the widgets 2 blocks project, this release introduces the RSS block.

The amazon kindle embed provider has been added recently to WordPress, this release adds the corresponding block to the editor.

It also brings some improvements to existing blocks including the possibility to define a custom focal point for the cover block’s background.

5.0 🇩🇪

Features

Add a new RSS block and follow-up improvements: 1, 2.
Add a new Amazon Kindle embed block.
Add a new FocalPointPicker component and use it to define the focal point of the Cover block background.

Enhancements

Optimize the re-rendering performance when inserting/removing blocks.
Improve the Reusable Blocks UX for contributor users.
Disable embed previews for the smugmug provider.
Make the fullscreen mode a desktop-only feature.
Accessibility:
- Add speak messages when using the FeatureToggle component.
- Change the inserter search result message from assertive to polite.
- Remove duplicate aria label from menu items.
Remove the “Show Download Button” toggle help text in the File block.
Render the block switcher as disabled if not available in a multi-selection.
Use a back arrow icon to clarify the Fullscreen mode exit button.
Limit the Gallery block columns count to the images count.
Automatically set a default block style if missing.
Hide empty categories from the Categories block in the editor.
Increase the padding of the gallery captions.
Add left/right alignments to the latest posts block.
Improve the columns margins.
Add a help text for the hide teaser toggle in the More block.
Improve the wording of the embed block messages.

Bug Fixes

Accessibility
- Fix the tab order of the date picker component.
Support non hierarchical taxonomies in the category selector component.
Fix WP_Screen::is_block_editor check when using the Gutenberg plugin.
Fix blocks marked invalid incorrectly due to special HTML characters.
Fix the Notice component styling.
Fix the :root selector in the editor styles.
Fix duplicate block toolbars.
Fix warning message when using the DateTimePicker component.
Fix the File block and Categories block style when applying custom classnames.
Fix the Gallery block styling in Microsoft Edge.
Fix the Button block styling when links are visited.
Fix Block Style preview not dismissed after selection.
Fix TabPanel buttons incorrectly submitting forms.
Fix hierarchical dropdown in the Categories block.
Fix wording for the color picker saturation.
Fix the save keyboard shortcut while in the code editor mode.
Fix the Google Docs table pasting.
Fix jumps when indenting/outdenting list items.
Fix FontSizePicker max width on mobile.
Fix PHP 5.2.2 Parser issue.
Fix plural messages POT generation.

Various

Add ESnext build setup and commands to the wordpress/scripts package.
Add “focus on mount” config to the DropDown component.
Improve the error handling in the data module resulting in clearer messages displayed in the console.
Support marking days as invalid in the DatePicker component.
Support block transforms with inner blocks.
Improve the styles of the editor notices with actions.
Replace Polldaddy embed block with Crowdsignal.
Avoid setting the generic Edit Post Title on load.
Deprecate window._wpLoadGutenbergEditor.
Avoid an empty classname when deleting custom classnames.
Add className prop support to the ServerSideRender component.

Documentation

Improve the components README files
- DropdownMenu.
- RangeControl.
- Add code example of the MediaPlaceholder component.
Add a accessibility dedicated page.
Add a Git workflow documentation page.
Reorganize the contributors guide.
Mention the dark theme support in the design docs.
Enhance the compose package documentation.
Expand the block templates code examples.
Fix unregisterBlockType code examples.
Clarify the block styles isDefault property.
Move the npm packages management documentation to a dedicated page.
Add a section explaining the links usage in the documentation.
Add a note about the wp-editor dependency when using RichText.
Update the isShallowEqual package documentation and tests.
Refresh the repository management doc.
Typos: 1, 2, 3, 4, 5, 6, 7.

Chore

Remove PHP Code maintained in Core and bump minimum WordPress version:
- Block registration.
- REST API Endpoints.
- Markdown support fix.
- Gutenberg body classname and responsive classname.
- Preloading API calls.
- Block detection utilities.
- List screen integration.
- Block content version.
- Block categories hook.
- TinyMCE scripts registration.
- Reusable blocks post type labels and listing page.
- Block Types Initialization.
- PHP Unit tests.
- Compatibility script.
- Meta boxes support.
- Polyfills.
- oEmbed Proxy Endpoint filter.
- Visual Editing Disabling.
Update browserlist dependency.
New E2E tests: Date floating for pending posts.
New ESlint rules:
- Enforce ES6 object shorthand syntax.
- Declare variables only when used.
Use ES5 eslint config for the is-shallow-equal package.
Mark the eslint config as a root config.
Remove the feedback form from the plugin.
I18n:
- Use a placeholder for the WordPress minimum version.
- Use Sentence case in toolbar tooltips.
Add the FontAwesome licenses to the GPL 2 compatible licenses.
Move the generated spec parser to the corresponding package.
Refactor the nonce apiFetch middleware.
Refactor the list block indent/outdent buttons.
Fix watching file changes on Linux.
Update the question issue template in GitHub to redirect help requests.
Fix wp-settings permissions in the local development environment.
Use a filter to populate the demo content.

Mobile

Improve the hide keyboard button.
Add the PostTitle component support.
Support Enter key press in the post title.
Support native Media Upload.
Support undo/redo in the post title.
Make the InspectorControls available for mobile blocks.
Add failed media upload support and cancel buttons.
Introduce the BottomSheet component.

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Riad Benguella 8:00 pm on February 5, 2019
Tags: core-editor

Editor Chat Agenda: February 6th

This is the agenda for the weekly editor chat meeting on Wednesday, 6th February 2019, 14:00 GMT.

Housekeeping

Release: Gutenberg 5.0
Project Update: Porting Widgets to Blocks

Call for Collaboration (REST API and Media teams)

Tasks Coordination

Open Floor

@nerrad: Handling support type requests in the slack #core-editor chat. I notice sometimes they are just getting ignored. Should we start actively directing people to the forums for them now? What ways could we make it more visible that the channel is not the place for general support?

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

This meeting is held in the #core-editor channel in the Making WordPress Slack.

#agenda, #editor-chat

Jb Audras 3:51 pm on January 25, 2019
Tags: 5.1 ( 21 ), core-editor, dev chat ( 277 )

Dev Chat Summary: January 23rd

This post summarizes the weekly dev chat meeting from January 23rd (agenda, Slack archive).

5.1 updates

Beta 2

5.1 beta 2 went out earlier this week.

There are a few tickets still open, most of them are related to fine tuning the WSOD handling.

Schedule update

Beta 3 is scheduled for January 29, this is also the soft string freeze. All string changes must be committed by then (except for the About page).

Dev notes status report

5.1 is being accompanied by a nice collection of dev notes, mainly from Make/Core but also from Make/Polyglots.

@desrosj is continuing to coordinate 5.1 dev notes. There are also plans to construct a 5.1 Field Guide that summarizes collects all dev notes.

Updates from focus reps and component maintainers

Meeting notes and summaries

Other calls/proposals

Proposal from @afercia to discuss a proposed change to the CSS Coding Standards
The Design Team has two posts requesting designs for:
- PHP Upgrade Page
- WordPress Showcase
@chanthaboune posted about strengths and challenges in the community seeking thoughts and feedback

Open floor

The Gutenberg Team is looking for more pull request reviewers. If you’re interested, please touch base with them in the #core-editor Slack channel. Details to be shared soon in a Make/Core Post.

About including recent Gutenberg changes in the currently scheduled release: the WordPress 5.1 cycle is being a bit stricter about non-regression bug fixes landing during the beta period, but WordPress 5.2 is expected to be able to take bug fixes during the WordPress beta period.

About the recent Post concerning the bulk edit process: many relevant opinions and thoughts were shared during the meeting.

@matt expressed a desire to reopen the tickets closed in the recent bulk edit.
@desrosj and @jeffpaul will work on a strategy for reverting closed tickets that have not been changed since the bulk edit, to allow the tickets to be properly evaluated for closure.
Component maintainers to review related tickets (via this custom query). However, the 5.1 release is probably going to delay the ability to do that.
Contributors can also use this Trac report (replacing “myusername” with their username and scrolling to those updated on January 4th) to find the tickets they have been involved with that were affected by the bulk closing.
A stale keyword and/or status was discussed as a good way to leave tickets open long term and avoid closing them as wontfix and maybelaterstatuses.
A post on Make/Core is coming next week to kick off the efforts of the new Triage Team.

This Dev Chat Summary post is open for further comments and discussions.

#5-1, #dev-chat

Riad Benguella 9:18 am on January 23, 2019
Tags: core-editor, editor ( 96 ), gutenberg ( 89 )

What’s New in Gutenberg? (23th January)

Gutenberg 4.9 is a big milestone in terms for performance improvements for Gutenberg. It introduces a new asynchronous mode for blocks rendering improving the responsiveness of the editor.

The Documentation efforts are still on-going with three new tutorials leveraging the Format API, the Sidebar Plugins API and Post Meta Blocks as well as a number of improved README files for our UI components.

In terms of developer experience, this release includes a lot of improvements to our e2e tests including support for aXe Accessibility testing.

4.9 🇦🇺

Performance

Implement an async rendering mode for the data module updates.
Avoid rerendering the block components when selecting a block.
Improve the performance of isEditorEmptyPost selector (13% typing performance improvement).
Data Module: Avoid persisting unchanged values.
Update withSelect to use type-optimized isShallowEqual.
Move data selection to event handlers (called only when necessary).
Improve the initial rendering time by optimizing the withFilters Higher-order component.

Bug Fixes

Fix RichText toolbar when using multiline=”li”.
Correct the margin of the block icons in the inserter.
Fix ampersand in post tags causing editor crash.
Remove alignundefined class from gallery block edit markup.
Disable the button to open the publish sidebar if locked.
Correct the default margin for buttons with icons.
Keep the date floating when for posts with “pending” status.
Fix using the EXIF title when uploading images.
Fix font size picker on mobile.
Fix z-index of the Reusable Block Inserter button.
Fix autop behavior when a text is followed by a div.
Fix warning when returning null from a data module generator.
Announce the screen reader messages in the correct order in Safari.
Check Post Type support in the options modal.

Enhancements

Support customizing the table background colors.
Support underlining text using the keyboard shortcut ctrl+U.
Apply the editor styles to the HTML Block Preview.
Improve the color swatch selection indicator.
Improve scrolling behavior in Fullscreen Mode in Edge.
Remove deprecated embed providers.

Refactor the alignements support in the Cover Block and the Categories Block.
Code quality improvement to getBlockContentSchema
Internationalize the excerpt documentation link.
Improve pasting of quotes with citations.
A11y
- Add a tooltip to the block list appender.
- Improve the color contrast of the inserter shortcuts.
- Remove the label from the Warning component’s menu.
Add an option to overwrite the block in the Warning component.

Extensibility

Support custom fetch handlers for wp.apiFetch.
Support additional data passed to the mediaUpload utility.
Add filter for the preview interstitial markup.
Avoid appending empty query string in wp.url.addQueryArgs.
Dispatch heartbeat events as hook actions to avoid the jQuery dependency.
Support adding classnames to the plugins sidebar panels.
Add a className to the parent page selector.

Documentation

Add tutorials for
- Creating sidebar plugins.
- Using the Format API.
- Creating meta blocks.
Reorganize the tutorials page.
Improve the UI component documentation:
- The ButtonGroup component.
- The IconButton component.
- The SelectControl component.
- The TextareaControl component.
- The TabPanel component.
- The Toolbar component.
- The FormToggle component.
Update the Gutenberg Release and the Repository Management docs.
Add new section on scoping JS code.
Use Block Editor instead of Gutenberg in the docs.
Mention the Advanced Controls Panel in the design guidelines.
Clarify the unregisterBlockStyle documentation.
Clarify the difference between the button block and the button component.
Scope JavaScript ES5 code example.
Fix incorrect code example.
Clarify the deprecated APIs.
Fix typos 1 2 3 4 5 6 7.

Chore

Improve CI build times.
Extract error messages from console logging in E2E tests.
Reorganization of the E2E tests setup and expose it as npm packages.
Add aXe accessibility E2E tests support.
Add E2E tests for the excerpt meta box plugin.

Mobile

Fix the Image Size implementation.
Fix scrolling long text content.

#core-editor, #editor, #gutenberg

pbrocks 4:36 pm on January 17, 2019
Tags: core-editor, editor ( 96 ), gutenberg ( 89 )

Editor chat summary: January 16

Phase 2

4.8 has been included in WordPress 5.1
4.9 is going to be released next week according to the regular schedule.
In order to address some feedback about how to get involved for phase 2 this post was shared to hopefully clarify this more.
Task Co-ordination
- The idea is not to get everything done for next week, a simple task could be to do some research and clarify the work needed to accomplish a task.
- The main features/focus for phase 2 are highlighted here.

Block Proposals Flow

@karmatosed raised the point of getting new blocks into core.
- When should something be proposed to core? Not all blocks should be core
- How can you propose a block to core?
- What ‘state’ should it be in?
- How do we proceed from proposal to iterate and collaborate?
- Don’t want to end up with 1000s of the same block

Widgets > Blocks

Need devs to build prototypes.
Would be great to get more people contributing and building these blocks.

PRs to highlight

E2e tests reorganisation — @gziolo has been doing some great work on e2e tests both for accessibility and also a way to make the e2e tests setup usable outside the Gutenberg repository, reference here.
A note for those who write e2e tests, they have been moved them to packages/e2e-tests/specs folder. As new blocks are developed supporting documentation should be developed and attached to the block some way.
New package with all e2e test utils wordpress/e2e-test-utils which is going to be published to npm next month and will allow some code reuse for those who can start writing e2e tests for their WordPress sites.
aXe accessibility testing
- The set of tools for accessibility static analysis which need integration with e2e tests to ensure that regressions are caught early on, learn more here.
- Issues need fixing, some of them are related to the fact that WordPress uses “screen-reader-text” class. More info here.
Async mode for the data module
- A big milestone in terms of performance improvements that is going to be included in 4.9.
- Make sure to test it extensively with your custom blocks plugins. More info here
Ready to review:
- Any volunteers to test and review these blocks?
- Tag Cloud (@soean)
- RSS Block: (@soean)

Action Items

Blocks Testing
- – classic widget block @jorgefilipecosta
- – Server-side registration @gziolo @aduth @pbrocks
- – Undo @aduth @mcsf
- – e2e tests @sheri
- – Widgets 2 blocks @ajitbohra @soean @pbrocks
- – Potential data improvements @nerrad
New Feature Testing –
- @gziolo wants to battle test wordpress/e2e-test-utils with WordPress core and Twenty X-teen themes. Once it’s solid hopes to see some tutorials published.
- @karmatosed will prepare a post gathering details/flow about core block candidates.

Open Floor

@chrisvanpatten — will have some free cycles this week to review docs PRs, particularly from a grammar/clarity/readability perspective. If anyone has PRs you want reviewed please DM him.
@luehrsen — would love to see a ‘blocks’ section on the ideas page: where people can propose blocks and plugin devs can pick that up. (Good case in point is @melchoyce’s Restaurant Design blog post)
Although @joostdevalk has expressed a desire to kill that ideas page in the past, and now that he’s in his new marketing position for the project he may very well follow through on that
@youknowriad — A premise of Gutenberg is to enable people to build custom blocks easily (for niche use-cases)
@ajitbohra — Perhaps a block library/pack as a plugin, for blocks that are not intended for core.
@paaljoachim — supports having options in blocks to create a top and bottom margin/padding, as we need space between blocks in the layout.

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

#meeting-notes, #editor-chat

#core-editor, #editor, #gutenberg

Riad Benguella 7:09 pm on January 11, 2019
Tags: core-editor, gutenberg ( 89 )

How to get involved in Gutenberg Phase 2

Having trouble figuring out how to get involved in the Gutenberg Phase 2 effort? Understandable! There are a lot of teams (and channels and blogs) to keep up with. This post will help you find the posts that are helping to define upcoming work as well as identify the places you can follow the conversation.

Development Information

Now that the 5.0 ship is sailing, it’s time to start looking at the second phase of Gutenberg. The 9 projects for 2019 include a few items we’ll be working on in Phase 2:

Creating a block for navigation menus.
Porting all existing widgets to blocks.
Upgrading the widget-editing areas in wp-admin/widgets.php and the Customizer to support blocks.
Providing a way for themes to visually register content areas, and exposing that in Gutenberg.

Work on these projects will continue throughout the year. An overview of tasks included in the current scope and features is outlined in this Github issue. It is a living document that evolves as progress is made toward achieving these goals.

Design Information

The second phase of Gutenberg required a lot of initial user research. Synthesizing this research is happening now. Details about how to get involved with this effort are outlined in this post.

Work on the research and subsequent design will also continue throughout the year. Regular updates will be shared on the Design P2.

Getting involved

While user research is in progress, there are a lot of development tasks that we can work on without additional design information. This includes improvements for phase 1 features, porting widgets to blocks and a lot more, as outlined in the “Actionable items” section of the Github issue linked above.

The main place to get involved is the Github repository. The #core-editor Slack channel is where developer coordination and live day-to-day discussions happen. The weekly developer meetings are held Wednesdays at 14:00 UTC.

Each meeting will have an agenda posted beforehand, so you can see if the topics up for discussion are relevant to your interests. Once completed, meetings will be summarized in a post, so that people who can’t participate synchronously, can catch up and comment asynchronously.

If you want to contribute to Phase 2 and still have questions about how to do that, please ask your questions in a comment on this post so we can make this resource even more useful!

#gutenberg

Riad Benguella 11:37 am on January 7, 2019
Tags: core-editor, editor ( 96 ), gutenberg ( 89 )

What’s New in Gutenberg? (7th January)

Gutenberg 4.8 is the first plugin release after WordPress 5.0 that is not going to be backported entirely to the WordPress 5.0.x releases. The bug fixes and performance improvements have been cherry-picked into the upcoming WordPress 5.0.3 release.

The Changelog is a bit long as it includes a lot of PRs that were merged but not included in previous versions due to the more critical work needed for the WordPress 5.0.x releases.

I’d like to particularly thank all the persons that helped and continue to help improve our docs. There has been a lot of nice improvements lately, including a Getting Started with JavaScript tutorial, improvements to the design guidelines to build blocks and high-quality README files for our UI components.

Work on the performance of the editor is also continuing and we can expect more improvements in this area in the next releases as well.

4.8 🚩