Getting set up
All of the components in Tailwind UI are designed for the latest version of Tailwind CSS, which is currently Tailwind CSS v3.2. To make sure that you are on the latest version of Tailwind, update via npm:
All of the examples in Tailwind UI rely on the default Tailwind CSS configuration, but some rely on additional first-party plugins like
When an example requires any plugins or configuration changes, it will be noted in a comment at the top of the example.
If you're new to Tailwind CSS, you'll want to read the Tailwind CSS documentation as well to get the most out of Tailwind UI.
Optional: Add the Inter font family
We've used Inter font family for all of the Tailwind UI examples because it's a beautiful font for UI design and is completely open-source and free. Using a custom font is nice because it allows us to make the components look the same on all browsers and operating systems.
You can use any font you want in your own project of course, but if you'd like to use Inter, the easiest way is to first add it via the CDN:
- Making sure components are properly keyboard accessible (dropdowns should be navigated with up/down arrow keys, modals should close when you press escape, tabs should be selected using the left/right arrow keys, etc.)
- Correctly handling focus (you shouldn't be able to tab to an element behind a modal, the first item in a dropdown should be auto-focused when the dropdown opens, etc.)
- Synchronizing ARIA attributes with component state (adding
aria-expanded="true"when a dropdown is open, setting
aria-checkedto true when a toggle is on, updating
aria-activedescendantwhen navigating the options in an autocomplete, etc.)
- ...and many other concerns.