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 surprising and 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?

We hear you, but we're not convinced that simply disabling our base styles is what you really want. You don't want to have to remove annoying margins every time you use a p element in a piece of your dashboard UI. And I doubt you really want your blog posts to use the user-agent styles either — you want them to look awesome, not awful.

That's why today we're excited to release @tailwindcss/typography — a plugin that gives you what you actually want, without any of the downside of doing something stupid like disabling our base styles.

It adds a new set of prose classes that you can slap on any block of vanilla HTML content and turn it into a beautiful, well-formatted document:

<article class="prose lg:prose-xl">  <h1>Garlic bread with cheese: What the science tells us</h1>  <p>    For years parents have espoused the health benefits of eating garlic bread with cheese to their children, with the    food earning such an iconic status in our culture that kids will often dress up as warm, cheesy loaf for Halloween.  </p>  <p>    But a recent study shows that the celebrated appetizer may be linked to a series of rabies cases springing up around    the country.  </p>  <!-- ... --></article>

So how does it actually look? Well you're looking at it right now — we use it to style the content on this very blog!

Check out the documentation to learn more and try it out today.

Want to talk about this post? Discuss this on GitHub →