1.4 - Tailwind - First look

Looking forward to it :smiley:

1 Like

Bump :smiling_face:

Quite excited :tada:


1 Like

Saw the Tailwind video on YouTube.
A phenomenal choice of introducing a popular and widely used CSS framework like Tailwind within a Wordpress page-builder, the ecosystem surrounding it, and the implementation is super slick. Kudos.

wow ! i don’t have words except than wow wow wow ! i’m looking forwards for 1.4 and i have a new site to build so i’ll wait for monday to start this one :slight_smile:

congrats Cwicly team, i love you !

This is exceptional and goes far beyond any personal expectations.
The overall impression for me is an even more streamlined workflow.
It takes away so many Tailwind and general class building/management pain points.

Here are my first points which needs to be addressed imo:

  • The added TW classes require consistency/organization. This was also mentioned in the live. With TW, one easily has added 20-30 classes to a block in an instant and this would be quite chaotic, nicely expressed. I’m also concerned about pushing the Primary/Design/Advanced tab too far down due to the amount (and partly length) of classes. Not sure if that could become an issue and if so, how to solve it
  • Quick access to property editing is huge! Is it possible to direct the user to its specific area, not to the general one? Clicking a box-shadow class sent Louis to the Borders tab, instead of Borders > Shadows. Seems like it’s the current general behaviour

There are some more questions open to me, but I’ll include that (if still relevant) with my initial feedback as soon as I have the opportunity to get my hands on.

I was always a huge fan of Tailwaind’s core concept but didn’t see it ever to become useful in some way inside a builder.
When TW for Cwicly was announced, my interest was quite moderate. I could see the benefit in combination with components though.
Now, I’m seriously considering making a full switch to Tailwind. At least I will have a hard time deciding against it. It’s just too powerful. Of course, this first impression might change.

1 Like

I had developed with Bootstrap for years then shifted over to Tailwind. The biggest difference is Mobile first design flow (that was an adjustment to say the least) and all those classes. The shell concept is an excellent management option to litigate all those classes.

This utility class framework you will adapt to quickly and become accustomed to looking through the classes for your styling without having to drill down into the UI as often.

I don’t know if this is a feature, but the option to turn ‘off’ and ‘on’ TW classes without deleting them from the block would be very functional. Like you can with relative styling.

1 Like

You can do that by clicking the class, just like you would do with a virtual class.

@Marius Oh I see lovely! Thank you for the link

Congratulations cwicly team.
Impressive implementation of tailwind.

Im aware that Tailwind has huge ecosystem and highly popular amongst developer outside wordpress (eg:just check at state of css 2023 data).

Once this feature ready and stable, you definitely have to use the momentum to promoting it :slight_smile:
Many developers may not yet realize the possibility of having WordPress + Webflow-like builder + Tailwind, now all in one solid package.

1 Like

I’ve never used Tailwind before, but this has got me interested in taking a course on it. Given that it will be a native part of Cwicly, a lot of other people in my position might do the same. If Tailwind can help people make websites faster, with more efficient code, and better designs that improve the user experience, then it’ll be worth the effort to learn.

This is pure GOLD. Something I have only been dreaming of for many years. Now to dig out my LTD! :slight_smile:

This is a really exciting time. The execution of the tailwind integration looks incredible and seems a lot more elegant than the likes of Pinegrow (which is still a great product!).

I predominantly build fully custom themes using Roots Sage and Bedrock, but am now going to be using Cwicly to execute the vast majority of new builds from now on.

I can’t wait to start using it. A huge thanks and congrats to Louis and the whole Cwicly team, you are creating THE solution for an advanced visual builder for WordPress. I can’t express how impressed and grateful I am with what you’ve done so far, and what is on the horizon.


@izzy I worked with Pinegrow as well before finding Cwicly. Unfortunately I ran into too many obstacles (with Pinegrow) and it didn’t suit me. Cwicly and the engagement of the dev team are particularly refreshing. The Tailwind integration is quite an accomplishment to say the least.


@hopscotch 100% agree with you on how amazing the engagement is from the Cwicly team. I don’t know where they find the time being such a small team managing the dev, documentation, videos, admin, support, community engagement etc. They are all super talented and hard working.


Hi there,
here some thoughts from me.

First a super BIG thank you to the Cwicly team for your work and for this update. :heart:

I really appreciate the Tailwind integration because, as mentioned several times, it greatly reduces the number of classes that need to be named. In my case, I am testing a new, simple website setup and have not created a single additional class so far.

Since class cluttering was already a big topic before the tailwind integration, I personally wouldn’t mind an additional button to toggle the block classes on and off. As in the example below, a simple button pushes the UI down quite a bit and I for one don’t feel the need to constantly check all classes. Unless I again missed to check an option :sweat_smile:


I would also prefer a somewhat sorted order of the classes. For example, the hover state is in the middle of all classes. Which doesn’t exactly make it easy to distinguish between the classes.

An alternative could be to highlight the classes that are currently active, or highlight only the specific classes in the current state, as shown below for hover.


And again, unless I missed it, I would like to be able to copy classes to another block. As far as I know, this is partially possible with shells. But what if I only want to edit that one element and not the shell? So I’m not sure if I’m looking for the ability to unpack the classes of a shell again. :thinking:

Well, that’s it for now, I’m having fun playing around with the new update. :+1:


1 Like

Hey @T-low.

I think most of your points have already been covered here, thanks for adding your thoughts too, confirming the necessity.
It would probably the best idea to create dedicated Feature Requests for it.

There is a quite powerful context (right-click) menu, which should fulfil your requirements of copying and pasting.


1 Like

Hi @Marius,
thank you for the info :+1:

Feature Requests Tailwind UI Ideas For Additions & Changes :white_check_mark:

Seems I am experiencing some problems there: Copy Pasting Classes


1 Like

That’s great @T-low.

Although separate Feature Requests for

  1. Addressing UI issue when many TW classes applied
  2. TW class order/organization and front-end output

would make more sense imo.
From my own experience in the past, merging many ideas into one topic won’t work out as anticipated.
It also can get chaotic and important things might get missed.

Just a hint, no call to action :handshake:

Well Why not @Marius, organisation is important :yum:

Feature Requests Tailwind UI Classes Clutter :white_check_mark:
Feature Requests Tailwind UI Classes Organisation & Display :white_check_mark:


@T-low these are great suggestions. Definitely worthy of feature requests.