KrafterPRO 2.0 Sneak Peek!
If you've ever imported a design system into Divi 5 and watched your global variables disappear — you know the panic.
I've been there.
One bad import. Server times out halfway through. Blank state. Everything gone.
That's exactly why I built this into KrafterPRO 2.0.
I just dropped a sneak peek video showing you what's new — and honestly, this update changes how you manage Divi 5 sites at a fundamental level.
Here's a taste of what's inside:
- Atomic imports — nothing gets written to your DB until everything is verified (no more half-broken imports)
- Rollback history — one click to undo any import instantly
- Full preview before you commit — see every color, font, and spacing token before a single thing changes
Please give me your thoughts and feedback. I will be releasing KrafterPRO 2.0 Tomorrow.
Is my understanding correct that if I have my own variables/presets that I use in addition to KrafterPro, the Merge button (updates by ID, keeps existing ones) allows me to update (overwrite) KrafterPro variables/presets only, while leaving my own variables/presets untouched? Thanks!
Aaron Kittredge That's my situation, too. After watching the introduction, it looks like what you've said is correct above. I'd also like confirmation about this . . . 👍
Thank you, that's what were missing in KrafterPro and for me it is a small step for Man, but a huge step for the Mankind.
Fantastic, Mak, what a great feature! 2 quick questions: (1) When importing a premade layout, wouldn't you just be sure NOT to click "import presets" so you don't have to remove them? (2) How would this design system work when using the new Divi quick sites? https://www.elegantthemes.com/quick-sites/ These are more enticing to me than the layouts, so you are not starting from scratch. I assume you would generate the starter or AI site, then use your new plugin to remove the variables and presets, then bring in KrafterPro ones, as you show?? This would be an amazing tutorial if you could create it. Thanks again!! Kind regards, John
Looks great. Just one thing, if I have already set my colours, will this not overwrite them? Thanks.
I’m very excited for this release especially for the import features. One thing I’m confused about is that in the video Mak . states that KrafterPro is now a plugin but proceeds to import JSON files. Maybe the backend framework is the plugin but the presets and variables JSONs also come with the downloads? I guess I’ll find out later today when I download it.
Hi Mak,
Fantastic tool! I saw you even built in a merge function—I’ve already been testing that, and it works perfectly. Your UI looks brilliant, by the way.
As I mentioned before, I always focus on testing functionality first during development before moving on to code refactoring. But the way you’ve built this is excellent! I can’t wait to get my hands on it and start testing it thoroughly.
After watching the video, I might already have an idea for a future extension. I’m currently testing some additions in my own plugin, and once they are stable, I’ll share those ideas with you.
Your tool makes KrafterPRO and your design framework even better by simplifying management. It really closes the massive gap that Elegant Themes has yet to address regarding variable and preset management. Thank you in advance for your creativity and dedication. You’ve definitely earned a few coffees!
Best regards,
Frank
Yeah, it's really a massive improvement. Mak . fixed the single biggest problem (duplicate presets after updating KrafterPRO) plus added some functionality (including protecting custom presets, et al) -
Good customer service, too. With a rapidly increasing number of users, Mak can respond more quickly to DIVI updates and updating KrafterPRO at scale got faster and safer. Nice work and much appreciated!
Yes, the issue with duplicate presets has been resolved. You can either do a clean reinstall of the update—with the side effect that all presets will be gone, including any you have created. The merge function could offer a solution here.
Using a naming convention is still important, as it is the only way to keep track of which presets are yours. Keep in mind that if you use an existing preset and expand upon it, it drops out of the update chain.
For example: If you use one of Mak's presets, expand it with your own settings or even CSS code, and save it as your own 'xy--\<preset / project-name...>', it will break the link. If Mak's preset receives an update later on (e.g., because Mak corrected a clamp() value), that change will not flow into your 'xy-preset....' and your preset will not be changed unintentionally. At least in my tests, it didn't.
So if you are using custom presets, be careful when updating presets and test the behavior in a staging environment first. The merge feature is very interesting in this context. I will test whether Mak's new tool already considers distinctions based on preset prefixes as soon as the rollout begins. I also wrote a technical article about this, which Mak has certainly read.
There are still other convenience options for preset management, as I like to call them. However, the first version that Mak wants to release cannot cover everything for everyone. I am also looking forward to the first plugin version, which has a very nice UI and includes a great range of features.
Frank Schlatter thank you, Frank! So just to be clear, when customizing one of Mak's presets, if I rename it "DH-Body Text" (for example) it will be protected from changes in a future "merge"-type update . . .