Dev Chat agenda, Wednesday February 7, 2024

(Updated with pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party dependencies feature discussion request)

The next WordPress Developers Chat will take place on Wednesday February 7, 2024, at 20:00 GMT in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion of proposals and releases, updates on 6.5, and have an open floor section. Additional items will be referred to in the various curated agenda sections. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this post.

Quick links to agenda sections

Announcements

Welcome to the two team reps for the remainder of 2024: Joe McGill (@joemcgill) and Sarah Norris (@mikachan)! With the increasing collaborative approach between coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and core-editor, it is wonderful to have reps from both parts of the team. A post formally introducing them will be published later this month.

@hellofromtonya and @webcommsat are doing a handover, and Abha (@abhanonstopnewsuk on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. to tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) with any updates) will continue to curate the agenda until Sarah is back on February 21.

Discussions on open core proposals and releases

As advertised last week, this week’s Dev Chat will explore the recently published proposal: What’s next for the FSE outreach program.

  • This post recommends next steps, including a rename of the channel as ‘outreach’ to use it more widely to reach site builders and extenders. It could also be used to assist several projects which could use Slack support in the WordPress space for discussion, clarification, and overall ruminating on future features coming to WordPress. 
  • Timescales:
    • Feedback deadline: February 12, 2024.
    • A Hallway Hangout is scheduled on February 20, 2024, at 15:00 UTC to further discuss this proposal, the comments, and the next steps.

Potential proposal for discussion at Dev Chat on February 14, 2024: Proposal: Implement a PHP autoloader in WordPress Core.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Highlighted posts

Phase 3 media meeting agenda – this is scheduled for Thursday, 8 February 2024 at 00:00 GMT in the core-media channel on Make WordPress Slack

A Week in Core – February 5, 2024 – props to @audrasjb. On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., between January 29 and February 5, 2024, there were.

  • 66 commits
  • 117 contributors
  • 79 tickets created
  • 8 tickets reopened
  • 56 tickets closed
  • welcome to 25 new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. in core

New commit message requirements in Git and a Hello props Bot. Thanks to everyone who has worked on this historically and who have brought this to its latest update.

Proposal: Implement a PHP autoloader in WordPress Core. This updates the historic work on this and a proposed implementation.

6.5 release parties schedule and host

Core-editor updates

Props to @annezazu for collating and sharing this list.

  • 17.7 RC1 is set to be released this week, marking the last GutenbergGutenberg 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/ version to make it into 6.5.
  • Designs are continuing for the highlight grid for 6.5.
  • New marketing related issues opened for the 6.5 micrositevideo featurettes, and social media assets.
  • Font Library: work continues to merge the Font Library APIAPI 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. redesign and a quick change was made to make the Font Library more discoverable, with the need for more feedback as betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 lands.
  • Pattern overrides: a PR is underway to add the block name to the pattern content data to help support future features, like shuffling patterns that are within the same categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and a larger effort is underway to tighten up the accessibility of these non-editable bound fields.
  • Data Views: a primary filter API was added to enable set filters exposed by default in the interface for both pages (showing status) and patterns (showing sync status).
  • Link Control: work is underway to try to get in a PR that adds a “add block” UI for the navigation block link UI to help resolve feedback around how hard it is to add blocks to navigation.
  • BlockBlock 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. Bindings: after lots of discussions in slack, block bindings is moving forward to support custom fields and the ability to override blocks in synced patterns. The project as a whole is very open to feedback from extenders to see what can be added in the future.
  • Interactivity API/Block effects (name is in flux): the PR to officially launch this new API is very close to landing (core reviews welcome! thank you to those who have reviewed).

Developer Blogblog (versus network, site) update

Developer Blog summary, February 1, 2024 – this includes recently published posts. The following topics still need a writer:

If you are interested in taking on a topic from this list or know someone who would be a good person to writer about them, comment on the issue or in the #core-dev-blog channel.

Forthcoming release updates

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.5

