Patterns are defined as something that can be accomplished in multiple ways utilizing a combination of component(s) with additional design considerations.
Patterns are “recipes” with “ingredients” (components) that are combined to accomplish something.
Patterns may have demo code associated with a pattern for example purposes. However no pattern will support all possible configurations in code.
We need to define what "demo code" is so we can be clear with our adopters about what they are getting (or not getting)
Decide how we will publish our pattern "recipes"
### Design
- [ ] https://github.com/carbon-design-system/ibm-products/issues/5651
- [x] Align with Core on pattern ingredient list method
- [ ] Onboarding: how do we document Onboarding patterns AND components
Determine how we deliver patterns
Patterns are defined as something that can be accomplished in multiple ways utilizing a combination of component(s) with additional design considerations.
We need to define what "demo code" is so we can be clear with our adopters about what they are getting (or not getting) Decide how we will publish our pattern "recipes"
Note: Publishing of ingredient list moved to 285