Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add scss to template engines #811

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add scss to template engines #811

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions source/localizable/basics/template-engine-options.html.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ ENGINE | FILE EXTENSIONS | REQUIRED LIBRARIES
Slim | .slim | slim
Erubis | .erb, .rhtml, .erubis | erubis
Less CSS | .less | less
SCSS | .scss | scss
Builder | .builder | builder
Liquid | .liquid | liquid
RDiscount | .markdown, .mkd, .md | rdiscount
Expand All @@ -55,3 +56,15 @@ Yajl | .yajl | yajl-ruby
Stylus | .styl | stylus

[Tilt]: https://github.com/rtomayko/tilt/


## When to use more than one file extension

You might be wondering when to use multiple file extensions like: `nav.scss.css` vs simply `nav.scss`. Only files which will be seen directly in the build process require the additional extension. In other words, if you plan to manage multiple `scss` files with `@import`, those imports should only use `.scss`.

```
stylesheets/
|- app.scss.css
|- partials/
| |- nav.scss // consumed with @import "nav";
```