TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

add instructions for adding additional manifests

Browse Source
This commit is contained in:
Patrick Sharp 2012-04-09 08:54:02 -05:00
parent 8f25db9067
commit f28f1d70b3
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
guides/source/asset_pipeline.textile
View File

@ -290,7 +290,11 @@ In this example +require_self+ is used. This puts the CSS contained within the f
NOTE. If you want to use multiple Sass files, you should generally use the "Sass +@import+ rule":http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#import instead of these Sprockets directives. Using Sprockets directives all Sass files exist within their own scope, making variables or mixins only available within the document they were defined in.
You can have as many manifest files as you need. For example the +admin.css+ and +admin.js+ manifest could contain the JS and CSS files that are used for the admin section of an application.
You can have as many manifest files as you need. For example the +admin.css+ and +admin.js+ manifest could contain the JS and CSS files that are used for the admin section of an application. In order for the pipeline to know about the additional manifest, it has to be added to application.rb.
<plain>
config.assets.precompile += %w( admin.css )
</plain>
The same remarks about ordering made above apply. In particular, you can specify individual files and they are compiled in the order specified. For example, you might concatenate three CSS files together this way: