JobComposer: Custom, user defined template sources

[ericfranz]

A template source is a directory whose subdirectories are job templates.

Currently there are two template sources: OSC Templates and My Templates. Alongside these fixed locations to find templates, let the user add extra paths to new template sources.

CustomSource and Source would share functionality. Ideally CustomSource would be a type of Source but also be ActiveRecord - so we would need to put some thought into the implementation to make this clean. The list of all templates would be extended to include Source.my.templates + Source.osc.templates + CustomSource.all.map(&templates) (pseudocode)

This would involve five UI changes:

1. Add /sources/new to create a new template source:

2.Add /sources/edit to edit a template source (that is not OSC or My Templates - ignore the fact that this screenshot shows editing that - it would actually only allow you to edit custom template sources):

1. Source dropdown would be added to the new job page with the options for adding or editing template sources added to this. Source dropdown would have (and default) to "All) showing all templates (as new job page currently does) or allow you to select a specific template source to view that. The edit button would be enabled if you select a custom template source. The add button would always be there:

Unfortunately, this would involve a schema change.

┆Issue is synchronized with this Asana task by Unito

[johrstrom]

This applies to the current job composer - so a lot of the notes aren't as relevant to the project manager. That said - the core of the idea is good and so we should keep it.