Ok, Ive been looking into this a bit.
Not too much.
As, it’s bending my head in half.
I mean, WHY!>?
Really, as a non pro, web tinkerer, this really really looks like a lot of stuff I really dont want to have to do, post css, build tools… installing NPM on someone elses computer Im currently using…lots of Config files,
… to end up with a pile of ,what looks like … inline classes!
I am struggling to find the real overall advantage of this malarky, over,
for instance… inline styles
Your own styles
I could go on.
It just looks way too complex (not complicated)
for simple web pages
Could someone show me some whizz bang wow of using this as frankly Im underwhelmed.
Its awesome that PG has new tools, but I think this one might be superflous to my requirements.
I cant even figure out HOW to use it in Pinegrow…
on our PG website, with regards Tailwind, under the heading
its Your workflow
Tailwind Visual Editor works with your existing web projects and integrates into your workflow. Tailwind Visual Editor opens and saves standard HTML files. It makes no assumptions about your build process, so you can use it CDN, PostCSS, Gulp, Webpack and so on.
whcih sounds kind of promising, and I know PG uses Node… but… do I have to install NPM?
As I cant on this machine right now.
And this one
under method 1, install from cdn then says
Unfortunately going down this route will lock you out of a bunch of functionality that you may want to familiarize yourself with including:
- Unable to customize the default theme
- Unable to install third-party plugins
- Unable to use directives
- Unable to enable features (ie group-hover)
How, what is actually required, WHY>?.. it just seems a convoluted way to end up adding a tonne of writing/utility classes…
I dont quite get the whole thing.
Thanks if anyone takes the time to help out with this or point out some decent explanatory resources.