Loom lets you easily build your own design systems. Organised around ITCSS it gives you a quick way of scaffolding sites, and then a more nuanced way of developing your own components.
Highly modular, Loom lets you easily extend it with your own modules and classes.
.c-fancy-button {
@include button(get-color(white), get-color(primary-brand));
@include font-size(large);
padding: get-spacing(xsmall) get-spacing(small);
}Loom's manifesto and opinions:
- Loom tries to make things easier for a developer.
- Loom doesn't come with a "theme" or a prebuilt pattern library. Loom helps you to weave your own pattern libraries.
- Loom is a tool and isn't designed to "drop in and go". It is something to help professional designer/developers in their everyday tasks.
- Loom is very opinionated about:
- Being an integral part of a design system. Therefore in Loom all colour, spacing and font values originate from centralised settings and are accessed only via getter functions.
- Keeping styling separate from structure. Loom only provides minimal styling to HTML elements and leaves everything else up to classes.
- Keeping specificity low. Loom is structured around ITCSS, so a selectors specificity should come from its source order, and nothing else. That also means:
- No
@extends. These so, so, so easily mess up the source order of a project. Because ITCSS, the core of this, is source order dependent, it's best to avoid any use of@extend. - No nesting. Loom really doesn't like nesting. Nesting makes for horrible specificity problems.
- No IDs. IDs make for even more horrible specificity problems. Just... no.
- No
- Being modular. If you don't like the way something works in Loom, you can remove it or use your own module instead.
- Loom doesn't care about:
- How you name your CSS selectors. Yes, it's opinionated about Sass structure, but kinda indifferent to your CSS output.
- Whether you want to use atomic or utility classes.
- Vendor prefixes - let's leave that up to Autoprefixer.
Eventually this will be an npm module, a bower module and gem. For now it's installable via npm:
$ npm install loomcss --save-devOr go old-school and copy/paste the contents of the assets folder into your project. Hey, whatever works, right?
Once installed, you will need to add the installation path to your own build system. This will probably be something like node_modules/loomcss/assets.
Once you have made that folder available to your build you can access the Loom layers using:
// -----> ADD YOUR OWN MODULES ABOVE HERE!
@import 'loom/10-global-settings';
@import 'loom/20-tools';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/30-generic';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/40-base-elements';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/50-layout';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/60-objects';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/70-ui-components';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/80-utilities';
// -----> ADD YOUR OWN MODULES BELOW HERE!
@import 'loom/90-trumps';
// -----> ADD YOUR OWN MODULES BELOW HERE!Please DON'T just link to main.scss! This will prevent you getting access to the interweaved layers of the ITCSS stack (it's there as an example only). Instead, copy the list of imports from main.scss into your main project file. Yes, it feels a bit unusual, but you'll gain a lot of power by doing so.
Add you own modules underneath the Loom layers (with the exception of the settings layer - to override Loom variables your own settings module must be placed above the Loom module.) If you require even more fine-grained control then you can copy and paste the imports from the layer import partials to your own Sass file.
Please remember that this framework is a basis for your own design system and won't give you much to see visually out of the box!
The Sass in the project is arranged in layers, with specificity and scope increasing as you decend from layer 10 to 100. Layers at the top (10) are extremely broad in scope and of low specificity, and those at the bottom (100) being extremely specific and high specificity.
You can add your own layers, but the default ones are as follows:
Sass global variables. Should only contain those things used by multiple layers and modules.
Mixins and functions to support the lower layers.
Generic CSS, imported Normalize and Reset CSS. Things that aren't really visual, but have a lot of impact across the project.
Specific simple styling for base elements. Loom gives some extremely simple styling to those elements that have a standard visual "state" and are not normally styled with the aid of classes (<p>, <ul>, <dl>, etc).
Headings (<h1> to <h6>) are the exception to this, as they are often used to provide semantic meaning, and so have their styling removed by default.
In general styling for must be added via a module from the Objects, UI Components or Utilities layers.
Layer modules that provide layout-specific styling. They are used on wrapper containers that themselves contain Objects or UI Components.
NOTE: Complications will likely occur if a Layout module and a lower layer module are used on the same HTML element!
Complex chunks of CSS that are used as the base for UI Component modules. Each object is defined as a mixin and expressed as a class, and each class can be used on its own.
The classes can be used for quick scaffolding, anchoring their classnames directly to CSS. (However, Loom opines that they should eventually be converted into UI Components, which directly consume the Object mixins. But Loom has some funny ideas and talks about The War a lot).
Some things might stay as class-based objects, and be used as a base for skinning, in true OOCSS style. For example, .button can serve as the OO base for .c-button and .c-button--primary.
<button class="o-button c-button c-button--primary">Continue</button>Or .c-button might consume @include o-button directly:
.c-button {
@include button();
}<button class="c-button c-button--primary">Continue</button>Your choice!
These are highly visual components built from Object mixins, Loom settings and custom CSS.
This layer will probably form the core of your own projects! :D
Utility modules provide classes that do one thing. While most visual styling should come from the component layer, there are always occasions where a separate class is needed to quickly nudge a component into shape.
Loom thinks that these should be used with caution, and that excessive use of these implies that a component or setting is lacking.
"Trumps" as in "a trump card". Extremely high specificity selectors live here!
Anything in this layer is used with some embarrassment. An example use might be to override CSS coming from external sources.
The only layer that !important is permitted in a module.
By default this project uses BEM notation for the optional CSS selectors.
You can specify fonts via the $LOOM-fonts. By default there is a primary and a secondary font. The default usage is secondary for headings and primary for everything else.
Each of these has a base and a webfont variant. These are for use with a font-observer system, that will add the class specified in $LOOM-fonts-loaded to the HTML element, allowing webfonts to be used without FOIC occurring.
The naming convention for internal variables and classes is as follows:
object-property-variant-state
objectis the thing being operated on.propertyis the aspect of object that is being altered.variantis a version of the object.stateis a state change, such as being active, or a breakpoint.
So examples of this might be:
.margin-left-small {}Object = margin; property = left; variant = small;$padding-top-largeObject = padding; property = top; variant = large;.button-background-primary {}Object = button; property = background; variant = primary;$button-background-color-hoverObject = button; property = background-color; state = hover; (note that background-color is one word. Hyphens are used to match the CSS property naming convention).
Always looking for fellow conspirators.