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
I believe that when a person is uploading or using the Custom Fonts then those Custom Fonts should be visible in the Font Family dropdown of Otter Blocks Style Settings and it will make it each for the Customer to upload and use the Font.
We can at least do it for Neve for the starters.
What is your proposed solution?
My proposed solution would be that I can understand that there are tons of themes out there and a person can upload a Custom font using different methods it can be tough or not possible for Otter Block Plugin to get those Custom Fonts and display it in the dropdown.
So we can provide the option to upload the Custom Fonts in Otter Blocks Plugin either via WP Dashboard > Otter Blocks > Settings or in the Font Family Dropdown so that Custom Fonts can be used.
Will this feature require documentation? (Optional)
None
The text was updated successfully, but these errors were encountered:
What problem does this address?
I believe that when a person is uploading or using the Custom Fonts then those Custom Fonts should be visible in the Font Family dropdown of Otter Blocks Style Settings and it will make it each for the Customer to upload and use the Font.
We can at least do it for Neve for the starters.
What is your proposed solution?
My proposed solution would be that I can understand that there are tons of themes out there and a person can upload a Custom font using different methods it can be tough or not possible for Otter Block Plugin to get those Custom Fonts and display it in the dropdown.
So we can provide the option to upload the Custom Fonts in Otter Blocks Plugin either via WP Dashboard > Otter Blocks > Settings or in the Font Family Dropdown so that Custom Fonts can be used.
Will this feature require documentation? (Optional)
None
The text was updated successfully, but these errors were encountered: