bunchopunch / nerdhat Goto Github PK

Even if we adhere to creating module style folders, some views may be used by several of those modules, and so housing the view in a particular module directory wouldn't make real sense.

To a lesser extent, our current thought is that layouts pair with controllers. It may be worth keeping that in the back of your head while pondering the question of shared views.

It seems there may need to be some tweaks to the build process so that we can properly support use strict with require. Getting that in places, along with some further tweaks to the .jshintrc files would be great to have in place.

The thing is a mess and full of stuff that you would never want to do in any production app. Ideally, that would be noted somewhere.

The Marionette default for templates is not really ideal. We're looking to continue using underscore for compiling the templates, but breaking them into external files. However, this also needs to avoid async loading, which can cause speed issues with. The solution may also require that templates are compiled in the build by some JST style task.

Additionally, LiveReload isn't triggered by edits to templates.

This is leans toward being outside of this project's scope. However, it's commonly an afterthought when planning apps like this, and it would be nice if there were some type of solution highlighted in this project.