Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Font Library post-WP 6.5 Issues #60528

Open
14 of 65 tasks
creativecoder opened this issue Apr 6, 2024 · 9 comments
Open
14 of 65 tasks

Font Library post-WP 6.5 Issues #60528

creativecoder opened this issue Apr 6, 2024 · 9 comments
Labels
[Feature] Font Library [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@creativecoder
Copy link
Contributor

creativecoder commented Apr 6, 2024

This is a collection of open Font Library bugs and enhancements to be considered for WP 6.6, grouped by category, with bugs at the top of each category:

UI Improvements

Accessibility

Collections and installing fonts

Managing installed fonts

Storage and data

Font files

Font post types

REST API

Font Collections

Google Fonts collection

All collections

Font Names and Previews

System Fonts

Relation to Global Styles and Themes

Related Typography Issues

Importing/Exporting

Code Quality

Misc

@creativecoder creativecoder added [Type] Iteration Scoped iteration of an effort from a tracking issue or overview issue ideally for a major release. [Feature] Font Library labels Apr 6, 2024
@afercia
Copy link
Contributor

afercia commented Apr 11, 2024

@creativecoder can we add #55179 to this list please? Thanks.

@creativecoder
Copy link
Contributor Author

@creativecoder can we add #55179 to this list please? Thanks.

@afercia I've added it to the list.

@annezazu
Copy link
Contributor

Can someone provide an update on where this work is with 6.6 beta 1 coming up? Curious what improvements we might see for the release and where we are with these efforts.

@creativecoder
Copy link
Contributor Author

@annezazu I believe the checklist in the issue description is up to date. It looks like we have a few small improvements:

Additionally, there's some in progress work on https://core.trac.wordpress.org/ticket/60835 to improve the underlying code.

That's all I'm aware of, right now.

@fabiankaegy
Copy link
Member

Hi all 👋

Reminder: The release candidate for Gutenberg Version 18.5 is scheduled for next Friday (May 31st). So anything that is supposed to make it into WordPress 6.6 must be merged by then.

Please raise any important issues that need additional attention :)

@creativecoder creativecoder added [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. and removed [Type] Iteration Scoped iteration of an effort from a tracking issue or overview issue ideally for a major release. labels Jul 12, 2024
@creativecoder
Copy link
Contributor Author

I've updated the labels on this issue to be a Tracking Issue (rather than Iteration). At this point the issue description is more a collection of categorized font library issues than a scoped set of issues for a specific iteration.

I've also combed through Gutenberg and Trac and added additional font library issues I found to the description.

@luminuu
Copy link
Member

luminuu commented Jul 26, 2024

@creativecoder I've been stumbling upon this request again, is there a reason why it's not included in this list? #55239

@creativecoder
Copy link
Contributor Author

@luminuu I still think Adobe/Typekit support is best done with a separate plugin, as I don't see any way to download or use Adobe fonts without signing up for an account, and many of the fonts seem to require a paid subscription.

But if their licensing allows free downloading and use without an account, and there's an API we can use to generate a font collection (see the google fonts collection scripts for reference), please let me know!

@luminuu
Copy link
Member

luminuu commented Aug 1, 2024

I have a licensed link available for testing and I tried to add these fonts as a font collection but I didn't got it working. It would be nice if there would be some possbility, apart from a very hacky way that I found. What technically happens is you get a link to a .css file which contains the @font-face declarations. I'd imagine the editor to load that CSS file and via the font collection, you can define the fonts, weights etc so they correctly appear in the editor. Ideally these fonts would show up the same way in the design tools and font library, just coming from a different source. This way could be used for other font providers as well, as long as you have a .css file that contains the fonts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Font Library [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
No open projects
Status: 📋 Iteration/Tracking Issues
Development

No branches or pull requests

5 participants