Permalink
Browse files

Edited railties/guides/source/asset_pipeline.textile via GitHub

  • Loading branch information...
1 parent 8bb7c86 commit 04daede85d9857e88a0e89019ec6a8ef136330b4 @TheEmpty TheEmpty committed Jun 18, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 railties/guides/source/asset_pipeline.textile
@@ -21,7 +21,7 @@ In previous versions of Rails, all assets lived under the +public+ directory in
This is not to say that assets can (or should) no longer be placed in +public+. They still can be, they will just be served by the application or the web server which is running the application and served just like normal files. You would only use +app/assets+ if you wish your files to undergo some pre-processing before they are served.
-When a scaffold or controller is generated for the application, Rails will also generate a JavaScript (JS) file (or CoffeeScript if the +coffee-script+ gem is in the +Gemfile+) and a Cascade Style Sheet (CSS) file (or SCSS if +sass-rails+ is in the +Gemfile+) file for that controller. For example, if a +ProjectsController+ is generated, there will be a new file at +app/assets/javascripts/projects.js.coffee+ and another at +app/assets/stylesheets/projects.css.scss+. You should put any JavaScript or CSS unique to the controller insider their respective asset files.
+When a scaffold or controller is generated for the application, Rails will also generate a JavaScript (JS) file (or CoffeeScript if the +coffee-script+ gem is in the +Gemfile+) and a Cascade Style Sheet (CSS) file (or SCSS if +sass-rails+ is in the +Gemfile+) file for that controller. For example, if a +ProjectsController+ is generated, there will be a new file at +app/assets/javascripts/projects.js.coffee+ and another at +app/assets/stylesheets/projects.css.scss+. You should put any JavaScript or CSS unique to a controller inside their respective asset files.
h4. Asset Organization

0 comments on commit 04daede

Please sign in to comment.