summaryrefslogtreecommitdiff
path: root/docs/src/pages/guides/styling.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/src/pages/guides/styling.md')
-rw-r--r--docs/src/pages/guides/styling.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/src/pages/guides/styling.md b/docs/src/pages/guides/styling.md
index 98df62b8a..a42d759df 100644
--- a/docs/src/pages/guides/styling.md
+++ b/docs/src/pages/guides/styling.md
@@ -235,6 +235,14 @@ Now you're ready to write Tailwind! Our recommended approach is to create a `src
@tailwind utilities;
```
+Lastly, add it to your Astro page (or layout template):
+
+```astro
+<head>
+ <link rel="stylesheet" href={Astro.resolve('../styles/global.css')}>
+</head>
+```
+
As an alternative to `src/styles/global.css`, You may also add Tailwind utilities to individual `pages/*.astro` components in `<style>` tags, but be mindful of duplication! If you end up creating multiple Tailwind-managed stylesheets for your site, make sure you're not sending the same CSS to users over and over again in separate CSS files.
#### Migrating from v0.19