Feedback and Ideas for Improving Winden plain classes (in Bricks)

Hi Marko,

First, thank you for all the work you’ve put into Winden and for making plain classes compatible with Bricks 2.0. I really appreciate your efforts!

I wanted to ask a few questions and share some ideas for potential improvements.

Would it be possible to make the plain classes field work more like your Gutenberg integration, where we have a single text field and don’t need to press Enter to edit a class? Or is this a limitation on Bricks’ side? I feel this would speed up the workflow. What do you think?

This leads me to the first idea: could we get a keyboard shortcut to jump directly to the plain classes text field? This would be a great quality-of-life improvement and would reduce the need for mouse clicks even further.

Another challenge I often face when working with plain classes in Bricks is that it automatically sorts the classes based on the global class ID. This makes it difficult to arrange classes according to Tailwind best practices. I’m not sure how other Bricks users feel about this, but could this behavior be changed?

One idea to make it even better—and this could also benefit other page builders—would be to integrate the Prettier Tailwind plugin (which can auto-sort Tailwind classes). Adding an auto-sort button and/or an option to always auto-sort classes would help users avoid manually reordering classes each time.

Another small quality-of-life idea: add a small color preview circle next to color-related classes.

I just wanted to share some feedback and ideas based on my experience. Thanks again for developing Winden—it’s a fantastic plugin.

Kind regards,
Malte