This post summarizes for the weekly editor chat meeting on Wednesday, 12th June 2019, 13:00 UTC held in Slack.
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/ 5.9
The release of Gutenberg 5.9, piloted by @nerrad, landed this morning. Over 40 individuals contributed, six of whom were first timers!! Some of the new features include:
- SnackBar Notices, brief messages that disappear after a short delay,
- the grouping/ungrouping feature that allows for grouping a number of blocks in a container, and
- new useDispatch and useSelect APIs were added to the data module.
There were also plenty of enhancements and 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, all of which were summarized in this post.
WordCamp Europe will take place next week in Berlin, Germany. As many from the group will be traveling to the event during meeting time, it was decided to skip next week’s meeting and regroup in 2 week’s time.
Gutenberg topics loom large for WCEU. In addition to a big number of sessions related to the 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. editor, @gziolo is leading the editor contributor table. Please stop by. The goal of the Gutenberg Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. table is to make it easier to contribute to Gutenberg. There are several tasks we can accomplish throughout the day:
- onboard a few new contributors, collect the feedback and work on documentation improvements to make the process smoother
- go through the list of open issues trying to identify tasks which would be an excellent fit for new contributors
- explore how we could automate the detection of pull requests sent by new contributors to ensure they get enough support from others
- triage issues looking for those which can be closed because they are no longer relevant, are duplicates or should be moved somewhere else
- @nerrad is refactoring a data component for editor initialization and also looking to picking up this issue.
- @joen is working on a PR to fix quote style.
- @jorgefilipecosta has been working on bug fixes and plans to help review @aduth PR’s related to reusable blocks refactor and use that work to solve biggest UI User interface problems of the widget 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. screen.
- @aduth working through a few columns improvements
- @mapk working to make disabled buttons in Gutenberg match Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in color and contrast
- @gziolo updated Block Registration API RFC waiting for final approval.
- @xyfi no follow functionality in Gutenberg.
- @youknowriad will be publishing packages to npm and also working on bringing motion to the block reordering, refactoring to the way we handle “post-meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.” attributes and the `re-resizable` dependency to support “snaps” when resizing images
- @garrett-eclipse raised a question around capitalization standards.
- @mapk created the Issue to gain greater exposure, consensus, and acceptance of capitalization conventions.
Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.
See you all in WCEU and for the others, rendez-vous in two weeks for the next editor chat.
Please Note: the agenda for the next meeting, two weeks hence, 26 June 2019 13:00 UTC is here, please add anything you want to discuss.
#meeting-notes, #core-editor, #editor, #gutenberg