Use branches instead of files for different template/js examples? about app-template HOT 3 CLOSED

Funny. I was just thinking the opposite. I like the idea that you clone the repo and get a stack of examples in your face. Also, for many apps, including some upcoming work we've already got planned, you'll have multiple pages of different types that will coexist in one project.

from app-template.

The problem is the repository is already becoming filled with a multitude of files that aren't relevant to any given project. For example, I really want to backport the "live news modules", because it's something we'll use a lot, but just for the river of news alone that's 4 files (river_post.jst, app-river.less, _river.html and app-river.js) that will just be cluttering up the repository when we don't need them. I feel like it makes it more difficult to actual sort out what examples matter. I think what we're going to end up with is a huge repository of loosely related fragments that have to be deleted in order to get to a coherent project starting point.

And well it's true that we'll sometimes use more than one template, I think that's the exception not the norm and will never be more difficult than just checking out the files you need from another branch.

from app-template.

And we're off!

from app-template.