Updates from the release squad can be shared in the Dev Chat. In addition, there are also the following updates identified and discussed in Slack.

6.5 release updates

  1. The first draft of the Beta 1 announcement is ready for review. Please share your feedback by February 8, 13:00 UTC.
  2. For anyone following on in the 6.5 release leads channel, the latest async updates from the various areas starts at this Slack message.
    • This includes an update on the monitoring of a performance regression, which is being addressed.
    • A final decision is needed on a design concept for the feature tiles.
  3. Discussion on Patterns in Classic Themes feature and reviews to help progress this area. Update 16:06 UTC, Feb 7: this is regarded as resolved. Thank you for all those who were involved.

4. Call for Testers early draft for 6.5. Publication date is just before Beta 1. Discussion on Slack if you are able to help.

5. Next general bugbug 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. scrubs for 6.5:

Discussion on Plugin dependencies feature

You can also view discussions taking place in #core-upgrade-install channel on Slack. This has been highlighted as a potentially very valuable feature for 6.5 and was merged into ‘trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.’ on Tuesday. Note this is the last dev chat before Beta 1.

Tickets to highlight for assistance

Tickets for 6.5 will be prioritized. Tickets can be referenced in the comments section of this agenda if you are unable to make the meeting and for asynchronous involvement.

Open floor

Raising awareness and amplifying the new core contributor sessions – the ticket is on the Marketing Team GitHub. It picks up a discussion in the sessions and from recent contributor days.

  • Action: comment on the ticket for any support you may be able to offer or if you can identify opportunities to amplify awareness of the sessions.

#6-5, #agenda, #dev-chat

Dev Chat agenda, January 31, 2024

The next WordPress Developers Chat will take place on Wednesday January 31, 2024 at 20:00 GMT in the core channel on Make WordPress Slack.

Announcements

WordPress 6.4.3, security and maintenance release, went live on January 30, 2024. It features 5 bug fixes on Core16 bug fixes for the Block Editor, and 2 security fixes.

Post dev chat: What’s new in Gutenberg 17.6 published.

Discussions

These will focus on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release items.

This week will provide a discussion opportunity during Dev Chat to explore this open core proposal relating to major release Field Guides.

Proposed for next week’s Dev Chat a look at the just published proposal: What’s next for the FSE outreach program.

  • This post recommends what could be next. One suggestion is to rename the channel as ‘outreach’ and use it in a wider way to reach site builders and extenders. Another use of this channel could be to assist several projects which could use SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. support in the WordPress space for discussion, clarification, and overall ruminating on future features coming to WordPress. 
  • Timescales:
    • Feedback deadline: February 12, 2024.
    • A Hallway Hangout is scheduled on February 20, 2024, at 15:00 UTC to further discuss this proposal, the comments, and the next steps.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Highlighted posts

Dev Chat summary from January 22, 2024. Props to @webcommsat and @ironprogrammer for running the meeting and summary.

A Week in Core – January 29, 2024 – props to @audrasjb for pulling this together.

Changes on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 22 and January 29, 2024:

  • 48 commits
  • 64 contributors
  • 60 tickets created
  • 4 tickets reopened
  • 67 tickets closed
  • welcome to two new contributors to core this last week

Core-editor updates

Props to @annezazu for collating and sharing this list.

  • Design draft shared for the highlight grid for 6.5.
  • Section Styling: this work has been punted due to some blockers in resolving CSSCSS Cascading Style Sheets. specificity questions.
  • Font Library: biggest work continues to be the Font Library: refactor REST API which was merged into Gutenberg following this merge criteria for this feature and had a quick PR to follow up on feedback. Outside of that, a discussion is underway around making the font library more discoverable.
  • Pattern overrides: there are some current questions around how this features ties to the BlockBlock 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. Renaming APIAPI 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. and how the internal block ids are generated and used. Right now, we can find the block names through block ids, but we cannot do the same the other way around.
  • Data Views: a recap of what’s planned and stable for 6.5 has been shared along with a PR to add sync status by default for Patterns, matching the current experience.
  • Link Control: A bigger PR was merged for Implementing new UX for invoking rich text Link UI by requiring explicit activation before displaying the Link UIUI User interface interface.
  • Block Bindings: the experimental flag was removed along with an outline of next steps for Gutenberg RC, Beta, and what’s out of scope for 6.5 (including when to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.). For out of scope, this includes a UI for users to add bindings. A ~4 min video walks you through the current status in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.!

General updates

An issue was opened for Media workflows around patterns that any media minded folks will find interesting. 

Releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.5

Any updates, bugbug 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 list or updates on betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1?

Beta 1 for WordPress 6.5 scheduled for February 13, 2024.

Reminder: Proposed Phase 3 media library planning meeting will take place on Thursday, 8 February 2024 at 00:00 GMT in the #core-media
channel. 

Existing 6.5 links

Latest minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.4.3

WordPress 6.4.3 is now live.

Tickets to highlight for assistance

Tickets for 6.5 will be prioritized.

Open floor

#agenda, #core, #dev-chat

Dev Chat agenda, January 24, 2024

(Update from new Contributor Meeting added)

The next WordPress Developers Chat will take place on Wednesday, 17 January 2024 at 20:00 GMT in the core channel on Make WordPress Slack.

Discussions

These will focus on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release items.

  • Interactivity API and building interactive blocks has moved past the proposal stage and is aimed at being a key feature planned for 6.5. Now that it’s near complete and planned for 6.5:
    • is there anything actionable in the proposal?
    • or is it considered done / closed?

Next week’s dev chat, a discussion opportunity is identified for this open proposal on core relating to major release Field Guides.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Highlighted posts

Summary from the experimental new style Dev Chat from January 17, 2024@webcommsat and @hellofromtonya

A Week in Core – January 24, 2024 – props to @audrasjb for creating this.

On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 15 and January 22, 2024:

  • 35 commits
  • 62 contributors
  • 67 tickets created
  • 10 tickets reopened
  • 72 tickets closed
  • and a welcome to three new contributors

Performance team roadmap for 2024 is out and covers priorities.

Team reps update. The nomination period has been extended for the Core Team Reps 2024 edition to Wednesday, 31 January 2024 at 23:59 GMT. Full details are on the original nominations post where nominations can be added.

New core contributor meeting – if you were not able to attend and would like to find out more, check out the link to the meeting in Slack on January 24, 2024 which includes useful information on getting started and the contributor mentorship program. The deadline for applications for the second cohort for the program is Wednesday, February 7, 2024.

Core-editor updates

Core Editor Improvement: Robust Revisions in the Site Editor.

Props to @annezazu for sharing this list.

Releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.5

Any other updates?

Phase 3 media library meeting will take place on Thursday, 8 February 2024 at 00:00 GMT in the #core-media
channel. The Media Component team is coordinating a meeting with the Editor team and other interested stakeholders to work on planning for the proposed Phase 3 Media Library.

Core-editor improvement – revisions in the site editor. This is a useful post for understanding some of the changes and new features to current revision functionality in the Site Editor aimed for 6.5 and the wider work in this area. 

WordPress 6.5 release squad formation as at January 18, 2024. Additional discussion on size of the squad can be found in the comments on this post.

Important milestones in the Editor for 6.5 – useful post for contributors working or wishing to support the GutenbergGutenberg 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/ repository with the scheduled betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 for WordPress 6.5 scheduled for February 13, 2024.

Existing 6.5 links

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.4.3

Any other updates?

Earlier today there were four open tickets – update in 6.4 release leads channel.

Tickets to highlight for assistance

Tickets for 6.5 and 6.4.3 will be prioritized.

Open floor

#6-4, #6-5, #agenda, #dev-chat

Dev Chat Agenda, January 16, 2024

The next WordPress Developers Chat will take place on Wednesday January 17, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

Dev Chat evolving

