You can actually build interactive tabs with daisyui without JS! relatively new addition i believe: daisyui.com/components/tab/#r… it uses a bit of radio input trickery (not sure if i am a fan, but it works)
Very well actually. Syntax-wise, they are very similar to React or Vue components - so it was easy for me to pick up. I find their rendering cycles much easier to predict than React Components.
If the JS-less way Thomas mentions doesn't work for you, look into Alpine: alpinejs.dev/
Very lightweight library, so it's great for this.
A good example is that I used a landing page called Landwind for #toyboxforlaravel , which was Flowbite based, but with a tiny bit of effort I converted it to only use Alpine.
How are you handling the JS part like interactive tabs?
I ended up having to build github.com/versoly/versoly-ui because it lacks JS otherwise I would have just used that.
You can actually build interactive tabs with daisyui without JS! relatively new addition i believe: daisyui.com/components/tab/#r… it uses a bit of radio input trickery (not sure if i am a fan, but it works)
After trying Daisy for a day I decided to just go bare bone Tailwind + Web Components. Removed Daisy.
understandable. how do web components work for you? have never used it myself
Very well actually. Syntax-wise, they are very similar to React or Vue components - so it was easy for me to pick up. I find their rendering cycles much easier to predict than React Components.
If the JS-less way Thomas mentions doesn't work for you, look into Alpine: alpinejs.dev/
Very lightweight library, so it's great for this.
A good example is that I used a landing page called Landwind for
#toyboxforlaravel , which was Flowbite based, but with a tiny bit of effort I converted it to only use Alpine.
Nice. I use Petite Vue instead as it is a little smaller and the core is Vue so any problems have a google answer haha.