Improved Design System & Kit Management
I would like to suggest a few improvements to how KrafterPro handles Design Systems, Colors, Fonts, Variables, and Presets.
1. Save Colors & Fonts as Reusable Kits
Please add the ability to save custom Color Kits and Font Kits. This would allow users to create, save, and reuse different brand/design configurations without having to recreate them manually.
2. Protect Existing Font & Color Kits During Updates
When updating the KrafterPro Design System, existing Font and Color Kits should not be overwritten automatically.
They should only be replaced when the user explicitly selects an option such as "Overwrite Existing Kits."
This is particularly important for projects where the default KrafterPro values have already been customized.
3. Non-Destructive Design System Updates
Design System updates should work more like a smart merge rather than a replacement.
Ideally, KrafterPro should:
- Ignore values that are already identical.
- Add only new variables/presets that don't currently exist.
- Clearly show which values will be Added, Updated, Skipped, or Overwritten.
- Preserve all user-created variables and presets.
- Protect customized values from being overwritten without confirmation.
- Provide a preview or summary of changes before applying the update.
The goal should be to allow users to safely update to the latest KrafterPro Design System without worrying about losing project-specific customizations.
4. Clear & Consistent Naming Structure
The naming structure across the Design System should be more standardized and predictable.
This includes:
Colors, Typography, Variables, Presets, Sections, Containers, Spacing, and other design tokens.
A consistent naming convention would make the system easier to understand, maintain, search, and scale—especially on larger websites.
KrafterPro Design System updates should be safe, transparent, and non-destructive, while giving users full control over what gets updated or overwritten.
This would make it much easier to keep KrafterPro updated across production websites without affecting existing customizations.
Thanks,
Kiran
I've done 2,3 and 4 Number one already exists.