Considering the ruling detailed in the article above, it would be prudent for HubSpot to improve how theme fonts are currently handled in CMS Hub to be both more compliant with GDPR and also deliver a better user experience by self-hosting fonts as opposed to using Google-hosted versions. This would keep the marketer/content editor flexibility of the current tool, but once a font is selected, HubSpot would automatically download the font files, install them in either the file manager or design manager file system, and embed these files in the same areas currently used. This should also reduce the likelihood of flashes of unstyled content (FOUC) that currently occur while the browser is waiting to download the Google-hosted versions of the fonts.
An Adobe fonts integration would also be great using the same workflow, but could easily be a future roadmap item after fixing the current issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.