Discourse FontAwesome Pro

:discourse2: Summary Discourse FontAwesome Pro allows the use of Font Awesome Pro icons in Discourse with a FontAwesome license by using your account’s NPM package token.
:hammer_and_wrench: Repository Link https://github.com/discourse/discourse-fontawesome-pro
:open_book: Install Guide How to install plugins in Discourse

Configuration

This requires a few extra step to enable from a normal plugin:

First, you will need to set up an additional env var containing your font awesome pro license key: DISCOURSE_FONTAWESOME_AUTH_TOKEN

The install script also needs to be called during initialization, as an additional “after_code” hook. This downloads and adds the FontAwesome Pro SVGs on build using your auth token. This is an additional block separate from the plugin clone block.

Here is an example install in app.yml :

env:
  DISCOURSE_FONTAWESOME_AUTH_TOKEN: 123456
  
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/discourse-fontawesome-pro.git
    - exec:
        cd: $home/plugins/discourse-fontawesome-pro
        raise_on_fail: false
        cmd:
          - $home/plugins/discourse-fontawesome-pro/scripts/install.sh

Picking an override family:

In the admin settings, you can override the default Discourse icon family:

Picking an override style:

You can also override the default icon style:

Duotone

To take full control of duotone support, you will be looking to override the following CSS (in a theme, or otherwise) and replace it with your own color scheme:

svg {
  --fa-secondary-color: red;
  --fa-secondary-opacity: 0.6;
}

To color individual icons reference the SVG’s ID:

#fad-search .fa-secondary {
  --fa-secondary-color: red;
  --fa-secondary-opacity: 0.6;
}

:warning: Duotone Styling Update
If you’re using class-based selectors like:

.fa-secondary { color: red; }

You’ll need to update your styling to use CSS custom properties instead. Class-based color overrides no longer work since they were dropped in Font Awesome v7


Under the hood, this is using FontAwesome’s repository to install fonts to the plugin’s SVG folder, and lets Discourse pick up the sprites from there.

:discourse2: Hosted by us? This plugin is available on our Enterprise plans.

Last edited by @Juan_David_Martínez 2025-10-29T16:14:49Z

Check documentPerform check on document:
36 „Gefällt mir“

@featheredtoast I haven’t had a chance to check but does this downloads the most recent version of fontawesome pro, like 6.x?

There was a workaround mentioned here:

Does the latest version already support FA6 pro? @featheredtoast

I’m afraid it doesn’t as yet. I think this is still the case:

3 „Gefällt mir“

For anyone wondering, this still doesn’t work with v6, even with the latest core supporting it, you still need to use --branch fa5 to get the pro icons to work.

3 „Gefällt mir“

Is this plugin still maintained? I am curious if we could use FA(6) pro icons at this point

It does need some tidying up - it’s on the list, we’re working through it - Pardon the dust.

2 „Gefällt mir“

Hi everyone, I have updated this plugin to work with FontAwesome v7 I will be updating the docs shortly

6 „Gefällt mir“

Is it possible that the regular style not applied correcty in the plugin settings? Checking Find Icons with the Perfect Look & Feel | Font Awesome , the regular style FA icons are all hollow but on my site the when I apply regular icon style, my icons still remain filled and regular mode

2 „Gefällt mir“

Thanks for reporting, the fix is already merged. Let me know if you encounter any other issues

2 „Gefällt mir“

Hi Juan,
Is this by chance related?

1 „Gefällt mir“

Anyone else having an issue with “d-icon-d-watching-first” icon not working when the plugin is enabled?
Tested on 3.6.0.beta2 with settings:
Fa icon style set to regular
Fa icon family set to classic

1 „Gefällt mir“

Oh, nice catch. I’ve just updated the plugin so that it will show the proper icon again.

2 „Gefällt mir“