This post summarized the editor chat from Wednesday, May 3, 2023, 14:00 UTC (agenda) held in the #core-editor channel moderated by @bph – Full transcript
Gutenberg 15.7 is now available for download from the plugins repository. Release post is in progress.
New Developer Blog (versus network, site) posts
FSE Program Testing Call #22: Front Page Fun – Deadline for feedback is May 8th, 2023
Developer Hours – Introduction to WordPress Playground will be held on twice
On May 23, 2023 at 17:00 UTC / 12:00 PM EDT hosted by Justin Tadlock
On May 24, 2023 at 8:00 UTC / 15:00 Indonesia Time hosted by Michael Burridge
@get_dave created a new overview issue for Navigation: WIP Navigation Overview: 6.3 Priorities
Fonts API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
@hellofromtonya posted an update for the Fonts API:
- The project board is now groomed, with card priority sorted in highest (top) to lowest (bottom).
- The Roadmap’s Ongoing work section is updated and tasks are split into
Required for Core introduction and
Future. The primary focus then is on completing the required for Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. items.
- Goal: introducing the API in WP 6.3
@twstokes noted recently fixed or improved
@annezazu mentioned: “There’s a new, very simple “UX and Polish” board that some of us are trying to curate for some developers to dive into.Any issue on this board should be actionable by developers specifically, not add any new features, and not require additional design thought or help.”
@mamaduka mentioned “I’ve been debugging flaky e2e tests and helping with reviews this week.”
Open Floor – extended edition
@proxxim posted on the agenda the following idea:
“The `templateLock` for feature `innerBlocks` might need more refinement” and provided the following use case:
“We want the client to be able to insert a maximum amount of two buttons in an innerBlock. The client should also be able to insert just one or zero buttons as well. The current implementation of templateLock does not offer a configuration option for such a use case.”
@aurooba commented: “This would be handy for a lot of different custom blocks I often also create where you need to maximum number of innerBlocks, rather than a specific amount.”, followed by another use case: a custom 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. to feature posts from another custom post type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.. The design directive explicitly asked to not allow more than 6, less than 6 was okay. “If the templateLock featured had a
max property, that would make it pretty simple.” she wrote.
Another use case: “Having a max (and even a minimum) is a pretty common pattern most folks coming from the world of ACF and similar plugins are used to. For example, the repeater field in ACF lets you define a minimum and maximum for its rows.” (also by @aurooba)
@fabiankaegy chimed in with an issue that’s already on the 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/ repo: Add ability to limit the number of items within an Inner Blocks area. @proxxim and @aurooba should join the discussion to give developer more scenarios to be sure a new API would cover the use cases.
Props to @paaljoachim for review
#core-editor, #core-editor-summary, #gutenberg, #meeting, #summary