aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/asset_pipeline.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'docrails/master'Xavier Noria2013-01-261-10/+10
|\ | | | | | | | | | | Conflicts: actionpack/lib/action_view/helpers/form_options_helper.rb guides/code/getting_started/app/controllers/comments_controller.rb
| * for recommended Apache configuration of asset pipeline, use <Location> ↵Erik Johnson2013-01-171-2/+2
| | | | | | | | | | | | | | | | instead of <LocationMatch>, to avoid unnecessary reg ex parsing and code <http://httpd.apache.org/docs/2.2/mod/core.html#location (recommended by @jja). - @erikj
| * update assets guide code stylingGosha Arinich2013-01-101-8/+8
| | | | | | | | | | | | * 1.9 hash syntax * proper formatting around one line blocks * do-end for multiline blocks
* | add asset pipeline guides section on implementing & registering own enginesGosha Arinich2013-01-101-1/+25
|/
* copy edits in assets guide [ci skip]Vijay Dev2012-12-211-23/+26
|
* Explain controller specific assets more thoroughlyDamian Galarza2012-12-171-17/+32
| | | | | | | | | The current section on controller specific assets does not really explain how the default application.css and application.js files generated by rails will work with controller specific assets and is a bit ambiguous. We should remind users that they will be included into their application by default but that they have the option to include them only where needed if they want and how this works with precompiling assets. [ci_skip]
* copy editing [ci skip]Vijay Dev2012-12-151-1/+1
|
* Add a small note about the compressing the file, and how that helps the ↵Anuj Dutta2012-12-131-1/+2
| | | | application.
* Remove references to Rails versions.Steve Klabnik2012-12-071-7/+3
| | | | | | | | There's no reason for guides to reference old behaviors. They should be current as of the versions of Rails that they ship with, and including older information just clutters thing. I discussed this change with @fxn and he agrees.
* Punctuation, capitalization, grammar fixes in rails guidesKatie Oldaker2012-12-071-5/+5
|
* Fixed grammar in a lot of guide prologues.Katie Oldaker2012-12-071-5/+5
|
* add a notice about loading assets in production modeTony Jian2012-12-051-1/+18
|
* Normalize on 'After reading this guide, you will know:'Steve Klabnik2012-11-291-1/+2
| | | | | We have three or four different introduction sentences to the guides. After this commit, we use the same one everywhere.
* Asset Pipeline: add 'the'Steve Klabnik2012-11-291-2/+2
| | | | | | Some guides work without 'the'. For instance, 'Migrations' or 'Form Helpers.' But when we talk about the asset pipeline, we... always say 'the asset pipeline.' The guide title should reflect this.
* Add periods to the bullet points in guides.Steve Klabnik2012-11-291-5/+5
| | | | Talked with @fxn about this. Bullet points should have periods at the ends.
* Revert "Switch to 1.9 hash syntax"Vijay Dev2012-11-171-10/+11
| | | | | | This reverts commit d8596c4b8500a899d686c57fa093c549b0378c7a. Reason: too many mistakes [ci skip]
* Switch to 1.9 hash syntaxAgis Anastasopoulos2012-11-151-11/+10
|
* use em-dashes instead of two minuses in guidesburningTyger2012-11-101-4/+4
|
* Further explain the CDN and caching situation.Steve Klabnik2012-11-091-3/+4
|
* Add note about asset pipeline and CDNs.Steve Klabnik2012-11-091-0/+11
| | | | Fixes #2468.
* With the Asset Pipeline the :cache and :concat options aren't used anymoreGuillermo Iguaran2012-10-241-0/+3
|
* Revert "divided into folder with the language"Rafael Mendonça França2012-10-171-0/+760
| | | | | | This reverts commit f5b9ed4fbc3215a5fce48985ea372ad3f1182252. REASON: Translation work can not be done in the docrails repository
* divided into folder with the languageRodrigo Martins2012-10-171-760/+0
|
* typo fix: remove duplicate periodcczona2012-09-271-1/+1
|
* Remove highly uncommon `config.assets.manifest` option for moving the ↵Guillermo Iguaran2012-09-191-9/+0
| | | | | | manifest path. This option is now unsupported in sprockets-rails.
* Fix the usage of `*` in MarkdownPrem Sichanugrist2012-09-171-2/+2
| | | | | In Textile `*` would convert to `<strong>`, but in Markdown we have to use `**` instead.
* Fix remaining formatting problems in the guidePrem Sichanugrist2012-09-171-50/+43
|
* Convert all the links into Markdown formatPrem Sichanugrist2012-09-171-14/+14
|
* Convert all inline codes to Markdown syntaxPrem Sichanugrist2012-09-171-98/+98
|
* Convert inline code tags to MarkdownPrem Sichanugrist2012-09-171-6/+6
|
* Convert heading tags and heading sectionPrem Sichanugrist2012-09-171-33/+43
|
* Convert code blocks into GFM stylePrem Sichanugrist2012-09-171-110/+110
|
* Rename the rest of the guides to MarkdownPrem Sichanugrist2012-09-171-0/+766