Hi Rick,

Another n00b question; I've just added FAP to my toolkit. I assume that in order to leverage it in WWHB content I just need to update my WWHB layout templates, or my WWC app templates for that matter, to point to the proper resource. Is that accurate?

<link rel="stylesheet" type="text/css" href="templates/scripts/fontawesome/css/font-awesome.min.css" />

to

<script src="https://kit.fontawesome.com/xxxxxxxxx.js" crossorigin="anonymous"></script>

TIA

The Help Builder templates use FA Pro - so you should be fine from that end.

You can copy your 'personal' version if you want into the templates folder to replace the files HB ships with (as we don't update the icons frequently).

I prefer the local copies because if you're offline you then won't see the icons while working locally.

Thanks. I'll see how I get on with this.

Hmmm... Can I get a little more specific info about files I need to copy where? And as I'm mainly generating HTML content as opposed to CHM, what would I need to push to the web help location?

TIA

Just replace the FontAwesome folder in templates/scripts/fontawesome.

Hmmm... just checked and it turns out the actual version in use is FontAwesome 4.70. So I lied about Pro version of FA. 😦

That's probably something that should be updated. Not 100% sure if just plopping in 5.x will work as the naming of stock icons has changed some. Templates have to be adjusted to point at the right version of the FA5 libraries.

+++ Rick ---

So maybe add a fontawesome5 folder and adjust refs in templates as you suggested?

The fontawesome folder structure in WWHB vs what I got from FA is a bit different.

You should only need the CSS and WebFonts folders which is what HB uses. But you'll need to update the LayoutPage template to point at the .all CSS library (or which ever other one you want to use).

+++ Rick ---