While asset_root support is nice for common scripts being updated across our sites all at once, it has some significant downsides:
It has caused unexpected breakage many times, since some sites may have an old version of the template(s) via the guides_style_18f gem that refer to assets whose path has changed, etc.
It adds a bit too much magic for my tastes.
Published sites behave differently from ones run locally.
I would be in favor of #21 instead.
TODOs
[ ] Remove asset_root support in Pages (shouldn't be a problem, since new builds would just use the styles from the gem rather than a central URL)
While
asset_rootsupport is nice for common scripts being updated across our sites all at once, it has some significant downsides:guides_style_18fgem that refer to assets whose path has changed, etc.I would be in favor of #21 instead.
TODOs
asset_rootsupport in Pages (shouldn't be a problem, since new builds would just use the styles from the gem rather than a central URL)asset_rootfrom across our various repositoriesguides_style_18f_asset_root