Sass
Utilize CoreUI source Sass files to take advantage of variables, maps, mixins, and functions to help you build faster and customize your project.
File structure
Whenever possible, avoid modifying CoreUI core files. For Sass, that means creating your own stylesheet that importsCoreUI for Bootstrap so you can modify and extend it. Assuming you're using a package manager like npm, you'll have afile structure that looks like this:
your-project/├── ...├── node_modules/│ ├── @coreui/coreui│ │ ├── scss│ │ └── ...│ └── @coreui/angular│ └── ...├── src│ └── scss│ ├── _custom.scss│ ├── ...│ ├── _variables.scss│ └── styles.scss└── ...
If you've downloaded our source files and aren't using a package manager, you'll want to manually create somethingsimilar to that structure, keeping CoreUI source files separate from your own.
your-project/├── scss│ └── custom.scss└── @coreui/coreui/ ├── js └── scss
Importing
In yourcustom.scss
, you'll import CoreUI source Sass files. You have two options: include all of CoreUI, or pickthe parts you need. We encourage the latter, though be aware there are some requirements and dependencies across ourcomponents. You also will need to include some JavaScript for our plugins.
Heads up!
Since@coreui/coreui
v5.3.0 and@coreui/coreui-pro
v5.10.0, we support Sass modules.
You can now use the modern@use
and@forward
rules instead of@import
, which is deprecated and will be removed in Dart Sass 3.0.0. Using@import
will result in a compilation warning. You can learn more about this transitionhere.
// Custom.scss// Option A: Include all of CoreUI@use "@coreui/coreui/scss/coreui";// Then add additional custom code here
// Custom.scss// Option B: Include parts of CoreUI// 1. Include@use "@coreui/coreui/scss/root";// 2. Optionally include any other parts as needed@use "@coreui/coreui/scss/utilities";@use "@coreui/coreui/scss/reboot";@use "@coreui/coreui/scss/type";@use "@coreui/coreui/scss/images";@use "@coreui/coreui/scss/containers";@use "@coreui/coreui/scss/grid";@use "@coreui/coreui/scss/helpers";// 3. Optionally include utilities API last to generate classes based on the Sass map in `_utilities.scss`@use "@coreui/coreui/scss/utilities/api";// 4. Add additional custom code here
Sass@import
are deprecated and will be removed in Dart Sass 3.0.0.!
You can also use@import
rules, but please be aware that they are deprecated and will be removed in Dart Sass 3.0.0, resulting in a compilation warning. You can learn more about this deprecationhere.
// Custom.scss// Option A: Include all of CoreUI@import "@coreui/coreui/scss/coreui";// Then add additional custom code here
// Custom.scss// Option B: Include parts of CoreUI// 1. Include functions first (so you can manipulate colors, SVGs, calc, etc)@import "@coreui/coreui/scss/functions";// 2. Include any default variable overrides here// 3. Include remainder of required CoreUI stylesheets@import "@coreui/coreui/scss/variables";// 4. Include any default map overrides here// 5. Include remainder of required parts@import "@coreui/coreui/scss/maps";@import "@coreui/coreui/scss/mixins";@import "@coreui/coreui/scss/root";// 6. Optionally include any other parts as needed@import "@coreui/coreui/scss/utilities";@import "@coreui/coreui/scss/reboot";@import "@coreui/coreui/scss/type";@import "@coreui/coreui/scss/images";@import "@coreui/coreui/scss/containers";@import "@coreui/coreui/scss/grid";@import "@coreui/coreui/scss/helpers";// 7. Optionally include utilities API last to generate classes based on the Sass map in `_utilities.scss`@import "@coreui/coreui/scss/utilities/api";// 8. Add additional custom code here
With that setup in place, you can begin to modify any of the Sass variables and maps in yourcustom.scss
. You canalso start to add parts of CoreUI for Bootstrap under theOptional
section as needed. We suggest using the fullimport stack from ourcoreui.scss
file as your starting point.
Variable defaults
Every Sass variable in CoreUI for Bootstrap includes the!default
flag allowing you to override the variable's default value in your own Sass without modifying CoreUI's source code. Copy and paste variables as needed, modify their values, and remove the!default
flag. If a variable has already been assigned, then it won't be re-assigned by the default values in Bootstrap.
You will find the complete list of CoreUI's variables in@coreui/coreui/scss/_variables.scss
. Some variables are set tonull
, these variables don't output the property unless they are overridden in your configuration.
Variable overrides must come after our functions are imported, but before the rest of the imports.
Here's an example that changes thebackground-color
andcolor
for thebody
when importing and compiling CoreUI for Bootstrap via npm:
Heads up!
Since@coreui/coreui
v5.3.0 and@coreui/coreui-pro
v5.10.0, we support Sass modules.
You can now use the modern@use
and@forward
rules instead of@import
, which is deprecated and will be removed in Dart Sass 3.0.0. Using@import
will result in a compilation warning. You can learn more about this transitionhere.
@use "@coreui/coreui/scss/coreui" with ( $body-bg: #000, $body-color: #111)
Sass@import
are deprecated and will be removed in Dart Sass 3.0.0.!
You can also use@import
rules, but please be aware that they are deprecated and will be removed in Dart Sass 3.0.0, resulting in a compilation warning. You can learn more about this deprecationhere.
// Required@import "@coreui/coreui/scss/functions";// Default variable overrides$body-bg: #000;$body-color: #111;// Required@import "@coreui/coreui/scss/variables";@import "@coreui/coreui/scss/maps";@import "@coreui/coreui/scss/mixins";@import "@coreui/coreui/scss/root";// Optional CoreUI components here@import "@coreui/coreui/scss/reboot";@import "@coreui/coreui/scss/type";// etc
Repeat as necessary for any variable in CoreUI, including the global options below.
Maps and loops
CoreUI for Bootstrap includes a handful of Sass maps, key value pairs that make it easier to generate families of related CSS. We use Sass maps for our colors, grid breakpoints, and more. Just like Sass variables, all Sass maps include the!default
flag and can be overridden and extended.
Some of our Sass maps are merged into empty ones by default. This is done to allow easy expansion of a given Sass map, but comes at the cost of makingremoving items from a map slightly more difficult.
Modify map
All variables in the$theme-colors
map are defined as standalone variables. To modify an existing color in our$theme-colors
map, add the following to your custom Sass file:
@use "sass:color";@use "sass:map";@use "@coreui/coreui/scss/variables" as *;$danger: color.scale($danger, $lightness: 45%);$primary: #0074d9;
Later on, these variables are set in CoreUI's$theme-colors
map:
$theme-colors: map.merge($theme-colors, ( "danger": $danger, "primary": $primary));
Add to map
Add new colors to$theme-colors
, or any other map, by creating a new Sass map with your custom values and merging it with the original map. In this case, we'll create a new$custom-colors
map and merge it with$theme-colors
.
Heads up!
Since@coreui/coreui
v5.3.0 and@coreui/coreui-pro
v5.10.0, we support Sass modules.
You can now use the modern@use
and@forward
rules instead of@import
, which is deprecated and will be removed in Dart Sass 3.0.0. Using@import
will result in a compilation warning. You can learn more about this transitionhere.
@use "sass:map";@use "@coreui/coreui/scss/variables" as *;$custom-colors: ( "custom-color": #900);$theme-colors: map.merge($theme-colors, $custom-colors);@use "@coreui/coreui/scss/coreui";
Sass@import
are deprecated and will be removed in Dart Sass 3.0.0.!
You can also use@import
rules, but please be aware that they are deprecated and will be removed in Dart Sass 3.0.0, resulting in a compilation warning. You can learn more about this deprecationhere.
// Create your own map$custom-colors: ( "custom-color": #900);// Merge the maps$theme-colors: map-merge($theme-colors, $custom-colors);
Remove from map
To remove colors from$theme-colors
, or any other map, usemap-remove
. Be aware you must insert it between our requirements and options:
Heads up!
Since@coreui/coreui
v5.3.0 and@coreui/coreui-pro
v5.10.0, we support Sass modules.
You can now use the modern@use
and@forward
rules instead of@import
, which is deprecated and will be removed in Dart Sass 3.0.0. Using@import
will result in a compilation warning. You can learn more about this transitionhere.
@use "sass:map";@use "@coreui/coreui/scss/variables" as *;@use "@coreui/coreui/scss/maps" as *;$theme-colors: map-remove($theme-colors, "info", "light", "dark");$theme-colors-border-subtle: map.remove($theme-colors-border-subtle, "info", "light", "dark");@use "@coreui/coreui/scss/coreui";
Sass@import
are deprecated and will be removed in Dart Sass 3.0.0.!
You can also use@import
rules, but please be aware that they are deprecated and will be removed in Dart Sass 3.0.0, resulting in a compilation warning. You can learn more about this deprecationhere.
// Required@import "@coreui/coreui/scss/functions";@import "@coreui/coreui/scss/variables";@import "@coreui/coreui/scss/maps";@import "@coreui/coreui/scss/mixins";@import "@coreui/coreui/scss/root";$theme-colors: map-remove($theme-colors, "info", "light", "dark");// Optional@import "@coreui/coreui/scss/reboot";@import "@coreui/coreui/scss/type";// etc
Required keys
CoreUI for Bootstrap assumes the presence of some specific keys within Sass maps as we used and extend these ourselves. As you customize the included maps, you may encounter errors where a specific Sass map's key is being used.
For example, we use theprimary
,success
, anddanger
keys from$theme-colors
for links, buttons, and form states. Replacing the values of these keys should present no issues, but removing them may cause Sass compilation issues. In these instances, you'll need to modify the Sass code that makes use of those values.
Functions
Colors
Next to theSass maps we have, theme colors can also be used as standalone variables, like$primary
.
.custom-element { color: $gray-100; background-color: $dark;}
You can lighten or darken colors with CoreUItint-color()
andshade-color()
functions. These functions will mix colors with black or white, unlike Sass' nativelighten()
anddarken()
functions which will change the lightness by a fixed amount, which often doesn't lead to the desired effect.
// Tint a color: mix a color with white@function tint-color($color, $weight) { @return mix(white, $color, $weight);}// Shade a color: mix a color with black@function shade-color($color, $weight) { @return mix(black, $color, $weight);}// Shade the color if the weight is positive, else tint it@function shift-color($color, $weight) { @return if($weight > 0, shade-color($color, $weight), tint-color($color, -$weight));}
In practice, you'd call the function and pass in the color and weight parameters.
@use "@coreui/coreui/scss/functions/color" as *;.custom-element { color: tint-color($primary, 10%);}.custom-element-2 { color: shade-color($danger, 30%);}
Color contrast
In order to meet theWeb Content Accessibility Guidelines (WCAG) contrast requirements, authorsmust provide a minimumtext color contrast of 4.5:1 and a minimumnon-text color contrast of 3:1, with very few exceptions.
An additional function we include in CoreUI for Bootstrap is the color contrast function,color-contrast
. It utilizes theWCAG 2.0 algorithm for calculating contrast thresholds based onrelative luminance in asRGB
colorspace to automatically return a light (#fff
), dark (#212529
) or black (#000
) contrast color based on the specified base color. This function is especially useful for mixins or loops where you're generating multiple classes.
For example, to generate color swatches from our$theme-colors
map:
@use "@coreui/coreui/scss/functions/color-contrast" as *;@each $color, $value in $theme-colors { .swatch-#{$color} { color: color-contrast($value); }}
It can also be used for one-off contrast needs:
@use "@coreui/coreui/scss/functions/color-contrast" as *;.custom-element { color: color-contrast(#000); // returns `color: #fff`}
You can also specify a base color with our color map functions:
@use "@coreui/coreui/scss/functions/color-contrast" as *;.custom-element { color: color-contrast($dark); // returns `color: #fff`}
Escape SVG
We use theescape-svg
function to escape the<
,>
and#
characters for SVG background images. When using theescape-svg
function, data URIs must be quoted.
Add and Subtract
We use theadd
andsubtract
functions to wrap the CSScalc
function. The primary purpose of these functions is to avoid errors when a "unitless"0
value is passed into acalc
expression. Expressions likecalc(10px - 0)
will return an error in all browsers, despite being mathematically correct.
Example where the calc is valid:
@use "@coreui/coreui/scss/functions/math" as *;$border-radius: .25rem;$border-width: 1px;.element { // Output calc(.25rem - 1px) is valid border-radius: calc($border-radius - $border-width);}.element { // Output the same calc(.25rem - 1px) as above border-radius: subtract($border-radius, $border-width);}
Example where the calc is invalid:
@use "@coreui/coreui/scss/functions/math" as *;$border-radius: .25rem;$border-width: 0;.element { // Output calc(.25rem - 0) is invalid border-radius: calc($border-radius - $border-width);}.element { // Output .25rem border-radius: subtract($border-radius, $border-width);}
Mixins
Our@coreui/coreui/scss/mixins/
directory has a ton of mixins that power parts of CoreUI and can also be used across your own project.
Color schemes
A shorthand mixin for theprefers-color-scheme
media query is available with support forlight
,dark
, and custom color schemes.
@mixin color-scheme($name) { @media (prefers-color-scheme: #{$name}) { @content; }}
@use "@coreui/coreui/scss/mixins/color-scheme" as *;.custom-element { @include color-scheme(dark) { // Insert dark mode styles here } @include color-scheme(custom-named-scheme) { // Insert custom color scheme styles here }}