Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Agenda: Reconciling WordPress and 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/ Script Handles
Context | Previous Effort | Slack
Some points there seemed to be consensus on:
- As needed, existing scripts in WP core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. will be pulled into the GB repository, exposed as their own package, and then re-registered for use in core.
- Old handles will still be present for back-compat, but redirect to new handles.
Initial effort regarding this will happen for:
- shortcode package: https://core.trac.wordpress.org/ticket/44987
- a11y package: https://core.trac.wordpress.org/ticket/45066
Agenda: How should uncaught errors be handled
Context | Slack
There was much discussion on not only the specific issue (see context) that triggered this agenda but also how this might be generalized. In conclusion, there was some consensus to explore something along the lines of [this solution](https://gist.github.com/aduth/f464f2d549a80716127a7e0d575b102f) in concert with implementing error boundaries in
withSelect to see how they interact and work. So short-term focus will be on fixing the immediate issue with errors in subscriber listeners.
Further discussion effort on this will be done in the pull request @aduth will own this issue (in collaboration with others who help).
Agenda: Reusable Scripts
Context: here and here | Slack
We reached the point where we exposed every tool Gutenberg uses adjusted for external plugins development@gziolo
Related packages will be published soon.
- update repository (once package is updated on npm) (@gziolo)
- dev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:
a description of the change;
the decision that led to this change
a description of how developers are supposed to work with that change.
Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. about the package linking to the docs and repository (@gziolo)