michael/astro
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add v20 documentation for bundling assets (#1262)

Browse source 
* Add v20 documentation for bundling assets

* 🛁 Revert bad doc

* 🛁 Address CR

* ✨ Use astro

* 🛁 Correct Link

* Update styling.md

Co-authored-by: Fred K. Schott <fkschott@gmail.com>
This commit is contained in:
Lachlan Young 2021-09-01 01:54:35 +10:00 committed by GitHub
parent 327d59287f
commit 5b24bd1768
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/src/pages/guides/styling.md
View file

@ -159,6 +159,17 @@ Now you're ready to write Tailwind! Our recommended approach is to create a `src
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
As of [version 0.20.0](https://github.com/snowpackjs/astro/releases/tag/astro%400.20.0), Astro will no longer bundle, build and process `public/` files. Previously, we'd recommended putting your tailwind files in the `public/` directory. If you started a project with this pattern, you should move any Tailwind styles into the `src` directory and import them in your template using [Astro.resolve()](/reference/api-reference#astroresolve):
```astro
<link
rel="stylesheet"
href={Astro.resolve("../assets/global.css")}
>
```
### Importing from npm
If you want to import third-party libraries into an Astro component, you can use a `<style lang="scss">` tag to enable [Sass][sass] and use the [@use][sass-use] rule.