Title: Editor chat summary: Wednesday, 27 November 2019
Author: Jorge Costa
Published: November 28, 2019

---

 [  ](https://profiles.wordpress.org/jorgefilipecosta/) [Jorge Costa](https://profiles.wordpress.org/jorgefilipecosta/)
1:01 pm _on_ November 28, 2019     
Tags: [core-editor ( 764 )](https://make.wordpress.org/core/tag/core-editor/),
[editor-chat ( 27 )](https://make.wordpress.org/core/tag/editor-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/),
[summary ( 983 )](https://make.wordpress.org/core/tag/summary/)   

# Editor chat summary: Wednesday, 27 November 2019

This post summarizes the weekly _editor chat _meeting on [Wednesday, 27 November 2019, 14:00 WET](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191127T1400)
held in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1574863263125100).

## 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/](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 release was possible thanks to the efforts of 51 contributors. More details 
about this release can be checked on the [release post](https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/).

## Weekly Priorities

November priorities post: [https://make.wordpress.org/core/2019/10/29/whats-next-in-gutenberg-november/](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](https://github.com/WordPress/gutenberg/issues/18667).
> @youknowriad

## Task Coordination

### 󠀁[@youknowriad](https://profiles.wordpress.org/youknowriad/)󠁿

Worked on PR’s [Edit/Navigation Tool](https://github.com/WordPress/gutenberg/pull/18624),
[Fixed Toolbar on mobile](https://github.com/WordPress/gutenberg/pull/18686), and
[Add a header menu to switch between edit and select tool](https://github.com/WordPress/gutenberg/pull/18624).
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](https://profiles.wordpress.org/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](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 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 by the repository owner. [https://github.com/](https://github.com/)
   repository.

### 󠀁[@noisysocks](https://profiles.wordpress.org/noisysocks/)󠁿

Finished the work on [adding a welcome guide modal](https://github.com/WordPress/gutenberg/pull/18041),
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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/karmatosed/)󠁿

Contributed to the following tasks:

 * PR for Sentence case: [https://github.com/WordPress/gutenberg/pull/18757](https://github.com/WordPress/gutenberg/pull/18757).
 * Proposed an experimental PR to make everything sentence case [https://github.com/WordPress/gutenberg/pull/18758](https://github.com/WordPress/gutenberg/pull/18758).
 * Navigation PR for styles is now merged: [https://github.com/WordPress/gutenberg/pull/18553](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](https://profiles.wordpress.org/mapk/)󠁿 

 Worked on some reviews and triage, namely the NUX modal PR for [@noisysocks](https://wordpress.slack.com/team/U6SFAQ3EK).

### 󠀁[@paaljoachim](https://profiles.wordpress.org/paaljoachim/)󠁿

Looked closer at this issue h[ttps://github.com/WordPress/gutenberg/issues/17640#issuecomment-556866662](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](https://profiles.wordpress.org/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](https://central.wordcamp.org/about/). Łó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](https://profiles.wordpress.org/bph/)󠁿

Working on End User Documentation and connected with [@melchoyce](https://wordpress.slack.com/team/U02QJMG7R)
on her project to replacing gifs with videos.

## Open floor

[@scruffian](https://profiles.wordpress.org/scruffian/) brought the topic of how
we handle Full Site Editing blocks for non-adminadmin (and super admin) users.

[@youknowriad](https://profiles.wordpress.org/youknowriad/) referred the precedent
we have in media blocks to allow/disallow features based on user capabilitiescapability
A **capability** is permission to perform one or more types of task. Checking if
a user has a capability is performed by the `current_user_can` function. Each user
of a WordPress site might have some permissions but not others, depending on their
role. For example, users who have the Author role usually have permission to edit
their own posts (the “edit_posts” capability), but not permission to edit other 
users’ posts (the “edit_others_posts” capability)., and [@noisysocks](https://profiles.wordpress.org/noisysocks/)
referred the API we have to query user permissions.

[@scruffian](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/mrmark/) asked the use case Navigation 
Block and if it is intended to replace the menu system eventually. [@youknowriad](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/mrmark/) referred that the Next
Generation of Themes and how they integrate with the Block Editor should start being
conceptualized.

[@youknowriad](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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](https://make.wordpress.org/core/tag/core-editor/), [#editor-chat](https://make.wordpress.org/core/tag/editor-chat/),
[#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2019/11/28/editor-chat-summary-wednesday-27-november-2019/?share=linkedin)

# Post navigation

[← New CSS focus in Core](https://make.wordpress.org/core/2019/11/28/new-css-focus-in-core/)

[WP Notify hiatus till January 2020 →](https://make.wordpress.org/core/2019/11/29/wp-notify-hiatus-till-january-2020/)