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.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 7.0

Gutenberg 7.0 was released. It brings the navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. out of the experimental state. The releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 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 ToolFixed Toolbar on mobile, and Add a header menu to switch between edit and select tool. Hopes to continue a trend of 50% reviews and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and 50% code.

@jorgefilipecosta

Gave support on the forums, triaged issues, rebased and updated some PR’s, submitted and merged several 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 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 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/ 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:

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 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Łódź, helped people on forums, worked on some triage based on reports from people. This week will resume the work on Block Patterns 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..

@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-adminadmin (and super 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