Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: the road to fully consumable Pattern Libraries in PL (v3.0 - v4.0) #834
The road to fully consumable Pattern Libraries in PL (v3.0 - v4.0)
And to be clear, I'm talking here about a pattern library being publishable via NPM (or similar) and fully, directly consumable by a site or application without a nasty copy step or transform.
So, okay. Why is this hard currently?
It's hard because the default experience Pattern Lab is limiting. It promises ease of authoring at the cost of lock-in. It allows templates (or components, I suppose!) to include each other with names and syntaxes that aren't supported directly by the templating systems themselves
How would we fix this?
I think this all leads to the following conclusion: for patterns and components in a PL library to be directly consumable, Pattern Lab must
But what's the plan?
Here's how I think we can pull this off:
So... what's next?
referenced this issue
Apr 4, 2018
It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!