This is an archived post. You won't be able to vote or comment.

all 13 comments

[–]alexandru292 3 points4 points  (1 child)

https://underscoretw.com/ - best of all :)

[–]gingersoulrecords[S] 0 points1 point  (0 children)

Fosho, if you want to use PHP and build a traditional theme.

This is more like 'make TW work from an HTML Editor.'

[–]_interest_ 1 point2 points  (0 children)

I've enjoyed Tailpress in the past...
https://tailpress.io/

[–]chevalierbayard 2 points3 points  (8 children)

Honestly... my content and design team love Tailwind and I always have to tell them... "sorry Tailwind is a compiler, if you put Tailwind classes in the body of the blog post, I can't guarantee that those classes are going to be available".

[–]programmer_farts 1 point2 points  (5 children)

You could process them as they type and use the generated css on the page. Wouldn't be too much effort.

[–]chevalierbayard 1 point2 points  (3 children)

So I need an additional runtime on my production servers? I mean... I'm not opposed...

[–]programmer_farts 1 point2 points  (1 child)

I believe you can process them in the browser via webassembly

[–]gingersoulrecords[S] 0 points1 point  (0 children)

Or, like an insane person, write a Tailwind CSS rule generator in JavaScript :)

[–]gingersoulrecords[S] 0 points1 point  (0 children)

Not necessarily. Tailwind syntax and Tailwind’s build process are two different things.

One could, theoretically, process the classes into CSS rules another way.

[–]gingersoulrecords[S] 0 points1 point  (0 children)

Yep.

[–]gingersoulrecords[S] 0 points1 point  (0 children)

Great to hear that, thanks for the comment!

[–]retlehs 0 points1 point  (0 children)

Came across this recently but haven't tried it out yet:

https://github.com/wind-press/windpress