Living Styleguide

Devbridge Styleguide helps you create, share, and automate a living visual style library of your brand. Share your digital brand standards, improve team collaboration, and implement an independent easily-extendable modular structure.

Make sure you have following components installed on your machine:

#1 Install Styleguide node package to your local project's directory:
npm install devbridge-styleguide --save-dev
npm install devbridge-styleguide -g

#2 Initialize styleguide:
styleguide initialize

Copy of the styleguide will be generated and placed in your project's root directory under '/styleguide/' folder.

#3 Setup task runner:

var styleguide = require('devbridge-styleguide');

gulp.task('start-styleguide', function () {
module.exports = function (grunt) {
    var styleguide = require('devbridge-styleguide');
    grunt.registerTask('start-styleguide', function () {
        var done = this.async();
        styleguide.startServer().then(function (instance) {
            instance.on('close', done);

Run styleguide server: grunt start-styleguide

The Styleguide component has two modes - “view only” and “edit”.

"View only” mode does not have editing controls and is meant for presentation. It is a purely client-side application without any backend dependencies (html, css, and javascript only). It is delightly easy to share, publish, move, or export!

In order to switch to “Edit” mode and see all additional controls for editing, you need to run the styleguide server.

To manage categories:

Categories can be managed on your styleguide web page by clicking menu in the right top corner. You will be able to create, delete or modify categories.

To work with Snippets:

All snippet management is done in the browser. While styleguide server is running, you should be able to see additional controls for editing.

To scrape scss variables:

Scraping scss files you can automatically generate color palette or create a list of fonts used in the project.

  • First you need to add smart comment tags to your scss file to identify your variables:
    For color variables:
    //-- colors:start --//
    $color-black: #000000;
    $color-dark: #141823;
    $red-lighter: #d26262;
    //-- colors:end --//
    For font variables:
    //-- typo:start --//
    $font-proxima: 'Neue Helvetica W01', helvetica, sans-serif; // 300, 700
    $font-proxima-alternative: 'Neue Helvetica W01', helvetica, sans-serif; // 400, 400 italic
    $font-newsgothic: 'Neue Helvetica W01', helvetica, sans-serif; // 700
    //-- typo:end --//
  • Next, declare scss file path references in styleguide config file:
    "sassVariables": ['/path/to/your/project/scss/file.scss']

  • Lastly, open styleguide web page and select from the menu 'Scrape Variables'. Note, make sure you have styleguide server running.

To add CSS resources of the project to the styleguide:

Styleguide snippets are loaded through iframe using template.html file. All css references should be defined there.

To modify styleguide settings:

You can add project name, project logo or change settings modifying config.txt file, located in your styleguide directory:

  "projectName": "", //Project name
  "projectUrl": "",  //Domain name of your project
  "projectLogo": "", //path to your project logo
  "jsResources": [], //Javascript resources that's going to be included into the snippets
  "viewportWidths": [ //Predefinded viewport breakpoints
  "serverPort": 8889, //Default server port for styleguide component
  "snippetTemplate": "styleguide/template.html", //HTML template which will be used to wrap and show html snippets. Project CSS resources of the project should be placed in this template as well.
  "sassVariables": [], //Paths to your scss variables files
  "maxSassIterations": 2000,
  "database": "styleguide/db",
  "categories": "styleguide/db/categories.txt",
  "uniques": "styleguide/db/uniques.txt",
  "sassData": "styleguide/db/sassdata.txt",
  "extension": ".txt"

Find out more about the installation process and how to use it on Living Styleguide Github page.

What is Sourcery?

All of these components are Open Source.