-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tailwind css 3.0 should be added to Docusaurus #624
Comments
I tried adding it here, but that was Tailwind 2.0, which is wrong for us. This highlights the issue that this is an awkward way to go about this though. |
I tried this but didn't get it to work: https://dev.to/sajclarke_62/using-tailwindcss-v3-in-docusaurus-in-5-steps-5c26 There are also some examples around here: https://codesandbox.io/s/rr0qy?file=/plugins/docusaurus-tailwindcss-loader I'm really not great with webpack stuff. |
Sorry, I did notice this and started trying to fix it. Docusaurus is a bit of a pain because it hides a lot of its details and doesn't have a functioning logger. But hopefully I'll get this one patched soon |
Actually, I realized that we don't want to import Tailwind.css to Docusaurus. Instead we want roughly this: |
Should this be closed too? |
Yea, thanks for flagging. |
We recently added tailwind to the components library. One problem though is that it's not being read by the other dependent libraries, specifically, docusaurus.
See:
https://deploy-preview-622--squiggle-documentation.netlify.app/playground
Even better could be a system that loads all the css we use in the components library, and brings that to places that use the styling.
This should include importing the
form
library,@tailwindcss/forms
This plugin would also be useful:
https://tailwindcss.com/docs/typography-plugin
@tailwindcss/typography
Ideally, this plugin would be used in the documentation. Right now, the headings were removed from the documentation (in that they're not large/styled, which is suboptimal)
Some relevant threads:
facebook/docusaurus#2961
The text was updated successfully, but these errors were encountered: