Until now, trying to style an article, document, or blog post with Tailwind has been a tedious task that required a keen eye for typography and a lot of complex custom CSS.
By default, Tailwind removes all of the default browser styling from paragraphs, headings, lists and more. This ends up being really useful for building application UIs because you spend less time undoing user-agent styles, but when you really are just trying to style some content that came from a rich-text editor in a CMS or a markdown file, it can be un lien dans le texte unintuitive.
We get lots of complaints about it actually, with people regularly asking us things like:
Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?Why is Tailwind removing the default styles on my h1 elements? How do I disable this? What do you mean I lose all the other base styles too?
“Typography is pretty important if you don’t want your stuff to look like trash. Make it good then it won’t be bad.

Listes
Nested lists basically always look bad which is why editors like Medium don’t even let you do it, but I guess since some of you goofballs are going to do it we have to carry the burden of at least making it work.
- Nested lists are rarely a good idea
- You might feel like you are being really « organized » or something but you are just creating a gross shape on the screen that is hard to read.
- Nested navigation in UIs is a bad idea too, keep things as flat as possible.
- Nesting tons of folders in your source code is also not helpful.
- Since we need to have more items, here’s another one.
- I’m not sure if we’ll bother styling more than two levels deep.
- Two is already too much, three is guaranteed to be a bad idea.
- If you nest four levels deep you belong in prison.
- Two items isn’t really a list, three is good though.
- Again please don’t nest lists if you want people to actually read your content.
- Nobody wants to look at this.
- I’m upset that we even have to bother styling this.
When a heading comes after a paragraph, we need a bit more space, like I already mentioned above. Now let’s see what a more complex list would look like.
- I often do this thing where list items have headings.
- For some reason I think this looks cool which is unfortunate because it’s pretty annoying to get the styles right.
- I often have two or three paragraphs in these list items, too, so the hard part is getting the spacing between the paragraphs, list item heading, and separate list items to all make sense. Pretty tough honestly, you could make a strong argument that you just shouldn’t write this way.
- Since this is a list, I need at least two items.
- I explained what I’m doing already in the previous list item, but a list wouldn’t be a list if it only had one item, and we really want this to look realistic. That’s why I’ve added this second list item so I actually have something to look at when writing the styles.
- It’s not a bad idea to add a third item either.
- I think it probably would’ve been fine to just use two items but three is definitely not worse, and since I seem to be having no trouble making up arbitrary things to type, I might as well include it. I’m going to press Enter now.
Tableaux
| Wrestler | Origin | Finisher |
| Cedric Kelly | Front-end Developer | 2012/03/29 |
| Cedric Kelly | Front-end Developer | 2012/03/29 |
| Wrestler | Origin | Finisher |
| Cedric Kelly | Front-end Developer | 2012/03/29 |
| Cedric Kelly | Front-end Developer | 2012/03/29 |
Niveaux de titres
Titre 1
Font size: 30px | Line height: 36px | Tracking: -2%
Titre 2
Font size: 26px | Line height: 32px | Tracking: -2%
Titre 3
Font size: 24px | Line height: 30px | Tracking: -2%
Titre 4
Font size: 20px | Line height: 26px | Tracking: -2%
Titre 5
Font size: 16px | Line height: 22px
Titre 6
Font size: 14px | Line height: 20px