🔍 You get access to this Raycast extension we built for ourselves, which is super handy for getting the CSS for a specific class, checking the specificity of a class, finding the nearest Tailwind color for a hex code, or looking up the nearest sizing utility for a pixel value.

🎨 We put together four custom Tailwind-inspired VS Code themes, based on the syntax themes we designed for the Tailwind website. Been using our "Dark (Enhanced)" one for years and could never switch to anything else at this point.

🤖 You get access to my ever-evolving custom Cursor/Claude/AGENTS.md rules for getting LLMs to follow Tailwind best practices, use the latest APIs, and generally just produce better code.

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 🚀

Yep good catch, this looks like a regression in how outline handles high border radius values. Going to hound Safari team to fix.

What version of Safari? Looks right here on 17.5:

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 `` 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?