1. NEW LICENSE PANEL
   • This should address this request: https://feedback.headspinui.com/feedback/154764/
   • Also this should address cases when you need activate license again (local => production when URL changes) as whole license handling and checking logic is rewritten
   • Better design, telling you Pro/Free version, telling you is license active or not

2. PLUGIN VERSION NUMBER
   This should give small clue which version you are using right now, we have added UI element around each plugin panel so you could see
   https://feedback.headspinui.com/feedback/164037/

3. BETTER DATA HANDLING
   Default app needs 1000 input vars, when you add new palette that adds need for 200 vars.
   Most hosts are configured to 1000 and app in some configuration app could need 3000 input vars which results in only partial saving error.
   We don't think we should tell each time customers to change configuration, and that will be tedious task for us and customers so we think that we need rework saving logic for app data. Current implementation is sending JSON and encoding on server via wp_json_encode but due dynamic app nature there isn't way to be sure that customers will be safe with any config and it would be insane that we suggest some crazy numbers for max input vars just to use our plugin.

We are working on Saving API v2 which should encode/decode JSON on client side and send that data to server as single var which would eliminate need for special server configuration and keep plugin running smoothly on default hosting setups.

4. IMPROVED COLOR SYNC LOGIC
   We have found some edge cases related to color sync when user have palettes named like dummy-some and dummy where later would override first by value due missing this edge scenario of naming.

5. NEW FEATURE: Theme Directives
   This should make easy some common style patterns like main palette color (9) as background and respective onColor as foreground

Internal public note: We need to improve materials about theming, users were confusing and used dark mode theming to achive this. This is not same as dark theming and we should do better job in documentation/videos about this and make examples when user wants local dark theming, when theme directives, etc
Also with v1.3 we are going to have full weapon for theming, we need materials to cover this as it is powerful but users needs to understand patterns in theming and how they could work. We need to make Theming masterclass series to onboard users

Link to more details about directives: https://feedback.headspinui.com/feedback/164762/