Editor chat summary: Wednesday, 10 July 2019

This post summarizes for the weekly editor chat meeting on Wednesday, 10th July 2019, 13:00 UTC 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/ 6.1

Thanks to @noisysocks for the release of Gutenberg 6.1.  Highlights include:

  • motion on 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. reordering, 
  • performance improvements, and
  • a new `PluginDocumentSettingSlot` enabling third-party developers to add panels to the document settings sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme..

Very nice to see the editor becoming more polished over time. For a fuller description, please view this post and be sure to check out the short video that helps make the changes come alive.

Task Coordination

  • @mapk catching up on all the amazing work and jumping in to review and help keep things moving forward.
  • @aduth 
    • Custom block sources work is nearly ready for merge (currently a refactoring for meta attributes, but will build support for other sources like post properties, site options, etc) https://github.com/WordPress/gutenberg/pull/16402
    • Started exploring localStorage-based autosaves https://github.com/WordPress/gutenberg/pull/16490
    • I’ve got a few reviews I need to catch up on
    • Hopefully planning to tackle some lacking documentation I’ve seen mentioned in this channel over the past weeks
  • @youknowriad

has reviewed a bunch of PRs:

  • – Custom block attribute sources
  • – Mobile unit tests to be added to CI
  • – Smaller PRs here and there.

And worked on several things:

  • – Performance improvements
  • – Try to build a better Drag and Drop
  • – Work on 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): Edit and Navigation Mode
  • – Some low-level refactorings (Slots)
  • @getdave
    • Merged PR to allow alternative Blocks to register themselves to handle Grouping interactions (side benefit: also removes hardcoded refs to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./group within transformation logic)
    • Working on PR to add a grouping flag to the Block supports. This will allow Blocks to opt-in/out of being available to be grouped. This is because certain blocks shouldn’t be Groupable (eg: single column block).
    • #16278 Update to allow alternative Blocks to handle Grouping interactions
  • @epiqueras
    • – Reviewed: Custom Sources PR.
    • – Opened: FSE Templates PR, Block Invalidation Fix PR.
    • – Closed: Some issues that were fixed by parallel PRs.
  • @karmatosed
    • deep diving into the ‘needs design’ and ‘needs design feedback’ labels. My focus is on what can we ship, what needs to be made into multiple issues (some conversations grew) and what can have a quick mock to just get coded to see.  
    • Considering splitting out our project boards for ease.
  • @kjellr
    • I have a quick fix for @tellthemachines helpfully pinpointed the reason for failing tests in the borders + padding for nested blocks PR, but it’s still a little fragile, so I’d love another set of eyes.
    • I’m working on getting a V1 ready for the new Tips implementation, so @noisysocks can begin development:
    • Helping sort out a possible way to add a circular block style for images:
    • Working on comps for the Patterns API:
    • Finally, I’d love a dev to pick this one up at some point.
  • @joen created this PR to improve the consistency of how the trailing appender works in nested contexts. 
  • @jorgefilipecosta submitted a PR that expands block styles allowing users to select a default style per block, submitted some 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 merged old PR’s. Reviewed RichText refactors, live drag drop, custom parser options, and widgets in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.

Open Floor

  • @tellthemachines opened a new issue around automated tests and documentation on expected behavior. She’s looking for feedback in GitHub so unit testing can be better documented and easier to implement for all contributors. New contributor feedback is requested to further improve the tests. @mapk suggested a post about the topic to share information.
  • @spacedmonkey wants to add a custom block to the list of allowed blocks when extending the core/media-text block.
  • @spacedmonkey requested direction for an issue allowing inner blocks to be defined at the block level, making them filterable. While similar to the concept of child blocks opened under @youknowriad suggesting opening a new issue in 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 be the repository owner. https://github.com/ rather than reopening previous issue
  • @aduth will be restructuring GitHub tags to  remove “Theme” from “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/ or can be cost-based plugin from a third-party & Theme Interoperability”, add a new “Themes” label and will update descriptions

Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.

The agenda for the next meeting, 17 July 2019 13:00 UTC is here, please add anything you want to discuss.#meeting-notes, #core-editor#editor-chat#summary