The catch with that approach is that openjs can't parse the font when it comes through as a 'ConfigurationPage' from my plugin. If I could figure out how to tell Plugin.cs to provide the font in the same way as the server provides: "localhost:8096/web/modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmJ_1.woff?v=4.5.4.0" (attachment, content-type 'font/woff', etc.) I'd be in business. From what I'm seeing, 'configurationpage=' can figure out that a javascript file is 'appl