This is a sub-task to #4, and is still in the "exploratory"/WIP phase. If we're going to make our YAML work in a reasonable fashion (or a DB for that matter), we need to think through what we are going to template, how we are going to template it, and where we put the templates and the templating logic. And this may or may not be the right strategy. Please see the discussion under #4 for additional considerations - and feel free to chime in!
Current proof of concept is to use template strings, and pull various pieces of info from a YAML file of resources. The resource file would be filtered by Topic/level, and the template(s) would pull in the needed info and make the JSON necessary to send out the message.
Attached is a (not yet working) copy of a template. Suggestions welcome.
This is a sub-task to #4, and is still in the "exploratory"/WIP phase. If we're going to make our YAML work in a reasonable fashion (or a DB for that matter), we need to think through what we are going to template, how we are going to template it, and where we put the templates and the templating logic. And this may or may not be the right strategy. Please see the discussion under #4 for additional considerations - and feel free to chime in!
Current proof of concept is to use
template strings
, and pull various pieces of info from a YAML file of resources. The resource file would be filtered by Topic/level, and the template(s) would pull in the needed info and make the JSON necessary to send out the message.Attached is a (not yet working) copy of a template. Suggestions welcome.