Skip to content

Commit

Permalink
update 'customization' in README (jekyll#79)
Browse files Browse the repository at this point in the history
  • Loading branch information
ashmaroli authored and DirtyF committed Oct 29, 2018
1 parent e462092 commit 78a21b3
Showing 1 changed file with 29 additions and 1 deletion.
30 changes: 29 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,35 @@ The site's default CSS has now moved to a new place within the gem itself, [`ass
- Copy the `assets/` folder from there into the root of `<your-site>`
- Change whatever values you want, inside `<your-site>/assets/main.scss`

--

When you override only a minima-sass-partial, it is not automatically imported because we're still importing the `minima.scss` within the theme-gem and that subsequently imports the partials with respect to itself, i.e. partials within the gem. Hence you should either include a *copy of `minima.scss` from the gem* inside the `_sass` directory at source or the overriding `/assets/main.scss` file should explicitly import the edited partial. :
e.g. To have an **edited** `_syntax-highlighting.scss` be rendered, you should either have

```sass
/* <your-site>/assets/main.scss */
@import "minima";
@import "minima/syntax-highlighting";
```
or
your `<your-site>/_sass/` should look like:

```
.
├── minima.scss
├── minima
| ├── _syntax-highlighting.scss
```

To have your CSS overrides in sync with upstream changes released in future versions, collect all your overrides into a single partial sass-file and then import that partial after importing minima, like so:

```sass
/* <your-site>/assets/main.scss */
@import "minima";
@import "my_overrides";
```


### Customize navigation links

Expand Down

0 comments on commit 78a21b3

Please sign in to comment.