My pipeline 1) parses content dirs you configure in e-cli-build: https://github.com/anulman/cook-for-mom/blob/feat/markdown-yml/ember-cli-build.js#L17-L20
2) Passes the resulting components through e-cli-htmlbars (by virtue of including them in the treeForTemplate
); I'm personally preprocessing these between hyde & e-cli-htmlbars to support handlebars / ember env in my templates: https://github.com/anulman/cook-for-mom/blob/feat/markdown-yml/lib/ember-cli-markdownbars/index.js#L16-L40
3) splits remote templates (currently hardcoded, can be made configurable) into the root dir, ie to be distributed in the public
tree
4) The json & content can be fetched from a predictable path:
- JSON: https://github.com/anulman/cook-for-mom/blob/feat/markdown-yml/lib/ember-async-layout/app/mixins/async-resource-adapter.js#L4-L13
- Content: https://github.com/anulman/cook-for-mom/blob/feat/markdown-yml/lib/ember-async-layout/app/components/async-layout.js#L44-L72 (I know the JSON one conforms to adapter naming; it's a mixin and can be used anywhere)