It does not use asset-pipeline, but I use this directive @parentin Blade templates.
On my site, I have several jsand several cssthat I need on every page (for example, Twitter bootstrap), and I have Blade layoutone that includes them.
Then on some pages (my application is an analytic application) I need to enable special resources for the page (for example, a graphics library).
Therefore, on my layout there are:
@section('js')
{{ HTML::script('js/a.js') }}
@show
@section('css')
{{ HTML::style('css/a.css') }}
@show
And then on a specific page, I have:
@extends('layouts.site')
@section('js')
@parent
{{ HTML::script('js/b.js') }}
@stop
@section('css')
@parent
{{ HTML::style('css/b.css')
@stop
This works great for me. The subpages in my application are very specific as to what additional assets they need, so controlling them in this way is very effective.
source
share