No description
I still want to explore this again in the near future but there are some trade-offs that I need to think about more before I actually put this into a proper release and make it impossible to revert without a major version update. The main one that I literally just ran into is that if the end user has an old version of Inter installed locall (say one from before Inter had light weights), things can look pretty bad. |
||
|---|---|---|
| .github | ||
| __tests__ | ||
| dist | ||
| jest | ||
| scripts | ||
| src | ||
| stubs | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .npmignore | ||
| .travis.yml | ||
| base.css | ||
| components.css | ||
| defaultConfig.js | ||
| defaultTheme.js | ||
| LICENSE | ||
| package.json | ||
| plugin.js | ||
| README.md | ||
| resolveConfig.js | ||
| screens.css | ||
| tailwind.css | ||
| utilities.css | ||
| yarn.lock | ||
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
Discuss Tailwind CSS on GitHub
For casual chit-chat with others using the framework:
Join the Tailwind CSS Discord Server
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.