Proposing a Change
Knapsack's Propose Change functionality enables all contributors - technical and non-technical alike - to make changes to core system documentation and assets via the Knapsack UI.
When a change is proposed via the UI, Knapsack creates a pull request ("PR") in the connected git repo with your changes, allowing the change set to be entered as a permanent record in the version history timeline of your design system.
After you have made changes to your system via the Knapsack UI, click Propose Change from the main settings menu.
A form modal will appear, allowing you to enter a title for the change proposal, as well as a detailed description or notes.
The information entered here will become a permanent record in version history of your system, so it’s worth taking the time to provide a clear explanation.
Once ready, click the “Propose Changes” button.
Once the PR is created, a toast modal will appear in the bottom right of the screen providing a link to the PR in the connected git repo. in.
How this pull request is managed will be up to your team’s governance model and how you set up Knapsack to handle content changes (some teams opt to have them directly merged into the master branch and deployed, others prefer an approval process).