Skip to content

Commit

Permalink
remove leading slash from Sass file location (#8021)
Browse files Browse the repository at this point in the history
Merge pull request 8021
  • Loading branch information
Gareth Mcshane committed Feb 24, 2020
1 parent 3e440a9 commit 331d3f3
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/_docs/step-by-step/07-assets.md
Expand Up @@ -36,7 +36,7 @@ You could use a standard CSS file for styling, we're going to take it a step
further by using [Sass](https://sass-lang.com/). Sass is a fantastic extension
to CSS baked right into Jekyll.

First create a Sass file at `/assets/css/styles.scss` with the following content:
First create a Sass file at `assets/css/styles.scss` with the following content:

```sass
---
Expand All @@ -51,7 +51,7 @@ directory (`_sass/` by default which is directly under root folder of your websi
At this stage you'll just have a main css file. For larger projects, this is a
great way to keep your CSS organized.

Create a Sass file at `/_sass/main.scss` with the following content:
Create a Sass file at `_sass/main.scss` with the following content:

```sass
.current {
Expand All @@ -70,7 +70,7 @@ Open `_layouts/default.html` and add the stylesheet to the `<head>`:
<head>
<meta charset="utf-8">
<title>{{ page.title }}</title>
<link rel="stylesheet" href="/assets/css/styles.css">
<link rel="stylesheet" href="assets/css/styles.css">
</head>
<body>
{% include navigation.html %}
Expand All @@ -80,7 +80,7 @@ Open `_layouts/default.html` and add the stylesheet to the `<head>`:
```
{% endraw %}

The `styles.css` referenced here is generated by Jekyll from the `styles.scss` you created earlier in `/assets/css/`.
The `styles.css` referenced here is generated by Jekyll from the `styles.scss` you created earlier in `assets/css/`.

Load up <a href="http://localhost:4000" target="_blank" data-proofer-ignore>http://localhost:4000</a>
and check the active link in the navigation is green.
Expand Down

0 comments on commit 331d3f3

Please sign in to comment.