Tailwind transition overthinking

[asvae]

We decided to have 1st class tailwind support, so we'd scrape some of our helpers, and just link tailwind solutions instead. That's not an easy process so let's think it over.

• Typography - there is a typography plugin for tailwind (https://play.tailwindcss.com/uj1vGACRJA?layout=preview), also typography doesn't go out of the box for tailwind. So we probably can keep our solution and it's overall a good fit
• Colors - not exactly clear on implementation, but we're probably looking to integrate tailwind config with vuestic config.
• Breakpoints - we're looking for some kind of integration with tailwind solution. As we can't rely completely on tailwind here.
• Grid - We should separate smart (vuestic) grid classes and tailwind. Both could be used at once though.
• Dark theme - again, would be nice to have a way to combine both, but not sure if that's possible.
• Reset could also become a bit of an issue. (maybe not - if we don't use it for vuestic components at all)

---

• Might make sense to introduce vuestic-tailwind-plugin to keep all tailwind integration in one place. Or maybe as an optional service?

Relevant issues

These should ideally be handled in context of this issue.

• #665
• #731
• #764

[asvae]

We decided to use tailwind and not to use tailwind for vuestic component.

[asvae]

[m0ksem]

@asvae, @aluarius done?

[aluarius]

Imo yes, can't see anything else to do here.