You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Change: Allow sites to use local Sass files
This processes ".scss" files in the "assets/css" directory, allowing
downstream sites to use Sass as well as plain CSS.
* Also compile SCSS as templates
* Be explicit about style sheet extensions
* SCSS files are also templated
* Fix small typo introduced in css layout
* Fix rings.svg location
---------
Co-authored-by: Stefan van der Walt <stefanv@berkeley.edu>
Copy file name to clipboardExpand all lines: doc/content/getstarted.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,10 +72,10 @@ Example `config.yaml` files can be seen in [scientific-python.org](https://githu
72
72
73
73
### CSS
74
74
75
-
To customize styles, add CSS files to the `./assets/css/` directory.
76
-
It's recommended to put your customizations in a file named `custom.css`, but other `css` files added there will also be loaded.
75
+
To customize styles, add CSS (`.css`) and Sass (`.scss`) files to the `./assets/css/` directory.
76
+
It's recommended to put your customizations in a file named `custom.css`, but other `.css` and `.scss` files added there will also be loaded.
77
77
78
-
CSS files are compiled as Hugo templates, i.e. configuration variables from the `config.yaml` file can be accessed as `{{ .Site.Params.VARIABLE }}`.
78
+
CSS and SCSS files are compiled as Hugo templates, i.e. configuration variables from the `config.yaml` file can be accessed as `{{ .Site.Params.VARIABLE }}`.
0 commit comments