TailwindCSS v2 support instruction in Docs?

[natac13]

Could I add the following instructions to the Styling section of the docs to add TailwindCSS Support? Or would you rather not?

#2961 (comment)

[kvnxiao]

The instructions from the comment I wrote above is still a workaround, and while I'm not affiliated with the project I would still like to interject with my opinion that if anything is to be currently added to the docs please advertise it as such (a workaround). I'm hoping Docusaurus supports it natively sometime in the future without anyone having to fiddle with additional plugin config files.

[slorber]

Agree

As I've never used Tailwind myself it's hard for me to claim that Docusaurus actually support tailwind 😅

The plan is more to build a tailwind theme, and then claim official tailwind support ;)

[natac13]

So the PR you would be looking for is to create a new theme folder except all styling done with tailwindcss?

[slorber]

Yes, and the goal is that switching themes should be easy, and they'd share the same config and UX.
#3522

[vjpr]

Another option for tailwind support is twin.macro. Very easy to setup. Only one minor issue for content plugins (plugin-content-docs) (with workaround) #4035.