This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, February 16, 2022, 14:00 UTC.
Async key project updates
We used to exchange key project updates synchronously during the chat. However, many of the key 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/ projects sustain a regular cadence of updates on their tracking issues on Github 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/.
This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:
- Focused on making inner blocks easier to locate.
- Interactive link states. (there are multiple issues for it.)
- Group 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. – add support for Background Images.
- Gathering consensus on add margin support to group block. #37344 PR. After a lot of thoughtful discussion I believe we have agreed this can be merged. Just needs final approval. Thanks again to everyone that participated in this discussion.
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.
Highlighted PR for preserving content in invalid blocks on behalf of @dmsnell. Share your thought and feedback.
Highlighted discussion on styling in Gutenberg.
The general gist from a themers / my POV: The editor is taking a lot of liberties from us at the moment and makes things harder than they need to be. (And there are a lot of thing breaking by classes suddenly disappearing.)
@tomaz I really like this idea, one thing that I’ve learned in the past is that this requires some strictness as to language/vocabulary and breadth of what can/should be state, and what are the rules behind extending it, how to extend it at core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. level and how to make it available at local/theme level.
Read complete transcript
#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary