Tailwind

[tiborp]

Hi Brett,

Not an issue, but I noticed you closed all Tailwind related branches. Coincidently I also noticed that WebDevStudios is working on their wd_s theme to support Tailwind; thought you might want to give that a look (since I still think it would be nice to have a Tailwind-supporting version of Luxe ;-)):

https://github.com/WebDevStudios/wd_s/tree/feature/tailwind

Cheers, Tibor

[brettsmason]

Hey Tibor

Yeah I think I saw Sami share that on Twitter - interesting!
I experimented quite a lot with a utility heavy approach in several clients sites.
What I struggled with was getting a balance between utility only vs a healthy mix.
I'm also a little weary of getting too dependent on another CSS framework again (like I have previously with Foundation).

In the end I think Tailwind might be a little too far for me personally (in a WordPress context anyway).
It wouldn't be too much work to get it added to the build pipeline, but my time is limited at the moment. I could potentially have a forked version that was Tailwind only.

I have been considering a theme rebuild/new theme for a while now after using Luxe on so many client projects.
There are some pain points that I'd like to address, and also simplify things a little (considering dropping HC too now that you can pass data via get_template_part and development has all but stopped).

If you have any issues you've had and would like to air them do let me know 😄

[mattradford]

Apologies jumping in and pimping my own code, but @tiborp you may be interested in a Tailwind starter theme I've been working on, Mountain Goat. I've just updated to Tailwind 2.

The rationale was to have a basic starter for sites with simple content, making sure that it's block editor compatible (as much as it can be given the moving target...). It already uses some code from the orignal Tailwind NPM package, so thanks for that @brettsmason 👍

[tiborp]

@mattradford Thanks for the tip! Although, like @brettsmason, I am also not sure if I want to go full Tailwind, there's always some nice things to learn from. I will definitely play with it sometime!

[brettsmason]

Hey @mattradford no worries thanks for chiming in!

I had seen your Mountain Goat theme when I noticed you forked my original Tailwind package - it looks very nice, I'll make sure to give it a try when I get some time 👍

I've worked with Tailwind on three WordPress projects now (two were WooCommerce too) and I'm not 100% sold on it just yet. I noticed a considerable hit in compliation speed which was a pain, and with version 2 they dropped IE11 support, which unfortunately I still need to support for my day job (hopefully that will change at some point!).

Would love to hear about your experience with it though in a WordPress environment.

[mattradford]

@brettsmason Like you I"m not 100% sold. It works fine. Compilation speed is ok with Laravel Mix, Tailwind 3 will introduce JIT compilation, so that will also help.

Conceptually, I like the idea of a design API, but Tailwind in operation feels restrictive to me. Really, I want to tell a designer the grid, some margin/padding and typography baselines, and let them have at it - then have that baked into a base theme that's ready to translate their design into code. That doesn't need all of Tailwind. So yeah, I maintain that Tailwind is just fine for people who don't like to write or want to think about CSS - but I do.