📝 Tailwind to Webstudio Copy/Paste

[itsNintu]

This feature will enable the direct copying of Tailwind CSS templates and layouts into Webstudio’s interface.

[brandondrew]

Will TailwindCSS NOT be supported on Webstudio for some reason? It would be much nicer to have the option to use Tailwind rather than only be able to convert from Tailwind.

[kof]

@brandondrew tailwind is literally not necessary in webstudio, it is solving problems with authoring css in code, we don't have the same problems, webstudio design tokens solve most of them already, we just need an easy way to reuse stuff that exists written in tailwind

[brandondrew]

Yes, but if (a) I'm already familiar with Tailwind and (b) I might export my site to be hosted elsewhere, then that might not help me.

One thing I like so much about Webstudio is that you're not locking anyone to your product. But if you don't support using the tools we already know and love, that's going to be a big detraction.

[kof]

Yes, but if (a) I'm already familiar with Tailwind and (b) I might export my site to be hosted elsewhere, then that might not help me.

Yes I agree generally with the sentiment, though bringing coding habbits to a visual platform that tries to get rid of the problems with code is kinda not a good idea.

On the other hand exporting to tailwind is def not a bad idea because that's where coding habbits are useful again if someone wants to take the exported code and use it.

Since tailwind classes a really super generic, we can potentially import and export while we don't need to be working with them visually

[brandondrew]

Yes I agree generally with the sentiment, though bringing coding habbits to a visual platform that tries to get rid of the problems with code is kinda not a good idea.

Okay, this is confusing to me. Perhaps I misunderstood what you're trying to build. What do you consider "the problems with code"?

[kof]

Tailwind is a hack that solves limitations around authoring CSS. You don't have that problem in Webstudio!

[brandondrew]

Well, I haven't used Webstudio, so I'll reserve judgement, but that's a pretty extremely negative opinion of something that a lot of people find very useful. Maybe you're right, but I certainly can't see it yet.

[kof]

@brandondrew I don't mean it emotionally negative, I am saying it from technical perspective.

[gumush]

+1 Vote

[Zmove]

Don't really see the added value of using tailwind in a Webstudio project. Projects that can really take benefits from using tailwind are molecular components based project (generally pretty big ones). Using tailwind outside of that scope is just adding complexity and difficulty to maintain.

I understand kof when he say that Webstudio nature make the use of tailwind useless. Sure it could be a useful addition for some people wanting to use tailwind against all odd, but there are soooo many more important to develop that it would be a very very tiny priority to me

[kof]

@Zmove primary objective is ability to copy-paste tailwind with html/jsx, which is a handy way to use all the ecosystem of tailwind templates

[brandondrew]

The more WebStudio can interoperate with normal & widespread web technologies, and normal & widespread workflows, the more successful it is likely to be. Conversely, the more it is viewed as a walled garden by those creating it, the more it is likely to be treated as a walled garden that others choose not to enter.

I hope you will make WebStudio interoperate smoothly with code written elsewhere (including code using Tailwind utility classes).

[brandondrew]

Don't really see the added value of using tailwind in a Webstudio project.

The fact that a feature is not useful to you does not mean it is useful to others.