←back to thread

Vanilla JavaScript support for Tailwind Plus

(tailwindcss.com)
304 points ulrischa | 1 comments | 25 Jul 25 18:11 UTC | HN request time: 0s | source
Show context
bikeshaving ◴[25 Jul 25 19:02 UTC] No.44686961[source]▶
This is a exciting use-case for custom elements, and probably how tailwind should have been implemented from the start, but it’s hilariously a paid feature?! (https://tailwindcss.com/plus#pricing) Intuitively, I’d expect the custom elements to be free and the framework integrations to cost money.
replies(4): >>44686977 #>>44687096 #>>44687163 #>>44690620 #
gavinray ◴[25 Jul 25 19:03 UTC] No.44686977[source]▶
Tailwind Plus is a paid collection of UI components and templates.

TailwindCSS itself is meant to be nothing more than a styling tool, like Bootstrap...

replies(2): >>44687008 #>>44689417 #
bikeshaving ◴[25 Jul 25 19:05 UTC] No.44687008[source]▶
The title of the blog post mentions Tailwind Plus so I’m assuming it’s a paid feature. The ambiguity is probably intentional.
replies(1): >>44687074 #
Alupis ◴[25 Jul 25 19:08 UTC] No.44687074[source]▶
It's not very expensive, all things considered. $299 for a single-user perpetual license (includes all future updates too) or about $1k for a team license[1].

If it saves you a bunch of time writing and maintaining the sort of components they are showing off, probably worth it?

[1] https://tailwindcss.com/plus#pricing

replies(3): >>44687164 #>>44687639 #>>44687692 #
1. cschmatzler ◴[25 Jul 25 19:59 UTC] No.44687692{3}[source]▶
Yeah I strongly emphasise with them getting their money - the only problem with headless components being behind a paid license is that you cannot build a design system on top of them and open source it.