More use of generic templates

[cstewart87]

Working on adding a new top-level component ('Assemblies', 'Stacks', 'Offerings', etc.) I caught myself doing a lot of copying and pasting, especially with templates. Then, after clicking through the components I realized there's some inconsistencies with layout (button placement, message placement).

I'm hoping there's a way to have some more generic templates, with names like 'topComponentTemplate', 'subComponentTemplate', 'componentList', 'componentTable', etc. These templates would contain a base for what our common layout should be (styling, placement, etc.) and when adding a new component, the only requirement would be to create a new view, and render the template with appropriate titles, collections, messages, etc.

If there are reasons for avoiding this approach, please share. I feel if we can move in this directions, it would help decrease the time to add new features, as well as keep a more consistent design throughout our application.

[lifeBCE]

Agreed. As part of the application refactor, we need to go through a series of DRY runs.