Once you get Sass up and running in your project, make sure to configure Sass to
include node_modules in its includePaths option. For more information,
checkout the configuration section in our Sass
docs.
There are various helpers that you can include from Carbon, as well, such as a
CSS reset, grid, breakpoint helpers, and more. You can include these similar to
how you bring in components:
// Bring in the CSS Reset@use'@carbon/styles/scss/reset';
// Bring in the CSS Grid@use'@carbon/styles/scss/grid';
To learn more about the various helpers that @carbon/styles provides, checkout
the overview of the files available to use in our
Sass docs.
Carbon is designed, tested, and tuned for IBM Plex. We do not recommend
replacing the Carbon typeface. If you absolutely need to use a different
typeface, you'll need to treat it as a build-time Sass customization that your
application owns. There is no support for runtime typeface overrides on
prebuilt/CDN Carbon styles.
Use at your own risk
Overriding the Carbon typeface has broad design and accessibility
implications. Carbon type styles are tuned with IBM Plex metrics in mind,
including line heights, letter spacing, weight, glyph proportions, ligatures,
and fallback behavior. A replacement typeface can change layout, wrapping,
density, readability, and interaction states. It can be a significant design
and engineering effort to make another typeface work correctly across an
application.
To use Carbon with a different typeface, three things are needed:
Turn off Carbon's Plex @font-face generation
Change the root font-family definition(s)
Supply your own @font-face rules
You can accomplish the first two by configuring the Sass entrypoint that your
application compiles. This configuration must happen before any other @use of
Carbon Sass modules.
@use'sass:string';
@use'@carbon/styles' with (
// Turn off Carbon's Plex `@font-face` generation
$css--font-face: false,
// Change the root `font-family` definition(s)
$font-families:
(
'sans':
string.unquote(
"'Inter Local', system-ui, -apple-system, BlinkMacSystemFont, '.SFNSText-Regular', sans-serif"
),
'mono':
string.unquote(
"'IBM Plex Mono', system-ui, -apple-system, BlinkMacSystemFont, '.SFNSText-Regular', monospace"
),
'serif':
string.unquote(
"'IBM Plex Serif', system-ui, -apple-system, BlinkMacSystemFont, '.SFNSText-Regular', serif"
),
// Include any other Carbon font family keys your application compiles.
)
);
$font-families is not merged with Carbon's defaults. If you configure this
map, include every family key your compiled styles need, such as sans, mono,
serif, or any additional language-specific Plex stacks used by your
application.
Then, supply your own @font-face rules to load your replacement font assets.
Only load the weights, styles, and Unicode ranges that your application needs,
but make sure they cover the font weights and styles your Carbon usage emits. If
you use a third-party font service, review its privacy and regional compliance
implications carefully, including whether font requests expose user data in ways
your application cannot accept.
You can change the default theme of Carbon by doing the following:
@use'@carbon/styles/scss/themes';
@use'@carbon/styles/scss/theme' with (
$theme: themes.$g100
);
This example uses a built-in theme from Carbon provided by the scss/themes
entrypoint. You can also use a custom theme, or add your own custom tokens to
extend the theme.
// Configure with a custom theme@use'@carbon/styles/scss/theme' with (
$theme: (
background: #e2e2e2,
text-primary: #ffffff,
)
);
// Extend the g100 theme with your own tokens@use'@carbon/styles/scss/themes';
@use'@carbon/styles/scss/theme' with (
$fallback: themes.$g100,
$theme: (
custom-token-01: #000000,
)
);
You can access the design tokens defined by the Carbon Design System through the
@carbon/styles/scss/theme entrypoint. This file will allow you to refer to
tokens using Sass Variables as well as get the current value for any token in
the current theme. For example:
@use'@carbon/styles/scss/theme';
body {
background: theme.$background;
}
For a full list of tokens available for you to use, check out our
theming documentation.
We're always looking for contributors to help us fix bugs, build new features,
or help us improve the project documentation. If you're interested, definitely
check out our Contributing Guide!
This package uses IBM Telemetry to collect de-identified and anonymized metrics
data. By installing this package as a dependency you are agreeing to telemetry
collection. To opt out, see
Opting out of IBM Telemetry data collection.
For more information on the data being collected, please see the
IBM Telemetry documentation.