After completing the deep integration with Gutenberg, Bricks Builder, and Oxygen by dynamically retrieving values from them, it’s time to focus even more on
in-browser actions.
Winden is no longer dependent on a server to compile CSS!
With that said, we reassure you that you will have full ownership of Winden and the compile process. Even if something happens to DPlugins, you will still be able to compile in the future.
other benefits? SPEED!
The compile process is now even faster, taking around 50ms. We’ve also merged the save and cache buttons, so you’ll receive the updated CSS instantly after making any changes.
More Benefits?
Autocomplete is not compiled anymore!
We’ve transitioned from compiling class names into a JSON array to directly communicating with the Tailwind Config, allowing us to retrieve all the data in real-time. This gives us access to more than just class names—it enables us to see the specific values associated with classes like p-2 or rounded-sm.
This new approach also gives us greater flexibility for integrations. Consequently, we’ve started incorporating screen helpers into the Gutenberg autocomplete, further enhancing functionality and improving the user experience.
This also means that during compilation, there is only one task instead of two, reducing the load on both the browser and the server. This leads to even less stress on system resources, improving performance and efficiency.
Note:
Did I mention that we’ve developed this serverless feature so that we’re no longer dependent on waiting for other developers to push fixes for new Tailwind support?