FYI - We have a problem brewing with Axure + Font Awesome.
Getting Font Awesome fonts working locally was always a bit complicated but easy once you know it well - Download & Install the Font Awesome OTFs fonts, then open Axure, and then go to fontawesome.com/icons, click the round “I” info icon in the upper right to expose the copy to clipboard icon below each icon, so you can easily copy any icon, paste into your axure wireframe, it’ll look like an empty box temporarily, then you highlight it and change the font for that box to Font Awesome, and presto, it works. Generating local prototypes would show correctly.
When you publish to share.axure.com with just that, it’d show correctly for you (since you have all the font awesome fonts installed locally and the browser can figure that out), but for others without them, they see empty boxes.
That brings us to the brewing problem I mentioned in the opening line - if you want the Font Awesome fonts to show correctly on your published prototypes that render at share.axure.com for people other than you (you know, the whole point of all this), the solution ‘currently’ is to click the blue Axure share button in the upper right, and in the Fonts tab, add a link to Font Awesome’s CDN-hosted all.css file, like this: https://pro.fontawesome.com/releases/v5.10.1/css/all.css. The problem is - Font Awesome appears to be attempting to discontinue this method. They’ve already buried the ability to even find that link deep in fontawesome.com/account/cdn, and on that page, they have a big yellow warning that this functionality is being sunset, as seen here:
I started a chat thread with a Font Awesome support rep named Trevor, asking him about the absence of css from the start page where it used to live, and after initially missing the point that having links directly to .css files is the linchpin of how we all use Font Awesome with Axure, he eventually copped to the fact that Kits only gives you a link to a js file, and once the CDN is sunset, there’ll be no way to link directly to css.
I hope someone has a solution for this, because I like FontAwesome, and I’d like to not have to discontinue using them.