A lot of people disagree with Tailwind's design philosophy on both the developer and consumer side of the code (i.e. DX and UI), so it's questionable what "real project" and "time saver" really mean; ironically, I question that your definition of "real project" even included a team with design chops.
I can see how that would also be a benefit to a "SAAS starter pack" where you have a small team wearing many hats, probably people with a familiarity with CSS but not experts. The code base in these early stage startups and side projects is going to be small and you want to move quickly. Tailwind is great at that.
However if you have a frontend team of CSS experts to draw upon, the benefits of Tailwind are fewer and the downsides are greater - your CSS people will not enjoy having your classes named things like "px-2 py-1 rounded border bg-blue-800 text-white font-bold hover:bg-blue-500" rather than just "btn btn-primary". They can iterate fast anyway and they will probably leave more maintainable HTML and CSS/SCSS in the long run.
However I'd still be interested if any large teams (with correspondingly large code bases) have made Tailwind work for them.
“No, you have never worked on a real project!” :)
Both can be real projects, without quotation marks. I’m constantly surprised that there are so many different ways and processes to build a website; and people who think theirs is the best.
If we're going to discard some projects as real, a pretty easy filter is "were multiple people required to build it". People who need Tailwind to provide their design system like Tailwind, but they are usually working on very small-scale projects they're unlikely to maintain and upgrade like a project with real users, real design, and multiple engineers would. And a pretty easy proxy for the latter type of shop is "do you have people who aren't even front-end engineers doing your design", and that commenter was displaying all those signals to me.
The right path is having tools the team is currently, or will be productive with, and isn't the markedly wrong tool for a type of job.
Html is split into components or views or partials. Links are inside loops etc.
You save time every time you don’t have to think about coming up with a new class name or how it might affect the hierarchy.
I totally understand it feels weird to begin with but on a major project you never worry that your css tweaks might affect some other obscure part of the site.
