A plugin that provides a set of prose classes you can use to add beautiful typographic defaults to any vanilla HTML you don't control (like HTML rendered from Markdown, or pulled from a CMS).
<article class="prose lg:prose-xl">
{{ markdown }}
</article>Install the plugin from npm:
# Using npm
npm install @tailwindcss/typography
# Using Yarn
yarn add @tailwindcss/typographyThen add the plugin to your tailwind.config.js file:
// tailwind.config.js
module.exports = {
theme: {
// ...
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}If you need to pull in these styles via CDN, you can do so using services like UNPKG or jsDeliver:
<!-- From UNPKG -->
<link
rel="stylesheet"
href="https://unpkg.com/@tailwindcss/typography@0.2.x/dist/typography.min.css"
/>
<!-- From jsDelivr -->
<link
rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/@tailwindcss/typography@0.2.x/dist/typography.min.css"
/>To use these styles alongside the rest of Tailwind via CDN, we recommend pulling in each layer separately so you can put the styles in the correct order:
<link rel="stylesheet" href="https://unpkg.com/tailwindcss@^1.5/dist/base.min.css" />
<link rel="stylesheet" href="https://unpkg.com/tailwindcss@^1.5/dist/components.min.css" />
<link
rel="stylesheet"
href="https://unpkg.com/@tailwindcss/typography@0.2.x/dist/typography.min.css"
/>
<link rel="stylesheet" href="https://unpkg.com/tailwindcss@^1.5/dist/utilities.min.css" />Now you can use the prose classes to add sensible typography styles to any vanilla HTML:
<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>Size modifiers allow you to adjust the overall size of your typography for different contexts.
<article class="prose prose-xl">
{{ markdown }}
</article>Five different typography sizes are included out of the box:
| Class | Body font size |
|---|---|
prose-sm |
0.875rem (14px) |
prose |
1rem (16px) |
prose-lg |
1.125rem (18px) |
prose-xl |
1.25rem (20px) |
prose-2xl |
1.5rem (24px) |
Everything about the provided size modifiers has been hand-tuned to look as beautiful as possible, including the relationships between font sizes, heading spacing, code block padding, etc. Just like the Tailwind color palettes, none of these styles are based on naive mathematical formulas, and have been hand-crafted by professional designers.
Size modifiers are designed to be used with the multi-class modifier pattern and must be used in conjunction with the base prose class:
<!-- Will not work -->
<article class="prose-lg">
{{ markdown }}
</article>
<!-- Always add the `prose` class -->
<article class="prose prose-lg">
{{ markdown }}
</article>None of the sizes are automatically responsive, but responsive variants are provided for each size modifier so you can easily change the typography size at different breakpoints:
<article class="prose prose-sm sm:prose lg:prose-lg xl:prose-xl">
{{ markdown }}
</article>Since the typography styles are added to the components layer and Tailwind only purges utilities by default, you will notice that even with the purge option configured in your tailwind.config.js file, all of the typography styles still remain in your final CSS.
If you'd like to purge unused typography styles, you'll need to use the mode: 'all' option in your purge configuration:
// tailwind.config.js
module.exports = {
purge: {
mode: 'all',
content: [
// Paths to your templates here...
],
},
}It's important to note that if you are using markdown for any of your source files (perhaps you're working on a blog or similar), that you need to be careful not to accidentally purge styles you actually need.
Markdown files for example contain no actual h2, blockquote, strong, etc. elements, so PurgeCSS will remove those styles because it doesn't think you need them.
You have two options for solving this:
-
Safelist all of the plain HTML elements you need in your config file:
// tailwind.config.js module.exports = { purge: { mode: 'all', content: [ // Paths to your templates here... ], options: { whitelist: ['h1', 'h2', 'h3', 'p', 'blockquote', 'strong' /* etc. */], }, }, }
-
Use a custom extractor to compile your markdown files before scanning them for tokens. This is more complicated but it is what we do for the Tailwind blog for example.
The customization API is currently extremely low-level in order to be as flexible as possible. We will be introducing higher-level configuration options over time as we learn what types of customizations are most common.
To customize the styles provided by this plugin, add your overrides under the typography key in the theme section of your tailwind.config.js file:
// tailwind.config.js
module.exports = {
theme: {
typography: {
default: {
css: {
color: '#333',
a: {
color: '#3182ce',
'&:hover': {
color: '#2c5282',
},
},
},
},
},
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}Like with all theme customizations in Tailwind, you can also define the typography key as a function if you need access to the theme helper:
// tailwind.config.js
module.exports = {
theme: {
typography: (theme) => ({
default: {
css: {
color: theme('colors.gray.800'),
// ...
},
},
}),
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}Customizations should be applied to a specific modifier like default or xl, and must be added under the css property. Customizations are authored in the same CSS-in-JS syntax used to write Tailwind plugins.
It's important to note that all customizations are merged with the defaults. If you'd like to completely override a provided size modifier, you can do so by disabling that modifier so the default styles are not included.
See the default styles for this plugin for more in-depth examples of configuring each modifier.
Many styles (for example colors, font weight, and text decoration) are shared between all size modifiers, and are therefore defined only for the default modifier, since modifiers are designed to be used with the multi-class modifier pattern.
If you'd like to customize these sorts of styles, do so using the default modifier:
// tailwind.config.js
module.exports = {
theme: {
typography: {
default: {
css: {
color: '#333',
strong: {
fontWeight: '800',
},
// ...
},
},
},
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}You can add a new modifier by creating a new key in the typography section of your theme and providing your own styles under the css key:
// tailwind.config.js
module.exports = {
theme: {
typography: {
'3xl': {
css: {
fontSize: '1.875rem',
h1: {
fontSize: '4rem',
},
// ...
},
},
},
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
}Each size modifier comes with a baked in max-width designed to keep the content as readable as possible. This isn't always what you want though, and sometimes you'll want the content to just fill the width of its container.
In those cases, all you need to do is add max-w-none to your content to override the embedded max-width:
<div class="grid grid-cols-4">
<div class="col-span-1">
<!-- ... -->
</div>
<div class="col-span-3">
<article class="prose max-w-none">
{{ markdown }}
</article>
</div>
</div>If you'd like to completely disable any size modifiers (either for file size reasons or because you'd like to completely redefine that modifier), you can do so using the modifiers option when including the plugin:
// tailwind.config.js
module.exports = {
theme: {
// ...
},
plugins: [
require('@tailwindcss/typography')({
modifiers: ['sm', 'lg'],
}),
// ...
],
}This option acts as a safelist, so you can list only the modifiers you'd actually like included and the others will be removed.
The default modifier is always included and cannot be disabled.
If you'd like to disable the responsive variants for any reason, you can do so by setting the typography key to an empty array in the variants section of your tailwind.config.js file:
// tailwind.config.js
module.exports = {
theme: {
// ...
},
plugins: [
require('@tailwindcss/typography'),
// ...
],
variants: {
typography: [],
},
}