Technical Considerations
- How do I version my design system using Knapsack?
- Can Knapsack work with a CMS-powered website or application?
- Does Knapsack integrate with hand-off tools like Zeplin, Avocode, or InVision Inspect?
- Does my source code repository need to be structured a specific way in order to work with Knapsack?
- Does Knapsack create NPM packages of my system?
- Is the preview in Knapsack identical to what's in the production app?
- Can I use Knapsack to automate pattern testing?
- How do I review, approve, and revert changes to my design system using Knapsack?
- Can I use breakpoint tokens as options when resizing pattern examples?
- Does Knapsack provide any hosting services?
- Can I make global changes to my product(s) using Knapsack?
- Can CSS and JS libraries be made available at a CDN?
- Does Knapsack provide notifications to users upon system changes or releases?
- Can my data be migrated to and from Knapsack easily?
- Can a Knapsack workspace support multiple design systems?
- Can my Knapsack workspace inherit components from other repos or systems?
- Does Knapsack create run-time dependancies for my application?
- Can a Knapsack workspace support multiple organizations?
- What are some common use cases for technical system contributors?
- How can Knapsack help with accessibility compliance?