This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 16th Oktober 2019 held in Slack. Moderated by @jorgefilipecosta.
Gutenberg 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.7
A new version of Gutenberg (6.7) was released this morning.
It includes lots of important bug 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 that were cherry picked and should also be part of WordPress 5.3. If you are finding any problem with this release please let us know or create an issue. This release was mostly about stability or performance. But includes Gradient backgrounds as a relevant feature. For more information see the release post: What’s new in Gutenberg? (16 October)
Weekly Priorities
Gradients: Theme support, classNames, custom UI User interface.
Full site editing: Site Title block 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., rendering engine, temporary template editing UI and start working on the multi-entity saving UI.
Improvements to the link UI (a bit mid-term goal).
Complex block interactions.
https://github.com/WordPress/gutenberg/issues/13202
Some requirements are needed before that: selection mode
https://github.com/WordPress/gutenberg/issues/17088 and better drag and drop.
A new Link UI comment made by @get_dave.
Issue: https://github.com/WordPress/gutenberg/issues/17557
PR: https://github.com/WordPress/gutenberg/pull/17846
A mention:
@jorgefilipecosta
To create a storybook for the new component to allow easier testing.
@youknowriad
Current storybook is only for wordpress/components and this is a wordpress/block-editor component if I’m not mistaken so there’s some organisation/thinking to do here.
@jorgefilipecosta
I guess it would also make sense to use storybook for components under block-editor.
Storybook links:
“Build bulletproof UI components faster” https://storybook.js.org/
WP Storybook for components: https://wordpress.github.io/gutenberg/design-system/components
Check the Core Editor discussion for more information.
Task Coordination
@youknowriad
I’m planning to review Full Site Editing and UI components (Card) related work. Work on the selection tools (breadcrumb and edit/select tools).
@andraganescu
Smart block appender
https://github.com/WordPress/gutenberg/pull/16708
Add horizontal option for the block movers
https://github.com/WordPress/gutenberg/pull/16615
Media Flow Component
https://github.com/WordPress/gutenberg/pull/16200
Also I will be reviewing as much as possible the two new Navigation Block PRs: navigation: Navigation customization
https://github.com/WordPress/gutenberg/pull/17832
Unified Link creation interface
https://github.com/WordPress/gutenberg/pull/17846
@gziolo
Finish or close all my open PRs which didn’t get to 5.3.
@karmatosed
Plan on picking up some ‘needs design’ that have been sat a while around smaller screen experience, for example buttons vanishing.
Giving design feedback the link interface iterations. https://github.com/WordPress/gutenberg/pull/17846#issue-325799134
Give feedback on the audit work.. come join me! https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+audit+label%3A%22Needs+Design+Feedback%22
@brentswisher
I plan on continuing on adding a notice of disabled blocks to block inserter when no results are found. Look into options for starting a new post in “editing” vs. “navigation” mode of the writing flow.
@koke
Template selector for new pages in the mobile apps. I have to catch up with the current Full Site Editing state and see how that would overlap with existing plans, and if the feature makes sense for core Core is the set of software required to run WordPress. The Core Development Team builds WordPress./web. I hope to have something more concrete to propose/discuss next week.
@vindl
I’ll try to write up some feedback and proposals on Block templates for Full Site Editing https://github.com/WordPress/gutenberg/issues/17512 based on the work and takeaways from https://wordpress.org/plugins/full-site-editing/
@mapk
Reviewing some of the block pattern work: https://github.com/WordPress/gutenberg/issues/17335
Helping to keep the drag n drop of images issue rolling. https://github.com/WordPress/gutenberg/issues/13202
@jorgefilipecosta
I will work on the Gradient related tasks on the priority list. I hope to submit a core patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to fix a kses rule to allow gradient styles for contributor roles. Besides the gradients related work, I will continue the work on the block style improvements.
@retrofox
Currently working on customization. The PR is really advanced. Feedback is more than over welcome!
Issue: https://github.com/WordPress/gutenberg/issues/17683
PR: https://github.com/WordPress/gutenberg/pull/17832
@mkaz
So I’ll continue to add components to storybook.
Open Floor
@brentswisher
In working on updates to the inserter https://github.com/WordPress/gutenberg/pull/17338 and it was pointed out that I can not use packages from edit/post in the inserter.
Check the Core Editor Slack discussion for more information.
#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary
