Excited to share tailwindcss-fluid-font-size, a new fluid typography Tailwind plugin.
I’ve been iterating on Tailwind approaches to fluid typography for a couple years. tailwindcss-fluid-font-size is more flexible and, to me, the most ergonomic and idiomatically “Tailwindy” of the solutions I’ve built or read about.
Open minded Tailwind haters might even be interested in at least the design.
I honestly use #tailwindcss because I started out with HTML and CSS after the year 2000, and honestly today neither HTML nor CSS have a documentation that like the one offered by Tailwind lets me get to the doing part immediately.
It makes absolutely no sense that #DesignSystems and #FrontendFrameworks like #TailwindCSS have decided to have darker colors be higher numbers, since computer screens are an additive color system where the more color you add the brighter things get.
💜 Remix / Tailwind Infinite Scroll Masonry Grid 💜 So excited to have gotten this so smooth and beautiful. It might be my favorite component thus far. It is flawless from mobile to ultraHD, from 300px to 4000px!
Finally I switch to #vscode for developing front end work. It's super useful to see the converted class for #tailwindcss (I'm a beginner). I know there is lsp-tailwind, but I use eglot, and it cannot have multiple lsp server in one major mode yet.
Cet article (🇬🇧) explique tellement bien ce qui cloche avec Tailwind.css ! Ça me rassure de voir que ce point de vue existe toujours. Tailwind est simplement très très fort en communication/manipulation.
À lire !
> Because trends are temporary, but standards are forever.
It's still very experimental as it's very early days for this new TUI framework. But my friend @joshkarpel is building something very special here. It's a TUI framework in pure python, but inspired by #React, #TailwindCSS, and (of course) #Textual. Check it out!
Hey devs, I am working on a project that requires restricting a #fastapi API from public access, but data generated from API needs to be made available to clients. So, came up with this workflow, what do you all suggest?
With layers and scope, it may finally be possible to create a complex web site with pure #CSS without resorting to BEM or other hacks, and without frontend framework component-scoped styles.
Before scope and layer my stylesheets would inevitably get out of control and become append-only as the project grew and changed (and that's why I went to #tailwindcss .) But once scope gets broad support, I can see it working.
The criticisms against #tailwindcss are deserved in most cases.
But the put-downs against developers who use tailwind make me cringe. Things like "they use tw bc they couldn't be bothered to learn the cascade" that I see repeated over and over on here are bad. It paints a picture of the purist #CSS community as completely oblivious and uninterested in why tw came about in the first place.
Guess what: Tailwind is a cry for help. Blaming #webdev that use it isn't the win you think it is.
Hey! I’m a senior front-end developer looking for my next medium- to long-term freelance role.
I have 14 years of experience working along the full web development stack, usually with #JavaScript, #TypeScript, #ReactJS, #NextJS and #TailwindCSS. I often work with e-commerce and healthcare clients. Once, I helped turn a household appliance into a smart IoT prototype.
My website/blog has always had dedicated light and dark themes (thanks to using Tailwind from the ground up). It came to my realization, however, that the proper theme may not render by default based on people's OS preferences. That's why I added this small cosmetic touch that will hopefully help a bit.