3 ms·
For those recommending Tailwind, it's huge if you're using it from the CDN (318K uncompressed). Other tools (except for Tachyons, these are maybe out of scope
by tbran 4y ago
For those recommending Tailwind, it's huge if you're using it from the CDN (318K uncompressed).
Other tools (except for Tachyons, these are maybe out of scope for a home lab):
- Tachyons [0] is a small (16K-ish) utility class framework.
- DaisyUI [1] is a free and open source component lib for Tailwind.
- WindiCSS [2] is built on Tailwind with some additional features.
- UnoCSS [3], an interesting on-demand atomic CSS engine that supports Tailwind CSS, WindiCSS, Bootstrap, and Tachyons.
[0]: https://tachyons.io/ https://tachyons.io/
[1]: https://daisyui.com/ https://daisyui.com/
[2]: https://windicss.org/guide/ https://windicss.org/guide/
[3]: https://github.com/unocss/unocss https://github.com/unocss/unocss
- atonse 4y agoRegarding Tailwind, shouldn’t you always run postcss in production? I wondered if anyone’s working on the following: Tailwind.js running on a cloudflare worker (so it’s a “CDN”) and calculates the postcss on first request and then caches it. Wouldn’t that be the best of both worlds?
- sanjayio 4y agoYes, always purge / treeshake and then tailwind will have a significantly smaller footprint.