We’ve made an important decision: Winden is now open source for Gutenberg integration.
The core Gutenberg + Tailwind workflow is available for everyone to use, learn from, and build upon—completely free.
While Winden Pro will continue to exist for advanced features like other visual builders and file scanners, the Gutenberg integration is now fully open so the community can follow along, learn, and grow together.
Why Open Source?
Gutenberg on its own is powerful, but it still has limitations—especially when it comes to styling.
Often, you need to add extra CSS just to achieve relatively simple layouts or tweaks.
With Winden, instead of writing custom CSS, you can use a few Tailwind utility classes directly inside Gutenberg and you’re good to go.
That’s also why I decided to make this open source:
- So everyone can learn
- So everyone can see how it works
- So everyone can build better Gutenberg experiences
Education and transparency are the most important things here.
Gutenberg Course Coming Soon
Alongside this change, I’m also preparing a “Gutenberg for Everyone” course.
In the course, we’ll:
- Go deep into Gutenberg fundamentals
- Learn where Gutenberg falls short on its own
- Integrate Winden to solve real-world styling problems
- Build faster without writing custom CSS
If you want to truly understand how Gutenberg works under the hood—and how to push it further—this course will be for you.
Massive Performance Improvements 🚀
This update isn’t just about open sourcing—it’s also a huge performance upgrade.
We tested Winden on our own shop, which includes:
- A large number of licenses
- Heavy user meta
- API-driven data
- Gutenberg enabled on posts and custom post types
Before the refactor, some operations took 20–30 seconds.
After the update, the same operations now complete in just a few milliseconds.
What Changed?
- Major file refactoring
- Pro-only features were moved into a dedicated pro folder
- The open-source core is now fully visible and easier to follow
- CSS is now generated on post save
- Every time you save a post, Winden automatically compiles a new CSS file
- Visitors always get pre-compiled CSS
- No more compiling styles in the DOM on page load
This results in a massive performance boost for both editors and visitors.
How to Get Started
- 📦 Download Winden from GitHub (WordPress.org release is coming soon)
- 🐞 Create issues if you find bugs or have suggestions
- 💬 Join our Facebook group to discuss ideas and improvements
- 📬 Subscribe to our newsletter to get updates and early access to the Gutenberg course
We’re happy to help, listen to feedback, and keep improving Winden together with the community.
Thanks for being part of the journey 🙌




Leave a Reply