the-spec
the-spec copied to clipboard
The specification for implementing Pattern Lab in various languages. This way there can be common core functionality and common shared assets.
As a design system creator, I want other product teams to have the ability to inherit base patterns and assets from an upstream, unchangeable starterkit, so that they may build...
The purpose of this post is to describe the vision for using Pattern Lab as a proper style guide website (a storefront) in addition to continuing to serve as a...
Each `*.md` has been consider "Documentation" and appears in various ways to tell more about the pattern. Originally, changing the file name of the pattern informed pattern lab about it:...
Per discussion over here: https://github.com/pattern-lab/patternlab-php-core/pull/139#issuecomment-337945453 Having pattern states affect larger components is typically a good idea. If the primary nav isn't done, the header isn't done, which means the homepage...
I'm not sure if this is the exact right place to discuss this, but as I've been cleaning up the UI layer, I've been thinking about the role of annotations...
**Seeking Clarification** According to [http://patternlab.io/docs/pattern-hiding.html](http://patternlab.io/docs/pattern-hiding.html), hidden patterns may be included in other patterns, but they will not be accessible from the navigation. Should a user of Pattern Lab be able...
As a design system creator using Pattern Lab, I want to be able to override data values at the category level, so that I don't have to manually copy-paste (and...