#64564 closed enhancement (fixed)
Update Google Fonts collection for 7.0 release
| Reported by: | wildworks | Owned by: | wildworks |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.0 |
| Component: | General | Version: | |
| Severity: | normal | Keywords: | has-patch has-unit-tests |
| Cc: | Focuses: |
Description (last modified by )
Related past tickets:
The current Google font collection data is not up-to-date, with the latest additions to the list of available fonts and the latest versions of the existing ones.
This ticket is the central ticket for updating Google Fonts in the 7.0 release.
From my understanding, the tasks should be performed in the following order:
- Get a Google Fonts API key.
- Clone google-fonts-to-wordpress-collection repo locally, update fonts, and submit a PR with the latest fonts. Example of past PRs:
- After the PR is merged, submit a meta ticket to have the font list hosted. Example of previous meta tickets:
- WARNING: To avoid priming the w.org CDN with failing requests, do not begin this step until after the meta tasks have been completed. After the new font is hosted, update the core code with the new URL. Example of past PRs:
cc @mmaattiiaass @peterwilsoncc @mikachan @dd32
Change History (16)
#3
@
7 months ago
- Clone google-fonts-to-wordpress-collection repo locally, update fonts, and submit a PR with the latest fonts. Example of past PRs:
The PR is ready for review: https://github.com/WordPress/google-fonts-to-wordpress-collection/pull/51
This ticket was mentioned in PR #10877 on WordPress/wordpress-develop by @wildworks.
7 months ago
#4
- Keywords has-patch has-unit-tests added
Trac ticket: https://core.trac.wordpress.org/ticket/64564
#5
@
7 months ago
Sorry, PR #10877 was linked to this ticket by mistake.
#6
@
7 months ago
- Clone google-fonts-to-wordpress-collection repo locally, update fonts, and submit a PR with the latest fonts. Example of past PRs:
The PR is ready for review: https://github.com/WordPress/google-fonts-to-wordpress-collection/pull/51
This PR has been merged.
- After the PR is merged, submit a meta ticket to have the font list hosted. Example of previous meta tickets:
Meta ticket: https://meta.trac.wordpress.org/ticket/8172
This ticket was mentioned in PR #10891 on WordPress/wordpress-develop by @wildworks.
7 months ago
#8
Trac ticket: https://core.trac.wordpress.org/ticket/64564
## Use of AI Tools
This PR does not contain any AI-generated code.
### Testing Instructions
- Access Appearance > Editor > Global Styles > TYpography section > Manage fonts button
- Move to the "Install fonts" tab
- Make sure font previews are displayed correctly.
- Test installing and uninstalling fonts.
- Apply the installed fonts to the block and verify that they are applied correctly.
- In particular, test newly added fonts.
You can find newly added fonts here: https://github.com/WordPress/google-fonts-to-wordpress-collection/pull/51#:~:text=What%20new%20fonts%20will%20be%20added%3F
#9
@
7 months ago
Thanks @dd32!
The final step:
- WARNING: To avoid priming the w.org CDN with failing requests, do not begin this step until after the meta tasks have been completed. After the new font is hosted, update the core code with the new URL. Example of past PRs:
#10
@
7 months ago
- Keywords commit added
I've reviewed, tested and approved the linked pull request. This is good ready for committing.
@wildworks commented on PR #10891:
7 months ago
#11
@peterwilsoncc Thanks for the review!
@wildworks commented on PR #10877:
7 months ago
#13
Oh, I re-forked the wordpress-develop repo and it seems all my submitted open PRs were closed 😂 I submitted a new PR that is equivalent to this one. https://github.com/WordPress/wordpress-develop/pull/10922
#14
@
6 months ago
- Keywords add-to-field-guide needs-dev-note added
This is worth mentioning in the Field Guide.
Also adding needs-dev-note just in case we can mention it in a more general note.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
@wildworks As the API uses the WordPress.org CDN, the meta ticket and commit will need to be completed before the PR for WordPress-Develop is created. This will ensure the CDN isn't primed with 404 responses.
I'll take the liberty of editing your description accordingly.