Using the weekly curated agenda post for live and asynchronous usage, this meeting will begin an experiment to dedicate time to current proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and to help specifically with progressing releases.

  • Through the summaries of the discussions and SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. links, those unable to join live, will continue to be able to read and contribute asynchronously.
  • The links in the various agenda sections below will not be shared in full in the meeting, but be available for pre and post-reading. Anything for particular discussion can still be highlighted.
  • If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this post.

Discussions

These are some of the current proposals in core for awareness and which may be suitable for further discussion in Dev Chats.

  • Proposal: Default Theme Task Force for 2024
    •  This focuses on considering how the team approaches the maintenance of the default themes to make them easier to maintain, and more future-compatible. With the release of Twenty Twenty-Four, there are now 14 default themes maintained by the project.
  • Proposal: improve the editor tech workflow for major releases
    • This proposal is focused on a workflow for merging GutenbergGutenberg 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/ into Core
    • This could be an ideal time to discuss to discuss and experiment based on 6.4 learnings for the benefit of 6.5.
    • As Dev Chat now has a combined input from the Gutenberg and Core meetings, there is opportunity for discussing this further during the meetings and for a deeper discussion on what could be done in 6.5.
  • Interactivity API and building interactive blocks has moved past the proposal stage and is aimed at being a key feature planned for 6.5. An update has been requested to share with Dev Chat.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Announcements

6.4.3 – next maintenance release – the post includes the planned schedule, the dates of the bugbug 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. scrubs, and the final release date of 30 January 2024.

Highlighted posts for information

These will not be re-shared in full in the meeting itself to enable time for discussions in a new experimental approach to Dev Chat.

Dev Chat Summary from January 10, 2024.

New versions for the default themes for the Twenty Twenty-OneTwenty Twenty, and Twenty Seventeen are now available for download. 

A Year In Core: 2023 – just a few highlights from this detailed post. Props to @sabernhardt and @audrasjb.

  • In 2023, the WordPress Core team shipped 2211 commits (2597 in 2022). 2751 tickets were opened, 2545 tickets were closed, and 365 were reopened.
  • Also, 1079 people contributed to WordPress source code using TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (988 in 2022), and 472 people made their very first contribution to WordPress Core (398 in 2022).

A Week in Core – January 15, 2024 – props to @audrasjb. On Trac, between January 8 and January 15, 2024:

  • 37 commits
  • 64 contributors
  • 51 tickets created
  • 6 tickets reopened
  • 58 tickets closed
  • 8 new contributors to core!

Team reps update. The nomination period has been extended for the Core Team Reps 2024 edition to January 31, 2024 at 23:59 UTC . Full details are on the original nominations post where nominations can be added.

Call for mentors/ mentees for Contributor Mentorship program’s second cohort – deadline for applications, February 12, 2024

The Feature Projects page has had an update and worth checking out for the latest statuses. Feature Projects are intended to concentrate a group of people together, to explore potential ideas for WordPress Core.

Data Liberation in 2024 

What’s new for developers? (January 2024) on the Dev Blogblog (versus network, site).

Core-editor updates

Thanks to @annezazu.

For information

  • New tracking issue: Section Styling, Colorways, and Typesets for WP 6.5.
  • Font Library: biggest work for now is the Font Library: refactor REST API which needs feedback. Please help review if you have experience with the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/..
  • Pattern overrides: work is ready to test starting with making paragraph blocks overrideable. Up next, headings, buttons and images are expected to be added soon as blocks that can have overrides.
  • Navigation: customize the navigation overlay with a template part, enabling a separate menu experience for mobile, has been punted from 6.5 by contributors.
  • Design tools: PR merged to add backgroundSize feature with implicit repeating backgrounds to add more functionality to the Group blockBlock 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.’s background image support that was added in 6.4. Needs PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports.
  • Data Views: Templates is now stabilized with Pages, Patterns, and additional views in Templates added in as experimental. Questions around extensibility came up recently — extensibility is very much part of the plan with the focus currently being on stabilizing the base APIs.
  • Add appearance tools support for classic themes: this work has been completed and merged into Core trunk. This opens a world of design options that, up until this point, have been only available with Block Themes, or themes using theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML..
  • Interactivity APIAPI 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.work continues for a public launch with 6.5 including a recently merged PR to render the root interactive blocks in Server Directives Processing.
  • Block bindings API: block bindings prototype is being split into smaller PRs to move work forward in smaller chunks with the PR that sets the basis for the API recently merged (this doesn’t add a UIUI User interface to create the bindings).

