Tonya Mork

@simison There are 2 more blocking architectural PRs, one of which will rename the entire API and all of its code. A status update is here https://github.com/WordPress/gutenberg/issues/41479#issuecomment-1357603504.

@simison This issue is now unblocked. Please note, the API has been completely redesigned including a brand new architecture and renamed to Fonts API (including all of the public function...

Some notes to help: - I closed PR #46404. Why? Its implementation applied to the old API but will not work in the new Fonts API. - A PR will...

Update: This issue no longer applies to the Fonts API once the Font Library is merged. I believe this issue can be closed as the "name" attribute is supported in...

Thank you, Nick. You are correct. If you want to automatically generate the theme's `.pot` using one of the existing tools on the market, then using a variable or constant...

Thanks, Nick. That's awesome you ran the test with Poedit for me. Thank you so much! I really appreciate you taking the time and digging into it. Yes, I was...

Right now, the information is held in a separate and distinct container. @Mte90 Would you find that container to be more useful to you if it's integrated into Query Monitor?...

Hey contributors 👋 I'd like to ask that each backport: * be built in smaller PR increments, one thing in a PR * open a new Core Trac ticket for...

Backport for `wp_theme_has_theme_json()` (which includes deprecating `WP_Theme_JSON_Resolver::theme_has_support()`): - PR 3556 https://github.com/WordPress/wordpress-develop/pull/3556 - Trac ticket 56975 https://core.trac.wordpress.org/ticket/56975 Update Jan 18, 2023: This [backport was committed](https://core.trac.wordpress.org/changeset/55086.) today and Trac ticket closed ✅

(Web) Fonts API: I grouped those files together for tracking purposes and self-assigned. Status: This API is still in development and is not yet ready to backport to Core.