Should we be using the Nav block still, or opting to create our own menu from scratch using Tailwind and interations?
I feel like I was fighting trying to get Tailwind working with the Nav block. I eventually go there, but it didn’t seem intuitive
Should we be using the Nav block still, or opting to create our own menu from scratch using Tailwind and interations?
I feel like I was fighting trying to get Tailwind working with the Nav block. I eventually go there, but it didn’t seem intuitive
Hello @grantambrose,
The first instalment of the Tailwind integration brings its integration to most Cwicly blocks.
For the more complex ones like the Nav block that have nested elements, please bear with us while we integrate them fully for Tailwind support.
Cheers,
I’m not sure if this has been mentioned in the live revealing cwicly to be free or in the forum, but this question is of utter importance to me as well.
when opting for tailwind, I’d love to use a nav block preset that respects the mobile first approach. will this be taken care of the next update, @Louis ?
Hello @oppi,
Yes this is planned for the Nav block and all other Cwicly blocks. Some blocks will have their primary settings compatible with Tailwind in the next update, but the complexity of the Nav block means we will focus on it for another update.
It is set on our important to-do list as necessary for our design system.