← Back to context

Comment by ZeroConcerns

3 days ago

That's sad to hear, if true, and I'd have gladly paid for Tailwind if they'd had a "OK, so you use our CSS indirectly" program in place. I'm aware of "Tailwind Plus", but that seems to be React-only, and thus the opposite of where I want to be.

It's not React only. It has pure/regular HTML, React, and Vue. I have mainly only used the pure HTML personally as I use Phoenix/LiveView for most of my stuff, and it works phenomenally well and is very copy/paste friendly. The UI/console they provide is also top notch. For others who do use React, the React stuff also worked well too for one project I did that was a SPA.

It's well worth the money IMHO.

  • I just had a more-detailed look, and I'm not sure where I'd find the pure-HTML stuff? From https://tailwindcss.com/plus/templates/pocket#pricing:

    "Our website templates are built using Next.js, so all of the markup is written using React"

    And the individual components that make up these templates don't seem to have pricing attached, nor non-React usage examples?

    • Oh, yeah the templates are React/Next.js, but the components and things are not (they are what I described above). Templates are great but 95% of the value I get is the components and things

      5 replies →

You can actually use tailwind via the script tag in a plain HTML file. Not for production, but great for whipping up prototypes

  • Indeed, I've done this quite a few times myself. It's also a phenomenal way to be able to start poking at UI immediately without messing with build pipelines or anything besides just pointing your browser at `file:///...`. Then if the prototype is useful it's very easy to just delete the script tag and get it set up "properly" for a prod build and you know your prototype will pretty much "just work"