Skip to content

Latest commit

 

History

History

npm

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Castor Tokens

npm version Bundle size

This is Castor addition providing design tokens, including (CSS/Sass) themes.

Get started

Install package:

npm install @onfido/castor-tokens

Then add a theme by following either approach from examples below.

Setup using CSS

In order to use a theme with plain HTML + CSS, you must make the source available to public, and include it.

For example, if you serve your app from "public" directory, you can copy day.css and/or night.css files from node_modules/@onfido/castor-tokens/dist to public (or your root assets folder), then choose and include one theme in your HTML file from the following options:

<link rel="stylesheet" href="./day.css" />
<link rel="stylesheet" href="./night.css" />

Setup using Sass

@use Castor Tokens within your main Sass file:

@use '~@onfido/castor-tokens' as theme;

One time only, choose and include one theme within your root element from the following options:

:root {
  // "day" theme
  @include theme.day();

  // OR "night" theme
  @include theme.night();
}

Setup using CSS-in-JS (for example Emotion)

Choose and import one theme from the following options in your root JS file:

import '@onfido/castor-tokens/dist/day.css';
import '@onfido/castor-tokens/dist/night.css';

Switch theme

To be able to switch between one and another, use "classed" themes when importing, and switch with the helper:

import { switchTheme } from '@onfido/castor-tokens';

// switch to "day" theme
import '@onfido/castor-tokens/dist/day-class.css';
switchTheme('day');

// OR to "night" theme
import '@onfido/castor-tokens/dist/night-class.css';
switchTheme('night');

You can also include class themes within your Sass file instead:

@use '~@onfido/castor-tokens' as theme;

@include theme.day('class');
@include theme.night('class');

These themes are not applied to the root element but instead theme variables are scoped to CSS classes, which are then applied to the body element.

If you're using CSS modules, you must use a global scope when including class themes. For example, for PostCSS:

:global {
  @include theme.day('class');
  @include theme.night('class');
}

You can also switch a theme on any selectable elements, for example switching on a section using the custom theme:

.castor-theme--custom {
  // ...theme CSS variables
}
switchTheme('custom', document.querySelector('.section'));

If you do not use JavaScript, you might consider including a different CSS theme file based on URL parameter.

Lastly, if you're extremely concerned about efficiency, you can shave off 1-3 KBs by not including base tokens twice, if they're shared between the themes you're switching:

@use '~@onfido/castor-tokens' as castor;

:root {
  @include castor.tokens();
}

@include castor.day('class', 'raw');
@include castor.night('class', 'raw');