liip / Kanbasu

Important information

Kanbasu won’t get any new features from now on, we do not recommend using it in new projects.

This framework was created during a time it solved an actual problem for us and after being used for years, we think there are now better solutions available. In particular, we are convinced that the utility-first approach gives us more control over the styling of interfaces with less code.

If you’re looking for an alternative in that direction, we’re recommending the amazingly well-done Tailwind CSS.

Kanbasu is a toolbox to create responsive web interfaces quickly. It’s focused on the layout and voluntarily avoid defining much “styling” properties which can be completely different from project to project.

Written is Sass, it’s highly customizable, every component being optional and customizable with variables.

CSS features used are working in all current major browsers. The oldest Internet Explorer version supported is 11. However, the framework does not include vendor-prefixed properties! When building it, we recommend you to use Autoprefixer to ensure a complete compatibility.

Read more and browse the documentation on kanbasu.liip.ch.

Install

With npm (recommended)

npm install --save-dev kanbasu

With Yarn

yarn add --dev kanbasu

As a Git submodule

git submodule add [email protected]:liip/kanbasu.git

Manually

Download the latest release archive

Setup

Easily scaffold a new project by running the script below in your project directory to:

1. duplicate kanbasu.scss (renamed main.scss) and settings/_settings.scss to the specified destination
2. adapt paths inside main.scss to match the Node module location
3. remove Sass !default flags from settings/_settings.scss
4. import settings/_settings.scss into main.scss

With npx:

npx kanbasu path/to/your/sass/directory

See other scaffolding methods.

Disclaimer

Kanbasu does not include vendor-prefixed properties. You should consider using a tool like Autoprefixer to ensure the properties used match the desired browser support.

What’s next?

Have a look at the documentation →