A collection of foundational utilities for Sass.
npm install one-sass-toolkit --save// in your main.scss
@import "one-sass-toolkit/color";
@import "one-sass-toolkit/type-styles";
@import "one-sass-toolkit/fluid-size";
@import "one-sass-toolkit/fluid";The included tools are based heavily on the frontend development process at One Design Company, and as a result make some assumptions about the tools you're using and how your styles are organized.
There are three variables included for outputting helpers. One for each toolkit file.
$output-color-helpers
$output-spacing-helpers
$output-type-helpers
$output-fluid-size-helpers
By default all helpers are output, to turn them off just add the variable and set the variable to false.
One Sass Toolkit uses sass-mq for responsive adjustments, which expects you to have a global $mq-breakpoints variable that defines your mobile-first breakpoints. The exact sizes you have defined for these breakpoints can be anything, and you can specify additional breakpoints:
$mq-breakpoints: (
small: 500px,
medium: 768px,
large: 1024px,
xlarge: 1400px
);The color utility grabs colors and optionally generates helper class for your colors that can be used directly in your HTML.
.my-stuff {
background-color: color(blue);
color: color(yellow);
}<div class="h-color-bg-blue">
<h1 class="h-color-text-yellow">We all live in a yellow submarine</h1>
</div>Relies on a $colors map variable existing in the following format:
$colors: (
black: #222,
white: #fff,
gray: #aaa,
blue: #118bc1,
yellow: #ffe215
);Automatically generates all of the type styles for a project, provides a mixin for grabbing a specific set of predefined styles, adjusts type responsively, and provides optional helper classes for your type styles that can be used directly in your HTML. A type style can be any collection of CSS properties. Anything you add to the properties key of the configuration map will be output by the mixin.
.my-heading {
@include type-style(heading);
}
// Outputs the following css
/*
.my-heading {
font-family: Futura, 'Trebuchet MS', Arial, sans-serif,
font-size: 1.4rem,
line-height: 1,
text-transform: normal,
letter-spacing: 0
}
@media (min-width: 768px)
.my-heading {
font-size: 1.8rem;
}
}
*/If you'd like to get a type style at a specific size, without automatically including the responsive adjustments, you can use the get-type-style mixin:
.my-heading {
@include get-type-style(heading, medium);
}
// Outputs the following css
/*
.my-heading {
font-family: Futura, 'Trebuchet MS', Arial, sans-serif,
font-size: 1.8rem,
line-height: 1,
text-transform: normal,
letter-spacing: 0
}
*/And if you only want the basic styling for a font stack, you can use the font-stack-styles mixin:
.my-heading {
@include font-stack-styles(futura-bold);
}
// Outputs the following css
/*
.my-heading {
font-family: (Futura, 'Trebuchet MS', Arial, sans-serif),
font-weight: 700,
font-style: normal
}
*/<h1 class="h-type-heading">Ground control to Major Tom</h1>Assumes that you are using 10-based rem (e.g. font-size: 1.4rem; // 14 px) units for sizing across the site, via something like html { font-size: 62.5%; }
Also relies on $type-styles and $font-stacks map variables existing in the following format:
$font-stacks: (
futura-bold: (
font-family: (Futura, 'Trebuchet MS', Arial, sans-serif),
font-weight: 700,
font-style: normal
),
helvetica: (
font-family: ('Helvetica Neue', Helvetica, Arial, sans-serif;),
font-weight: normal,
font-style: normal
)
);
$type-styles: (
heading: (
stack: futura-bold,
sizes: (
default: 14,
medium: 18
),
properties: (
line-height: 1,
text-transform: normal,
letter-spacing: 0,
)
),
body: (
stack: helvetica,
font-smoothing: true,
sizes: (
default: 16,
medium: 24
),
properties: (
line-height: 1.4,
text-transform: uppercase,
letter-spacing: 1.2,
)
)
);The fluid size mixin makes it simple to smoothly adjust a value across a range of breakpoints, with precise control over the value at each breakpoint. It’s great for handling responsive margins and padding, but can be used for any numeric value, including font sizes, absolute/relative positioning values, etc. Interally, this mixin extends the fluid mixin mentioned later on. If you want a simpler, lower-level way to handle fluid property adjustments, check out the fluid mixin.
Relies on a $fluid-sizes map variable existing in the following format:
$fluid-sizes: (
s: (
default: 20px,
medium: 40px,
max: 80px
),
m: (
default: 20px,
medium: 60px,
max: 100px
)
);Each set in $fluid-sizes can have any key (e.g. s) and must include at least a default key/value and one other key/value pair representing another breakpoint. Each key/value pair inside of a set should have a key that matches a value from you $mq-breakpoints map, and a value that matches the desired value when the viewport width is at that breakpoint.
The default key here represents the minimum possible size/value, as defined by the $fluid-min-width variable, which is 320px by default. You can adjust this value by setting a $fluid-min-width variable to the smallest possible viewport width you want to handle.
* + * {
@include fluid-size(s); // by default, the value is applied to `margin-top`
}
* + * {
@include fluid-size(m, padding-bottom); // applies the value to any property
}When applied using the $fluid-sizes map in the example above, the first example here would output a margin-top value of 20px at a viewport width of 320px wide, which would scale up to a value of 40px at the medium breakpoint, then scale up to a maximum value of 80px at the max breakpoint. The value will never be less than 20px and never more than 80px
You can adjust the mixin to produce negative values from any $fluid-sizes set by setting the $negative parameter to true:
* + * {
@include fluid-size(s, margin-top, $negative: true);
}Due to some browser inconsistencies when using the CSS calc() function that is used by this mixin behind the scenes, we recommend setting all $fluid-sizes values in px, and all values must include a unit, even 0 values (i.e. use 0px instead of 0). Failing to follow these guidelines probably wont’t cause issues in all browsers, but cross-browser behavior may be inconsistent.
Works for any of the following classes:
h-fluid-size-top-margin-{$amount}h-fluid-size-bottom-margin-{$amount}h-fluid-size-top-padding-{$amount}h-fluid-size-bottom-padding-{$amount}
<h1 class="h-fluid-size-top-margin-s">Ground control to Major Tom</h1>Deprecated and may be removed in a future release. Use fluid-size instead.
Mixin to provide spacing (either margin or padding) to a defined location of an element and have that spacing scale down proportionally at smaller screen sizes. Can also optionally generate helper classes for use directly in your HTML.
.foo + .bar {
@include spacing(s); // by default, the value is applied to `margin-top`
}
.bar + .foo {
@include spacing(m, padding-bottom);
}Important: when provided as a function, the spacing will not be responsive.
.bar + .foo {
margin-top: get-spacing(m);
}Works for any of the following classes:
h-spacing-top-margin-{$amount}h-spacing-bottom-margin-{$amount}h-spacing-top-padding-{$amount}h-spacing-bottom-padding-{$amount}
<h1 class="h-spacing-top-margin-m">Ground control to Major Tom</h1>Relies on a $spacing map variable existing in the following format:
$spacing: (
none: 0,
xs: 2rem,
s: 3rem,
sm: 4rem,
m: 5rem,
ml: 6rem,
l: 8.5rem,
xl: 15rem
);The exact names of the keys in this map aren't important, as long as @include spacing(foo) has a matching key foo in the map.
Inspired by the work of Indrek Paas and the writing of Mike Riethmuller this mixin allows you to specify a minumum and maximum size for values. Allowing for more fluid websites.
@include fluid($properties)
/* Single property */
html {
@include fluid(font-size, 320px, 1366px, 14px, 18px);
}
/* Multiple properties with same values */
h1 {
@include fluid(padding-bottom padding-top, 20em, 70em, 2em, 4em);
}