New (thanks to @bph)

Releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.5

Please also view the updates relating to 6.5 related updates under the core-editor heading above.

A release squad announcement is expected shortly.
Next milestone: BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is Feb 13, 2024.

New links on 6.5 since last week:

Recording of hallway hangout: Let’s explore 6.5

Early opportunities to test WordPress 6.5

Note update on the Font Library API design proposal with a particular note for REST API folks to view as per this comment. The navigation overlay has been punted from the 6.5 roadmap by the contributors working on this feature.

Any other updates on the Font Library?

Could you help with running a bug scrub around a particular area, component, or towards 6.5? More information on running scrubs. More dates for 6.5 bug scrubs will also be added once a squad is in place.

Existing 6.5 links

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.4.3

  • As shared above in Highlighted Posts, the next maintenance release will be 6.4.3.
  • Milestone: RC1 January 25, 2024
  • Release slated for: January 30, 2024
  • Bug scrubs and more information is in the link above.
  • 6.4-release-leads channel on Slack

Gutenberg releases

17.5 can be downloaded from the Gutenberg plugins page.

Update: A “What’s new in Gutenberg 17.5” has been published – thanks @scruffian and everyone who worked on 17.5.

Tickets to highlight for assistance

Priority will be given to tickets relating to 6.5.

Open floor

You can post suggestions in the comments box. Please indicate if you are intending to be at the meeting for any queries.

Thanks to @hellofromtonya for discussion on the core proposals lists and @annezazu for sharing the core-editor updates.


#agenda, #core, #dev-chat

Dev Chat agenda, January 10, 2024

The agenda for the first dev chat after the seasonal break is below. The meeting takes place on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on January 10, 2024 at 20:00 UTC .

(Update: GutenbergGutenberg 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/ testing requests have been added under the Releases heading.)

Welcome and housekeeping

All welcome.

Announcements

What’s new in Gutenberg 17.4

Reminder: call for volunteers for 2024 major releases.

Highlighted Posts

Posts during the break were highlighted in the following post. Many of the items in that post are still relevant, including a reminder that the core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nomination period had been extended until January 12, 2024 at 23:59 UTC, to give more time for Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to consider and nominate other contributors and/or themselves. Nominations post for 2024 core team reps.

In the last few days, there have been the following new posts:

A Week in Core – Jan 8, 2023 – big thanks to @audrasjb

On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 1 and January 8, 2024:

  • 19 commits
  • 20 contributors
  • 26 tickets created
  • 2 tickets reopened
  • 21 tickets closed

Phase 3, agency outreach recap @s1m0nd on an outreach exercise to enterprise WordPress agencies specializing in enterprise projects, inviting them to a series of informal show-and-tell sessions.

Update from the Developer Blogblog (versus network, site)

New design is live.

What’s new for developers, December 2023.

Writers are invited for the following articles on the WordPress Developer Blog:

To volunteer or ask further queries, comment on the GitHubGitHub 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/ tickets linked. If you need further assistance, post a message in the in the #core-dev-blog channel.


Core-editor update

Props to @annezazu for this update from January 2, 2024.

For information:

Release updates

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.5

Existing links:

Gutenberg updates

Thanks @bph for sharing.

  • Gutenberg plugin 17.5 RC1 is now available for testing
  • WordPress 6.5 Roadmap: a few features are already available in Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and could use some testing and feedback (the links below are tracking issues)

