Title: Editor chat summary: January 16
Author: The API Guys
Published: January 17, 2019

---

 [  ](https://profiles.wordpress.org/pbarthmaier/) [The API Guys](https://profiles.wordpress.org/pbarthmaier/)
4:36 pm _on_ January 17, 2019     
Tags: [core-editor ( 764 )](https://make.wordpress.org/core/tag/core-editor/),
[editor ( 224 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 555 )](https://make.wordpress.org/core/tag/gutenberg/)

# 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 ](https://make.wordpress.org/core/2019/01/11/how-to-get-involved-in-gutenberg-phase-2)
   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](https://github.com/WordPress/gutenberg/issues/13113).

## 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. Proposals Flow

 * **[@karmatosed](https://profiles.wordpress.org/karmatosed/)** raised the point
   of getting new blocks into coreCore Core is the set of software required to run
   WordPress. The Core Development Team builds WordPress..
    - 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** — [@](https://profiles.wordpress.org/gziolo)**[gziolo](https://profiles.wordpress.org/gziolo)**
   has been doing some great work on e2e tests both for 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 also
   a way to make the e2e tests setup usable outside 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/](https://wordpress.org/gutenberg/)
   repository, reference [here](https://github.com/WordPress/gutenberg/pull/13228).
 * 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](https://github.com/WordPress/gutenberg/pull/13241).
    - Issues need fixing, some of them are related to the fact that WordPress uses“**
      screen-reader-text**” class. More info [here](https://make.wordpress.org/accessibility/handbook/markup/the-css-class-screen-reader-text).
 * **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](https://github.com/WordPress/gutenberg/pull/13056)
 * **Ready to review**:
    - Any volunteers to test and review these blocks?
    - [**Tag Cloud**](https://github.com/WordPress/gutenberg/pull/7875)  ([@](https://profiles.wordpress.org/soean)**
      [soean](https://profiles.wordpress.org/soean)**)
    - [**RSS Block**](https://github.com/WordPress/gutenberg/pull/7966)**:** ([@](https://profiles.wordpress.org/soean)**
      [soean](https://profiles.wordpress.org/soean)**)

## Action Items

 * **Blocks Testing**
    - – **classic 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. **block [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta)
    - – **Server-side registration** [@gziolo](https://profiles.wordpress.org/gziolo)
      [@aduth](https://profiles.wordpress.org/aduth) [@pbrocks](https://profiles.wordpress.org/pbarthmaier/)
    - – **Undo** [@aduth](https://profiles.wordpress.org/aduth) [@mcsf](https://profiles.wordpress.org/mcsf)
    - – **e2e tests** [@sheri](https://profiles.wordpress.org/sheri)
    - – **Widgets 2 blocks** [@ajitbohra](https://profiles.wordpress.org/ajitbohra)
      [@soean](https://profiles.wordpress.org/soean) [@pbrocks](https://profiles.wordpress.org/pbarthmaier)
    - – Potential **data improvements** [@nerrad](https://profiles.wordpress.org/nerrad)
 * **New Feature Testing** –
    - **[@gziolo](https://profiles.wordpress.org/gxiolo)** 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](https://profiles.wordpress.org/karmatosed)** will prepare 
      a post gathering details/flow about core block candidates.

## Open Floor

 * **[@chrisvanpatten](https://profiles.wordpress.org/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](https://profiles.wordpress.org/luehrsen/)** — would love to see
   a ‘blocks’ section on the [ideas page](https://wordpress.org/ideas): where people
   can propose blocks and 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/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. devs can pick that up. (Good 
   case in point is [@melchoyce](https://profiles.wordpress.org/melchoyce/)’s Restaurant
   Design blogblog (versus network, site) post)
 * Although **[@joostdevalk](https://profiles.wordpress.org/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](https://profiles.wordpress.org/youknowriad/)** — A premise of
   Gutenberg is to enable people to build custom blocks easily (for niche use-cases)
 * **[@ajitbohra](https://profiles.wordpress.org/ajitbohra/)** — Perhaps a block
   library/pack as a plugin, for blocks that are not intended for core.
 * **[@paaljoachim](https://profiles.wordpress.org/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](https://wordpress.slack.com/archives/C02QB2JS7/p1547647221650100).

The agenda for the next meeting is [here](https://docs.google.com/document/d/1yTi6uhIVFCOCDtAHMO10pNMrVgZ34GpddDA4wmfggcA/edit),
please add anything you want to discuss. [](https://make.wordpress.org/core/tag/dev-chat/)

 [#meeting-notes](https://make.wordpress.org/core/tag/agenda/), [#editor-chat](https://make.wordpress.org/core/tag/dev-chat/)

[#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/),
[#gutenberg](https://make.wordpress.org/core/tag/gutenberg/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2019/01/17/editor-chat-summary-january-16/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/fa9bb9feab2f2f97662e7b07c9deaf0aca3ec7c037840a8cc3563ec022f77048?
     s=32&d=mm&r=g)
 2.   [Miguel Fonseca](https://profiles.wordpress.org/mcsf/)  4:46 pm _on_ January 
     17, 2019
 3.  Thank you for the notes, [@pbarthmaier](https://profiles.wordpress.org/pbarthmaier/)!
 4.  ![](https://secure.gravatar.com/avatar/a2690bc3e7ef0350cac88e27809169288b0086b1714707655fd2635026a0670b?
     s=32&d=mm&r=g)
 5.   [Robert Anderson](https://profiles.wordpress.org/noisysocks/)  11:57 pm _on_ 
     January 20, 2019
 6.  Recap of the task co-ordination that [happened in the meeting](https://wordpress.slack.com/archives/C02QB2JS7/p1547648164678400):
 7.   * [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) to look
        into the classic 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. 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.
      * [@gziolo](https://profiles.wordpress.org/gziolo/), [@aduth](https://profiles.wordpress.org/aduth/)
        and [@pbarthmaier](https://profiles.wordpress.org/pbarthmaier/) to look at 
        server-side registration
      * [@aduth](https://profiles.wordpress.org/aduth/) and [@mcsf](https://profiles.wordpress.org/mcsf/)
        to look at undo improvements
      * [@designsimply](https://profiles.wordpress.org/designsimply/) to look at E2E
        test improvements
      * [@ajitbohra](https://profiles.wordpress.org/ajitbohra/) and Sören to investigate
        Widgets to Blocks
      * [@nerrad](https://profiles.wordpress.org/nerrad/) to investigate potential 
        data improvements
 8.  If you weren’t able to make the CoreCore Core is the set of software required 
     to run WordPress. The Core Development Team builds WordPress. Editor meeting but
     would like to spend this week looking into something on the list of [Phase 2 Scope & Features](https://github.com/WordPress/gutenberg/issues/13113),
     please reply inline here!
 9.   * ![](https://secure.gravatar.com/avatar/a61af5cd9a78137214c3f0b276a3d07bdb931397f4d7861ce6b818fd062b542d?
        s=32&d=mm&r=g)
      *  [Grzegorz (Greg) Ziółkowski](https://profiles.wordpress.org/gziolo/)  10:08
        am _on_ January 21, 2019
      * [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/), [@ajitbohra](https://profiles.wordpress.org/ajitbohra/)
        and [@soean](https://profiles.wordpress.org/soean/) – you all signed up to 
        help with Widgets to blocks project which looks as follows on 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/): [https://github.com/WordPress/gutenberg/projects/20](https://github.com/WordPress/gutenberg/projects/20).
      * It looks like [https://github.com/WordPress/gutenberg/issues/4770](https://github.com/WordPress/gutenberg/issues/4770)
        is what [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
        is focusing on. That leaves 3 PRs for new blocks which need review, one 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. which is still to develop, and one issue with refinements 
        to the existing Latest Posts block. [@ajitbohra](https://profiles.wordpress.org/ajitbohra/)
        and [@soean](https://profiles.wordpress.org/soean/) how do you want to be involved
        in the upcoming days? I will help with reviews.

Comments are closed.

# Post navigation

[← Dev Chat Agenda: January 16th](https://make.wordpress.org/core/2019/01/16/dev-chat-agenda-january-16th/)

[Media Meeting Recap – January 17, 2019 →](https://make.wordpress.org/core/2019/01/17/media-meeting-recap-january-17-2019/)