You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Font Library project (#54169) introduces a powerful REST API for seamlessly installing new Font Families and Font Faces, enhancing the website's typographic options.
On the front end, you can only install these fonts using the REST API. However, it might be helpful to have a dedicated PHP API for a smoother installation process on the backend side.
The text was updated successfully, but these errors were encountered:
gigitux
changed the title
Font Library: Add PHP API to allow the install Font Families and Font Faces on the PHP side
Font Library: Add PHP API to allow the installation of Font Families and Font Faces on the PHP side
Feb 5, 2024
gigitux
changed the title
Font Library: Add PHP API to allow the installation of Font Families and Font Faces on the PHP side
Font Library: Add PHP APIs to allow the installation of Font Families and Font Faces on the PHP side
Feb 5, 2024
However, I'm not sure how we would identify the font faces right now. Maybe an array that contains a list of properties to match font faces, if they are present in the collection, i.e.
However, this has subtleties we'd need to consider, like does bold match only a numeric font weight value of 700, or would it just look for something heavier than 400?
Alternatively, we could introduce font face slugs to collections in some way, so that there's an easy way to reference which font faces should be installed.
What problem does this address?
The Font Library project (#54169) introduces a powerful REST API for seamlessly installing new Font Families and Font Faces, enhancing the website's typographic options.
On the front end, you can only install these fonts using the REST API. However, it might be helpful to have a dedicated PHP API for a smoother installation process on the backend side.
The text was updated successfully, but these errors were encountered: