avoid all the annoying if logic in head by adding custom-head approach like custom-foot use.
in my other templates, there is two options for both head and foot: custom include and/or direct string.
Currently CB only has custom foot include.
For adding the required css in the head, it would be more handy to have a custom head that just adds the string directly (rather than having to go and write up a separate include for each.
Maybe foot/head would just be add a string, and custom-foot/custom-head could be custom include.
e.g. on data layout,
---
# "Data" page with table and data download options
layout: page
head: <link rel="stylesheet" type="text/css" href="{{ '/assets/lib/datatables/datatables.min.css' | relative_url }}">
custom-foot: js/table-js.html
---
this makes customized pages much easier to keep self contained (but still optimized) without spidering into needing to edit logic in other places.
avoid all the annoying if logic in head by adding custom-head approach like custom-foot use. in my other templates, there is two options for both head and foot: custom include and/or direct string. Currently CB only has custom foot include. For adding the required css in the head, it would be more handy to have a custom head that just adds the string directly (rather than having to go and write up a separate include for each.
Maybe
foot/headwould just be add a string, andcustom-foot/custom-headcould be custom include.e.g. on data layout,
this makes customized pages much easier to keep self contained (but still optimized) without spidering into needing to edit logic in other places.