View on GitHub

Customize

Learn how to theme, customize, and extend Boosted with Sass, a boatload of global options, an expansive color system, and more.

Sass Utilize our source Sass files to take advantage of variables, maps, mixins, and functions.
Options Customize Boosted with built-in variables to easily toggle global CSS preferences.
Color Learn about and customize the color systems that support the entire toolkit.
Components Learn how we build nearly all our components responsively and with base and modifier classes.
CSS variables Use Boosted's CSS custom properties for fast and forward-looking design and development.
Optimize Keep your projects lean, responsive, and maintainable so you can deliver the best experience.

Overview

There are multiple ways to customize Boosted. Your best path can depend on your project, the complexity of your build tools, the version of Boosted you’re using, browser support, and more.

Our two preferred methods are:

  1. Using Boosted via package manager so you can use and extend our source files.
  2. Using Boosted’s compiled distribution files or jsDelivr so you can add onto or override Boosted’s styles.

While we cannot go into details here on how to use every package manager, we can give some guidance on using Boosted with your own Sass compiler.

For those who want to use the distribution files, review the getting started page for how to include those files and an example HTML page. From there, consult the docs for the layout, components, and behaviors you’d like to use.

As you familiarize yourself with Boosted, continue exploring this section for more details on how to utilize our global options, making use of and changing our color system, how we build our components, how to use our growing list of CSS custom properties, and how to optimize your code when building with Boosted.

CSPs and embedded SVGs

Several Boosted components include embedded SVGs in our CSS to style components consistently and easily across browsers and devices. For organizations with more strict CSP configurations, we’ve documented all instances of our embedded SVGs (all of which are applied via background-image) so you can more thoroughly review your options.

Based on community conversation, some options for addressing this in your own codebase include replacing the URLs with locally hosted assets, removing the images and using inline images (not possible in all components), and modifying your CSP. Our recommendation is to carefully review your own security policies and decide on the best path forward, if necessary.