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
WIth great power comes great responsibility. The editor Fonts Library is a powerful feature. It puts fonts management entirely in the hands of users, whether they are agencies/professionals who manage websites for their customers or non-tech savvy users who manage their own website.
This is a significant shift from a site creation flow where typography was always a responsibility of professionals theme authors, who supposedly had at least some typography best practices knowledge, to a flow where users who may not necessarily have such knowledge can manage their website fonts.
Usrs with no great knowledge may not be able to follow best practices and end up by choosing font faces that aren't ideal for readability, usability, and accessibility. WordPress gives them such a power but, on the other hand, it doesn't do anything to guide users in making the best choices. There's potential to make the web worse, instead of making it better.
What is your proposed solution?
I'd think WordPress should educate users and guide them to follow at least some basic typography best practices.
The Fonts Library should link to a short documentation on Make.org with some basic typography principles. This documentation should not pretend to be a complete guide to typography. It would be good to point to some few, basic principles though and include links to good, authoritative resources for more details.
So far, the only guidance in the UI warns to not install too many font variants because they 'could make your site slower.' While that is true, users should also be educated that they should not use too many fonts for better readability of an overall web page.
Some of the basic guidelines may include:
LImit the amount of font faces used on a page to a reasonable number to not impact readability.
Prefer sans-serif fonts for the body text.
Explain the different usage between sans-serif and serif fonts.
Avoid handwriting font faces.
More basic best practices from people more expert in typography than me.
The text was updated successfully, but these errors were encountered:
What problem does this address?
WIth great power comes great responsibility. The editor Fonts Library is a powerful feature. It puts fonts management entirely in the hands of users, whether they are agencies/professionals who manage websites for their customers or non-tech savvy users who manage their own website.
This is a significant shift from a site creation flow where typography was always a responsibility of professionals theme authors, who supposedly had at least some typography best practices knowledge, to a flow where users who may not necessarily have such knowledge can manage their website fonts.
Usrs with no great knowledge may not be able to follow best practices and end up by choosing font faces that aren't ideal for readability, usability, and accessibility. WordPress gives them such a power but, on the other hand, it doesn't do anything to guide users in making the best choices. There's potential to make the web worse, instead of making it better.
What is your proposed solution?
I'd think WordPress should educate users and guide them to follow at least some basic typography best practices.
The Fonts Library should link to a short documentation on Make.org with some basic typography principles. This documentation should not pretend to be a complete guide to typography. It would be good to point to some few, basic principles though and include links to good, authoritative resources for more details.
So far, the only guidance in the UI warns to not install too many font variants because they 'could make your site slower.' While that is true, users should also be educated that they should not use too many fonts for better readability of an overall web page.
Some of the basic guidelines may include:
The text was updated successfully, but these errors were encountered: