Types
There are four types of icons: Outlined, Filled, Off, and Contained.
Outlined
Outlined icons are icons with a standard outline.
Use Outlined icons by default.
Filled
Filled icons are icons with a solid fill and are indicated by -fill
in the icon name.
Use Filled icons to show a toggled state or for contrast with Outlined icons.
Indicating a toggled state
For objects that can be toggled on/off, show the Outlined icon for off
and the Filled icon for on
.
Using for contrast
If contrast against other icons is important, use Filled for the more important icon(s).
For example, when showing one failure in a list of 20 otherwise successful builds, use x-square-fill
while keeping the remaining icons in the Outlined style so the failure is more prominent.
Off
Off icons are icons including a strike-through and are indicated by -off
in the icon name.
Use Off icons to indicate something is disabled, unavailable, or will return a toggled icon off
.
Indicating a disabled or unavailable icon
When needing to indicate an action is disabled or unavailable, consider pairing an Off icon with the color style Foreground/Disabled
and cursor property value not-allowed
.
Return toggled state back off
If an object is toggled on
and it can be toggled off
, consider showing the Off icon on hover to indicate that clicking the icon again will toggle the object back off
.
Contained
Contained icons are icons with a containing shape and are indicated by their shape type in the icon name, e.g., -circle
, -square
, etc.
Use contained icons for emphasis in the hierarchy.
If an object can have multiple states, use a Contained icon for the overall parent state and the Outlined icon(s) for the children’s state(s).
Animated
Animated icons are icons with an animated effect that show a transition between two states.
Use animated icons to communicate activity happening in the background. For example, when an object is updated, the loading icon could appear after the save action is triggered, indicating that the changes are in progress.
Sizes
Icons are optimized for two icon sizes: 16px
and 24px
.
Use 16px
icons by default in product interfaces and 24px
icons for empty states.
States
Icons frequently represent different states within product interfaces, most commonly as states of an object or states of feedback.
States of an object
Some objects can return a state, e.g., a Build, Run, Cluster, etc. Objects are typically displayed in lists or as cards and include their state when presented to the user.
States of feedback
Feedback is presented in response to user interaction, such as a displaying a success message after submitting a form or a warning when a user nears their usage limit.
Common icons
Some icons represent common actions within our products.
Editing actions
Navigation actions
Help actions
Use
learn-link
when linking to tutorials.Use
docs-link
when linking to documentation pages and installation guides.Use
support
when referencing HashiCorp support.
Resources
- Figma library (Internal only)
- SVG assets (ZIP file)
- Request an icon or report an issue
Installation
Icons can be used in many ways. The package can be installed as an Ember addon for the convenience of using a component with strong defaults. It can also be consumed in React applications via direct import of the SVG file or as a standalone React/SVG icon component.
Adding icons to Ember apps
Install the ember-flight-icons
addon.
yarn add @hashicorp/ember-flight-icons
Deferred loading
By default, the SVG sprite will be injected into your application's index.html
file. If you would like this to happen later as part of your app bundle you can set the lazyEmbed
flag to true
in the emberFlightIcons
object in your app's config/environment.js
file:
module.exports = function(environment) {
const ENV = {
// your other config
...
emberFlightIcons: {
lazyEmbed: true,
},
};
}
For more information on why this may be helpful in certain scenarios, see DS-049 - Improve Ember Flight Icons Loading Performance.
Adding icons to React apps
To add icons to a React application, install the @hashicorp/flight-icons
package and import the icons as either inline SVGs or as a standalone React/SVG component.
Installing the flight-icons
package
To install, run:
yarn install @hashicorp/flight-icons
Importing icons as inline SVGs
Single icons can be imported and used directly as SVG files using <InlineSvg> provided by @hashicorp/react-components.
Since this is just an SVG asset, no props can be passed. You should refer to the <InlineSvg> documentation to know how to apply color and size to the SVG icon.
// import the SVG file (using 'require')
const iconArrowRight = require('@hashicorp/flight-icons/svg/arrow-right-24.svg?include');
// or import the SVG file (using 'import')
import iconArrowRight from '@hashicorp/flight-icons/svg/arrow-right-24.svg?include';
// elsewhere in the file
<InlineSvg src={iconArrowRight} />
// alternatively you can also use a similar approach
<InlineSvg src={require('@hashicorp/flight-icons/svg/arrow-right-24.svg?include')} />
Importing icons as React/SVG components
Single icons can be imported and used directly as standalone React/SVG components:
// import the React/TypeScript file (using 'require')
const { IconArrowRight24 } = require('@hashicorp/flight-icons/svg-react/arrow-right-24');
// or import the React/TypeScript file (using 'import')
import { IconArrowRight24 } from '@hashicorp/flight-icons/svg-react/arrow-right-24';
// elsewhere in the file
<IconArrowRight24 />
How to use icons
The most basic invocation requires only the @name
property to be passed with a value matching an existing name in the Icon library.
<FlightIcon @name="alert-circle" />
It renders to this (where the id
will be unique each time):
<svg
id="icon-ember115"
class="flight-icon icon-alert-circle display-inline"
width="16"
height="16"
viewBox="0 0 16 16"
xmlns="http://www.w3.org/2000/svg"
fill="currentColor"
aria-hidden="true"
data-test-icon="alert-circle"
>
<use href="/@hashicorp/ember-flight-icons/icons/sprite.svg#alert-circle-16"></use>
</svg>
Because the icons are hidden to assistive technology, they cannot be used on their own and must be used inside of an element with an accessible name.
The Hds::Button component automatically provides this support, but if you make a custom element, or want to use a FlightIcon
inside of a native HTML element like your own button element, ensure that an aria-label
attribute is added, like this:
<button type="button" aria-label="add a new thing">
<FlightIcon @name="plus" />
</button>
Color
The default value is currentColor
which uses the inherited text color as the icon color. When setting a custom value, we recommend using one of the pre-defined variables to ensure consistency with our design language:
<FlightIcon @name="zap" @color="var(--brand)" />
Other accepted values include named colors and color values themselves (e.g., hex, rgb, etc).
<FlightIcon @name="zap" @color="rebeccapurple" />
<FlightIcon @name="zap" @color="rgb(46, 113, 229)" />
Size
The default size is 16px. To use the alternative 24px icon size, set the @size
value:
<FlightIcon @name="zap" @size="24" />
Stretched
To have the icon fill the parent container (width: 100%, height: 100%, display: block), set the @stretched
attribute to true:
<div class="doc-icon-demo--constrain-max-width">
<FlightIcon @name="zap" @size="24" @stretched= />
</div>
isInlineBlock
To change the default display from inline-block
to block
, set @isInlineBlock
to false:
<FlightIcon @name="triangle" @isInlineBlock= />
<FlightIcon @name="triangle-fill" @isInlineBlock= />
Aligning icons
Since the FlightIcon
component has an inline-block
display value by default (changeable using the @isInlineBlock
argument), this means that the icon behaves like an inline element. So, if you want to vertically align it in relation to other sibling elements, you will have to use CSS to achieve the expected result.
For example, to visually center an icon with a generic text node, you will need to use a parent flex
container with align-items: center
.
Animated icons
In Ember apps
Animated icons (e.g., "loading" and "running") are animated by default, meaning no additional properties are needed.
<FlightIcon @name="loading" @size="24" />
In React apps
To use the icons which are meant to be animated (e.g., “loading” and “running”), import the CSS that controls the icons’ animation:
// the path here depends if you’re using 'svg-react' or 'svg' icons
@import ~@hashicorp/flight-icons/svg-react/animation.css';
Then declare them the same way you would with any other icon.
// if you’re using the 'svg-react' icons
import { IconLoading16 } from '@hashicorp/flight-icons/svg-react/loading-16'
<IconLoading16 />
// if you’re using the 'svg' icons
import svgLoading16 from '@hashicorp/flight-icons/svg/loading-16.svg?include'
<InlineSvg src={svgLoading16} />
Component API
name
string
color
string
- currentColor (default)
@color
argument can be used to change the color. It works by setting the value of the icon SVG’s fill
property.
size
number
- 16 (default)
- 24
stretched
boolean
- false (default)
true
will make the icon have a height and width of 100% and a display of block
.
isInlineBlock
boolean
- true (default)
display
style for the icon. Setting it to false
will make the icon have a display of block
.
title
string
aria-hidden
value to false
instead of the default value of true
.
Conformance rating
When used as recommended, there should not be any accessibility issues with this component.
Browser accessibility support
Accessibility support for SVGs is inconsistent across browsers and assistive technology. Currently, the best practice is to set the aria-hidden
attribute to true
on the SVG itself (as we do by default for the FlightIcon
component). This means that the icon (both the singular icon and the icon component) will need to be used in context. The icons themselves are for presentation purposes only and should never be used on their own.
However, as a temporary bridge, while we work to provide the accessible components in the design system, we have provided the ability to add a title element to the Ember component by defining a value for the @title
property. This is a temporary measure, and we strongly encourage UI engineering teams to work with their designers and plan to convert any standalone icon use.
Examples of correct use
<button aria-label="Check activity">
<FlightIcon @name="activity" />
</button>
<h2>
Activity report <FlightIcon @name="activity" />
</h2>