We've been looking into having an external CDN URL for the fonts.
One problem with the icons is they're SVG and for both IE and a certain set of older webkit-based Android browsers we still support, the SVGs have to be placed on the page they're used. That can be done manually to your HTML page but if you use the Javascript (mentioned in Elements on the Icons page), you would have to change that URL to the CDN.
Which is doable, but I was hoping for a way to have that JS be able to grab the svg sprite file even if it doesn't exactly know its name or the full path.
Also currently both the fonts and svgs are fingerprinted-- we'll likely get rid of fingerprinting for the fonts, they're very unlikely to change much. So in our Jira we do have a story for getting rid of that and because it's gulp we figured we'd might as well move Elements over the webpack 2 as well (so everything uses the same tech stack).
We've been looking into having an external CDN URL for the fonts.
One problem with the icons is they're SVG and for both IE and a certain set of older webkit-based Android browsers we still support, the SVGs have to be placed on the page they're used. That can be done manually to your HTML page but if you use the Javascript (mentioned in Elements on the Icons page), you would have to change that URL to the CDN.
Which is doable, but I was hoping for a way to have that JS be able to grab the svg sprite file even if it doesn't exactly know its name or the full path.
Also currently both the fonts and svgs are fingerprinted-- we'll likely get rid of fingerprinting for the fonts, they're very unlikely to change much. So in our Jira we do have a story for getting rid of that and because it's gulp we figured we'd might as well move Elements over the webpack 2 as well (so everything uses the same tech stack).
I'll tag this issue number to that ticket, it's a good idea. https://agile-jira.pearson.com/browse/DES-216