Refactor frontend code to follow component structure - Due 6/27/2018

[brylie]

Our frontend code is somewhat disorganized. We agreed to re-structure the frontend code, so that it is easier to understand.

Goal

• Improve project maintainability by re-structuring code.
• Prepare to replace frontend framework, by re-structuring code to follow component-oriented structure

Resources

Backbone architecture

• Organizing a Backbone Application (2013)

Componentized web

• The Web's Declarative, Composable Future. by Addy Osmani

[brylie]

I think many Backbone projects may pre-date the 'componentized' web application movement. So, we may need to look towards other component frameworks for inspiration, and define our own bespoke component structure.

[mdwest]

Not well versed in the technical details, but if continuing to use the backbone framework will get us to a stable version sooner, I vote we use it and create our own standardization. Might be good to document our front-end "component structure" so we can easily share it with any developer interested in contributing to the front-end.

[JOO33]

Unless there are any objections, I will be using Marionette.js and webpack to help with the restructuring process.

[brylie]

That sounds fine by me.

Please consider that Marionette may be a stepping stone towards a broader migration of this project's frontend code towards WebComponent-based architecture.

[JOO33]

Closing due to solution proposed by #827 . The JS related issues will be no longer relevant.