It appears Typekit doesn't like serving fonts on the mesaaz.gov site:
For now, we can make a new font kit that is set to display on the mesaaz.gov site and deploy that.
Ultimately, a better fix may be to not use Typekit (we use it so we can have the Proxima Nova typeface, but I really like Adobe's Source Sans Pro typeface and am thinking we should just switch to that anyway so there is one less third party paid dependency).
Either that, or we should move the Typekit config into the config area and document that dependency.
techieshark
commented
7 years ago
It appears Typekit doesn't like serving fonts on the mesaaz.gov site:
For now, we can make a new font kit that is set to display on the mesaaz.gov site and deploy that.
Ultimately, a better fix may be to not use Typekit (we use it so we can have the Proxima Nova typeface, but I really like Adobe's Source Sans Pro typeface and am thinking we should just switch to that anyway so there is one less third party paid dependency).
Either that, or we should move the Typekit config into the config area and document that dependency.