[wp-trac] [WordPress Trac] #46370: A proposal for creating an API to register and enqueue web fonts

[WordPress Trac]

#46370: A proposal for creating an API to register and enqueue web fonts
-------------------------------------------------+-------------------------
 Reporter:  jonoaldersonwp                       |       Owner:
                                                 |  hellofromTonya
     Type:  feature request                      |      Status:  assigned
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests needs-dev-  |     Focuses:
  note                                           |  performance, privacy
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * keywords:  has-patch has-unit-tests needs-dev-note commit => has-patch
     has-unit-tests needs-dev-note
 * milestone:  5.9 => Future Release


Comment:

 Hello everyone,

 Thank you for contributions and support of the Webfonts API. A lot of work
 went into getting to its current state.

 The collaboration and review process has been significant, especially in
 such an accelerated timeframe. It has good support including at least 4
 Core Committers. But there are open questions and
 [https://github.com/WordPress/wordpress-develop/pull/1736#issuecomment-
 964540170a a Lead Dev has raised the red flag].

 Whether we agree or disagree, this is an opportunity to think about the
 best way forward for this API and web fonts in Core.

 As @azaozz noted, Core currently does not use this API. ''But what if it
 did?''

 @aristath shared a [https://github.com/WordPress/wordpress-
 develop/pull/1736#issuecomment-963893355 list of features and improvement
 initiatives] for Gutenberg and block themes. That's the bigger picture of
 the next steps for web fonts. A big driver to get into 5.9 was to support
 these initiatives.

 === Move it Gutenberg First Proposal

 What if it were in Gutenberg first?

 Then the list could be built onto of it. Think about it.

 Being in Gutenberg as part of building the list can mean:

 * Gets used in the editor and by `theme.json` experimentations
 * Changes don't need to support backwards-compatibility (until it merges
 into Core)
 * Changes can ebb and flow faster to support the features
 * Gains experimentation, learning, feedback, live testing, and lots of
 eyes on it
 * Proves itself by being a foundational piece of these features and
 improvements
 * Matures in the Gutenberg workflow process to become more robust,
 reliable, and stable

 When each thing on the list is merged into Core, so is the API. Welcome to
 Core.

 === The Next Step Forward

 Today is 5.9 Feature Freeze. The API brings a lot of new code. It can
 benefit from more feedback (especially from theme developers) and actual
 usage. It needs real world examples.

 Given the concerns raised combined with the advantages of being part of
 the new features and improvements in Gutenberg, I'm punting it to a
 `Future Release` and advocating to move it to Gutenberg. Time ran out in
 this cycle.

 Core needs this API for all the reasons laid out in the PR and the
 proposal. Let's take the time to vet it and ensure it's ready to deliver
 on its potential.

 Punting today is not an end; it's another step forward towards web fonts
 coming to Core.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/46370#comment:111>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform