Greg Sullivan

@juergengenser I also wrote release notes about building the new site for _tw and its documentation, in case that’s useful: underscoretw.com/release-notes/…

@juergengenser Sorry for the very belated reply—I’m not on here as much anymore! Yes, the docs are made with _tw. It’s this Tailwind Plus theme, modified to work with WordPress via _tw: tailwindcss.com/plus/templates…

So, Tailwind 4! _tw now fully supports the latest version, and it has been updated to use CSS configuration.

@se_nadir Not derailing whatsoever! That’s really great to know—that very much answers the question. Thank you!

@gregsvn Not to derail this but the calculator in cart is going away github.com/woocommerce/wo… it’s been a major pain and a source of many confusion settings and bugs in the whole flow

WooCommerce 9.9 comes with conditional Checkout fields, written in PHP via JSON Schema, this enables you to only show/required on the exact moment, like having certain product types/ids, a country, shipping method, email type. Here's a demo showing different fields per delivery

@se_nadir Yes, exactly. And only in the cart, above `Check delivery options`. The client request is to make the shipping calculation only require a ZIP code. (The store only supports US-based customers.)

@gregsvn This is now only for additional fields, are you looking to remove core fields? and only from shipping but not billing?

Sometimes on personal projects, I spell “colour” the Canadian way in variable names, as a treat. Then I realize I still need to spell it the American way in CSS properties and everywhere else, and I feel regret.

I just sliced an image for an HTML email, and I feel young again. But I don’t miss doing this.

@adamwathan Thank you—very much looking forward to it! I really like the idea of typography themes as part of Tailwind Plus, too. (Not expecting that to arrive right away, but looking forward to the day it does!)

@gregsvn @davebloomdev Hoping to finish this and tag a release within the next week or two for reference 👍

Yesterday I stumbled upon the new `css-only` branch in the Tailwind Typography repository, and I’m still feeling excited about what this will mean for _tw. (My only worry is that any videos I record about Tailwind Typography before its CSS-only release will become outdated almost immediately.)

@davebloomdev This is the branch: github.com/tailwindlabs/t… Adam mentioned his plans here: x.com/adamwathan/sta… (Sorry, just seeing your question now!)

@gregsvn Wait what's that?

You’re very welcome! You don’t need to sync the hex value to `tailwind-theme.css`, but if you add a new colour slug, you’ll need to add a corresponding line there with a `var()` matching the one WordPress will create. I talked about this a bit in the release notes, but it’s possible I should go into more detail in the documentation: #h-supporting-theme-json-variables-in-tailwind-4" target="_blank" rel="nofollow noopener">underscoretw.com/release-notes/…

@gregsvn Thanks for the update Greg! Do I now manually add my custom colors to tailwind-theme.css? I added them to theme.json but the extra ones I added (like "secondary-dark") were not automatically added to tailwind-theme.css.

Oh, and also, I have a Bluesky account now, if that’s a place you also go: bsky.app/profile/gregsu…

I’m going to revisit the documentation and inline comments after I get a sense of the questions people have over the next few weeks, but for now you can view the updates on GitHub, or generate a theme for your next project at underscoretw.com. Any feedback or questions would be much appreciated!

I’ll do a proper thread about it tomorrow, but I just pushed Tailwind 4 support in _tw to GitHub and deployed it to the generator! If anyone has time to take a look, I’d love to hear feedback.