Tickets for assistance

Tickets can be highlighted for this section of the agenda, priority will be given to 6.5 release items.

Open floor

#6-5, #agenda, #core-editor, #dev-chat

DevChat agenda – December 13, 2023

The next weekly WordPress developers chat will take place on Wednesday, December 13, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

Dev Chat summary from December 6, 2023

Props to @webcommsat for the agenda preparation, and @ironprogrammer for facilitating the meeting.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

Replay of the State of the Word 2023, in Madrid.

Highlighted posts

Roadmap to 6.5

What’s new in Gutenberg 17.0. This latest release is available for download. It includes some Site Editing improvements, including the ability to drag and drop to the top and bottom of the document and sticky table headers, improvements to the Interactivity APIAPI 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. docs, many bugbug 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 and a range of other improvements.

Raising the minimum version of MySQL in WordPress 6.5. In WordPress 6.5, the minimum required version of MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. will be raised from 5.0 to 5.5.5. 

What’s new for Developers, December 2023 edition is available on the Dev Blogblog (versus network, site).

A recording is now available for the Hallway Hangout: Performance End of Year Review 2023

Reminder: Feedback requested on redesign of Developer Resources section of WordPress.org and a call for testing.

Nominations for 2024 edition, core team reps – nominations still open!

Please add any additional highlighted posts in comments.

Update from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor

This is a new experimental section in the agenda.

Thanks to @annezazu for sharing this update.

  • Data Views: Add: Bulk actions API to dataviews and an initial bulk trash action, add Data Views to storybook to allow for UIUI User interface development in isolation, extract data views to a dedicated bundled package, and check out some recent designs for the grid layout.
  • Font Library: new issue opened on Improve UX — share any feedback you might have around what might help improve the experience ahead of 6.5.
  • Navigation: Draft PR and exploration to allow the navigation block to have a fluid breakpoint.
  • RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: Draft PR to integrate the Style Book in with Style revisions. This would give a high level overview of what’s changed with style decisions.
  • Site Editor: Various zoomed out mode experiments are being explored. This helps move forward a previously worked on GutenbergGutenberg 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/ experiment tied to this overview issue. For example, image a more exploded/zoomed out view when inserting patterns from the Inserter to allow you to see more of your site and see where the insertion zone of the pattern is.
  • Performance: fix typing performance by not rendering sidebar in the Site Editor along with various other PRs have been merged.
  • UXUX User experience: The copy for warnings for removing key blocks, like post content or query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.has been simplified and updated to help add more friction to the experience. Please keep sharing feedback here so we can iterate quickly!
  • BlockBlock 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. Bindings API: a Draft PR showing a first prototype of the Block Bindings API and the metadata source with a 6 min long explainer video: Add block bindings API basis and metadata source
  • A backwards compatibility and backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. to a minor WP release fix to be aware of with SlotFill: SlotFill: Allow contextual SlotFillProviders.
  • If folks have run into the following issue, please write a comment sharing something about your experience: Block styles set via the “css” property in theme.json are ignored on the frontend in classic themes. This was flagged as a comment on the 6.5 post and I’m curious to get a sense of broader impact.


Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

WordPress release: 6.4

Any new issues?

New updates on 6.4.x release team or dates for 6.4.2?

Next major WordPress release: 6.5

Any other new updates?

Roadmap to 6.5 is out (as highlighted above)

6.5 documentation tracker has been started on GitHubGitHub 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/. A request from @webcommsat please add to tickets as ‘needs dev notedev 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, and 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.’ and/or ‘add to Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.’ when a ticketticket Created for both bug reports and feature development on the bug tracker. is close to commit.

https://github.com/orgs/WordPress/projects/154

Existing 6.5 links:

Scrubs

Are you able to help with future bug scrubs? Bug scrubs post.

Next scrub: December 19, 2023 at 19:00 UTC in the core SlackSlack 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.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticket if needed.

Request: TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #17379 has a fix with a unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. and testing instructions. Feedback, reviews and help to get it to the next stage requested by Nate Allen.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

New Contributor Chat is currently on Wednesdays at 19:00 UTC in the core channel on Slack. Next one will be on December 13, 2023. More details in the schedule. @oglekler has highlighted that this may be a late time for some, and if there are any volunteers to facilitate these meetings in APAC friendly-time?

Dates for Dev Chat

Reminder: the last Dev Chat in 2023 will be on December 27, and the first in 2024 will take place on January 4.

#6-5, #agenda, #dev-chat

Dev Chat agenda, December 6, 2023

The next weekly WordPress developers chat will take place on Wednesday, December 6, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

Dev Chat summary from November 29, 2023 – props to @webcommsat for the agenda and summary, and @hellofromtonya for facilitating the meeting.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

Highlighted posts

6.4 Retro recap

Proposal for a default theme task force for 2024

Feedback requested on redesign of Developer Resources section of WordPress.org and a call for testing.

Summary posts covering content from November 2023: What’s new for Developers, November 2023 and What’s New on Learn WordPress, November 2023 edition. More developer-focused posts are available on the Developer Blog.
The next editorial meeting has been moved to December 14, 2023, 13:00 UTC in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-dev-blogblog (versus network, site) channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Create tours available for Make P2s (team blogs)

Nominations for 2024 edition, core team reps – nominations open!

Core Team update, December 4, 2023

Please add any additional highlighted posts in comments.

Update from core-editor

This is a new experimental section in the agenda.
Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

WordPress release: 6.4

Any new issues?

New updates on 6.4.x release team or dates for 6.4.2?

Next major WordPress release: 6.5

Any new updates?

Existing 6.5 links:

Scrubs

Are you able to help with future bugbug 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. scrubs? Bug scrubs post.

Next scrub: December 19, 2023 at 19:00 UTC in the core Slack channel.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

Dates for Dev Chat

The last Dev Chat in 2023 will be on December 27, and the first in 2024 will take place on January 4.

#agenda, #dev-chat

Dev Chat agenda, November 29, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 29, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

Dev Chat summary from November 27, 2023 – props to @marybaum for facilitating and the summary.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

What’s new in Gutenberg 17.1

Highlighted posts

Summary of the Hallway Hangout on the triage extensibility issue https://make.wordpress.org/core/2023/11/27/summary-hallway-hangout-triage-extensibility-issue/

Hallway Hangout: let’s explore WordPress 6.5 – this will take place on Zoom on Tuesday, January 14, 2024 at 21:00 UTC. All welcome to join, whether it is to listen or participate too. There will be a recording and recap published. The event will be in the form of a free flowing demo/ presentation going through as many 6.5 release priorities as possible. The release has a proposed schedule of March 26, 2024.
More on 6.5 further down the agenda.

Please add any additional highlighted posts in comments.

Update from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor

This is a new section in the agenda as a pilot.

Update on the Core Editor via @annezazu:

In the meeting or in the comments for async contributions, @annezazu asks if folks can please emoji reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. with feedback to give a sense of whether she is on/off track:  = good,  = okay,  = bad. For anything other than green, feel free to thread a comment during the meeting with feedback or link the item and add it to the comments below.

Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

WordPress release: 6.4

Any new issues?

New updates on 6.4.x release team or dates for 6.4.2?

For those who were missing the core contributor profile badge and should have received it after 6.4, profiles have been updated. Slack update. should have it now.

Next major WordPress release: 6.5

Any new updates?

WordPress 6.5 Editor Tasks board is out.

Development cycle page.

Are you able to help with future bugbug 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. scrubs? Bug scrubs post. Check out the tickets discussed at the bug scrub on November 28, 2023. Next scrub: December 5, 2023 at 19:00 UTC in the core SlackSlack 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.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

a) Reminder from last week: Josepha has asked in the Team Reps channel for highlights from the last year, if you have any item you feel should be included about core’s achievements or items in progress, please add them to the comments on this post for @webcommsat and @hellofromtonya who are preparing the bullet points to send for core. Please do share any comments on this agenda.

b) Nominations for Core Team Reps: 2024 edition – reshare of the draft post to gather suggestions on timings related to the end date for nominations and the end of the voting period. The voting tool to use and whether an embedded voting block in discussion with other teams would be available for this edition to be finalized.

Please do consider whether you could stand for the core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for next year.

#6-4-x, #6-5, #agenda, #dev-chat

Dev Chat agenda, November 22, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 22, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

Dev Chat summary from November 15, 2023 – thanks @ironprogrammer and @webcommsat

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

What’s new in Gutenberg 17.1

Highlighted posts

Exploration to support Modules and Import Maps – this post shares the collaborative effort to explore native support for modern JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. modules and import maps within the WordPress ecosystem to enhance the developer experience. Details of how you can get involved with this initiative are in the post.

Please add any additional highlighted posts in comments.

Introduction

Update from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor (New section in the agenda)

Initially items relating to this will be posted as comments on the agenda by @annezazu and others.

Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

WordPress release: 6.4 – any new issues?

Any new updates on 6.4.x release team or dates for 6.4.2?

Next major WordPress release: 6.5

Update opportunity.

Development cycle page.

Are you able to help with future bugbug 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. scrubs? Bug scrubs post.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

a) Josepha has asked in the Team Reps channel for highlights from the last year, if you have any item you feel should be included about core’s achievements or items in progress, please add them to the comments on this post for @webcommsat and @hellofromtonya who are preparing the bullet points to send for core.

b) Nominations for Core Team Reps: 2024 edition – reshare of the draft post to gather suggestions on timings related to the end date for nominations and the end of the voting period. The voting tool to use and whether an embedded voting blockBlock 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. in discussion with other teams would be available for this edition to be finalized. Please do consider whether you could stand for the core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for next year.

#6-4, #6-5, #agenda, #dev-chat

Dev Chat agenda, November 15, 2023

The next weekly WordPress developers chat will take place on Wednesday, November 15, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Welcome and housekeeping

All are welcome to join Dev Chat.

If you can help with dev chat summaries, please raise your hand in the meeting.

Announcements

WordPress 6.4.1 became available on November 8, 2023.

For background information:

Highlighted posts

What’s new in Gutenberg 17.0

WordPress 6.4 performance improvements (this will be added to the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.). @swissspidy has also published his own post on how to get started with WordPress performance https://pascalbirchler.com/wordpress-performance-testing/

An update to the Field Guide with a new dev notedev 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, and 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.: Main query loop handling for block themes in 6.4.

Post on an update to the core commit message format. It has been updated to take into account backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. and follow up commits. There is also a change on where ‘props’ is used in the commit message.

Call for what is currently needed with 6.4 End User documentation (HelpHub)
Documentation tracker on GitHub for 6.4 end users.

Reminder from last week’s schedule dev chat: (not all these may be featured in the dev chat on November 15 depending on time available).

Forthcoming release updates

WordPress release: 6.4 – any issues

Reference information:
Field Guide for 6.4
– All Developer Notes relating to 6.4 can be found using this tag.

Next major WordPress release: 6.5

The development cycle page has been created. It will be populated post the discussion on release timings and the finalization of the squad.

Are you able to help with future bugbug 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. scrubs? The next bug scrubs post.

Bug scrub on November 14, 2023. The list of tickets in milestone by the scrub. Start of the scrub for those looking at tickets async.

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.5 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

This was due to be shared at last week’s dev chat. Bringing it again to November 15, 2023:
Nominations for Core Team Reps: 2024 edition – @webcommsat to reshare the draft post and timings. To continue exploring and with metaMeta 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. to embed a voting blockBlock 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. within the post to make it easier for voting. Thanks to @ironprogrammer on testing and helping move this option forward, which may also assist other teams in the future.

#6-4, #6-5, #agenda, #dev-chat