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, April 13, 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 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:
- Patterns project we merged some big changes recently.
- A new UI User interface for the query 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. pattern selection UI And a pattern-based mechanism that allows the user to prefill the content of a page with a click is part of 6.0.
- For the page patterns one right now we did not create page patterns into the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or a core default theme so users don’t see anything yet.
- We should discuss if the core should ship a default page pattern or if a core theme like 2022 should do that.
For the next two weeks, my plan is to focus on :
- Wrapped up work on some of the tasks from the 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. scrub.
- Got a couple of issue numbers I’ve seen popping up on the list that I’ll pick if nobody does before but feel free to ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me – working along @paaljoachim gave a lot of insights so don’t be a stranger.
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.
Extending core search block
Proposed improving the ability to extend the Search Block to make it possible to easily use it as a block variation to provide a basic search experience for extensions that introduce new post types.
This would be helpful for creating standard patterns for things like e-commerce headers.
Search block extensibility would be nice, speaking from a place of interest of the elastic press team and possible integrations we might consider as well
Github issue with a detailed proposal will be created for further discussion.
Usage of CSS Cascading Style Sheets.
A question has been raised about the increasing use of the :where selector. The use of it in the block frontend output is of more concern than its use in the editor CSS. The concern is that this is unsupported in a reasonable percentage of older browsers, and doesn’t necessarily degrade gracefully.
It would be good to have this discussed wider, and a decision made about its continued use.
Read complete transcript
#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary