Skip to content
This repository was archived by the owner on Jun 25, 2025. It is now read-only.
This repository was archived by the owner on Jun 25, 2025. It is now read-only.

Decide on how we consume/offer PatternLab #11

@addyosmani

Description

@addyosmani

The way I've seen a few developers use PatternLab is by including the patternlab-node repo as part of their patterns directory, allowing them to just use the default build process for generating the style guide.

This allows your main build process and pattern process to be separate. Unfortunately, this isn't very clean and as we're using Gulp would mean using two different build systems (Grunt AND Gulp).

We have a few options for how we can work around this.

  1. Only include the output of patternlab-node (CSS and or Sass files) in Sushi. If a developer wants to generate their own they will need to install patternlab-node and we can provide instructions of how to do so. Cons: effort by the developer to make use of PatternLab.

  2. Re-write the patternlab build process so that it can be called from our Gulpfile. This allows the user to have one place where they can look for all of their build tasks. I believe https://github.com/growdigital/creeky/blob/master/gulpfile.js tried to do something similar. Cons: slightly beefier Gulp file.

  3. Use something other than patternlab for generating the styleguide and styles for the project. PatternLab is used by lots of RWD designers as a baseline so it would be useful to stick with it if possible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions