Skip to main content

Added support for self-hosted Font Awesome assets

What components does this change affect?

This change affects implementations of the Design System that use Font Awesome icons.

What changed

Added support for self-hosted Font Awesome assets as an alternative to using the externally hosted Font Awesome Kit.

Consuming applications can choose to use either the external Font Awesome Kit or self-hosted Font Awesome assets. The Font Awesome option is configured in Program.cs.

Before: 

services.AddTurasDesignSystem(options => 
{ 
    options.FontAwesomeKitId = "your-kit-id"; 
     
    options.SkipAutoInjectForPaths = new List<string> 
    { 
        "/customerrors", 
    }; 
});

After (to use self-hosted assets):

services.AddTurasDesignSystem(options => 
{ 
    // Remove the FontAwesomeKitId line to use self-hosted assets
     
    options.SkipAutoInjectForPaths = new List<string> 
    { 
        "/customerrors", 
    }; 
});

Removing the FontAwesomeKitId line configures the application to use the self-hosted Font Awesome assets.

Important: Teams wishing to use the self-hosted option must obtain a Font Awesome asset package from the Design System team. This is required for licensing purposes and allows Font Awesome usage to be tracked appropriately.

Why this change was made

This change provides a more resilient way of loading Font Awesome icons by allowing consuming applications to use self-hosted assets rather than relying on an externally hosted service.

Benefits include:

  • greater resilience – reduces reliance on externally hosted Font Awesome services
  • improved availability – icons can continue to be loaded when the external Font Awesome service is unavailable
  • greater flexibility – allows consuming applications to choose how Font Awesome assets are delivered

Note: The self-hosted Font Awesome asset package contains a reduced number of fonts and font weight options compared with the external kit. Teams choosing the self-hosted option should check their application's icons after switching. No fonts previously displayed on the Design System have been removed from the self-hosted package.

Recommended checks for consuming teams

After updating your Design System packages, we recommend reviewing Font Awesome usage in your application:

  • Font Awesome icons display correctly
  • existing icon usage and styling remain consistent
  • no unexpected console errors are introduced
  • any application-specific Font Awesome configuration continues to work as expected

Summary

This change adds support for self-hosted Font Awesome assets as an alternative to the externally hosted Font Awesome Kit.

Teams choosing the self-hosted option should review their application's Font Awesome usage to ensure icons continue to display as expected.

Internal reference

Design System internal reference: 87259

Was this page helpful?