I'm using Tabler for my latest project and love it so far. There are some caveats though:
- It's way too verbose sometimes. There are numerous instances where I would have done just a single tag and Tabler has two or three of them nested.
- Some similar components are implemented in way different ways. Compare .status-indicator which takes color as a dedicated class (`.status-green`, for example) and .badge, which uses background-color helpers (e. g. `.bg-green`).
- Secondary buttons are .btn without additional class, unlike .btn.btn-secondary in Bootstrap (which Tabler is based on). If you add .btn-secondary, you'll get a weird out-of-style button. Things get more difficult when you use a Bootstrap-based library for some interactive elements (I'm using Sveltestrap) and it adds .btn-secondary by default.
- Some layout bugs get introduced and fixed, nothing you can't patch out though. Hope it will get better as it matures.
Overall it's neat though, and for prototyping things quickly I'd say it's the best you can get now.
- It's way too verbose sometimes. There are numerous instances where I would have done just a single tag and Tabler has two or three of them nested.
- Some similar components are implemented in way different ways. Compare .status-indicator which takes color as a dedicated class (`.status-green`, for example) and .badge, which uses background-color helpers (e. g. `.bg-green`).
- Secondary buttons are .btn without additional class, unlike .btn.btn-secondary in Bootstrap (which Tabler is based on). If you add .btn-secondary, you'll get a weird out-of-style button. Things get more difficult when you use a Bootstrap-based library for some interactive elements (I'm using Sveltestrap) and it adds .btn-secondary by default.
- Some layout bugs get introduced and fixed, nothing you can't patch out though. Hope it will get better as it matures.
Overall it's neat though, and for prototyping things quickly I'd say it's the best you can get now.