Finally launched a sponsorship program for Tailwind CSS, with a bunch of cool perks โจ ๐ฌ Private Discord community ๐ค Cursor/Claude rules ๐จ Beautiful VS Code themes ๐ Raycast extension ๐ Early documentation ๐ซฃ Behind-the-scenes source code + Figma files We're calling it Tailwind Insiders ๐
Webdev - TailwindCSS
by @daspbn.eurosky.social
Webdev - TailwindCSS
We're hosting a local Tailwind Connect meetup โ in Miami! ๐ด Come hang out for a night of demos + Q&A with the Tailwind team and connect with other community members over pizza and drinks. ๐ Mindspace Wynwood, Miami FL ๐๏ธ Jan 21 @ 6pm RSVP to grab your spot: lu.ma/foeqxyz7
You know that annoying absolute positioning trick to add an inset ring around images to help them stand out? Way, way easier these days now that `outline` follows border radius ๐๐ป
Tailwind CSS just cracked 1 billion total downloads ๐ช๐ป Wild.
Having a blast working with the dreamstudio.co team on my new office/studio โ they put this rough shot together on the fly in like 15 minutes while we were on a call figuring out the layout, lighting, and camera placement in my new space. Total pros ๐ช๐ป Can't wait to see the finished concept!
Little Tailwind tip โ instead of trying merge classes and manage conflicts with `!important`, style things based on data or ARIA attributes and just handle everything declaratively with CSS:
Migrated the actual Tailwind UI website to the v4.0 beta this morning ๐ ๐ป (There's a Black Friday deal there too btw ๐)
TIL about the `<var>` element: developer.mozilla.org/en-US/docs/W...
In Tailwind CSS v4 a lot of utilities just let you put in any value you want now, like `col-start-71`, `z-43`, etc. so it's kind of weird to show a specific list of values in the API reference on the docs pages. If I did something like this instead, is it clear enough?