Hey guys, I'm using what I think is a novel architecture for organizing the parts of the-oregon-trajectory.

I've broken parts of the game into "scenes" which each have their own html, js/coffeescript, and .less files. This way different people can take full ownership over a game "module" without having to tiptoe around each other's code. Modules are defined as angular directive which get hidden/shown to switch scenes and the js/css is bundled so you never have to worry about including new scripts.

It's definitely not perfect, but I think it's very interesting, especially since it seems like it will make re-using modules/scenes/whateverYouWantToCallThem very easy.

What are your thoughts on this architecture? Does it make sense or will this non-conformity come back to bite me later? See anything else I could improve?