As part of our evolution to TasteJS, we're going to migrate compile to JS apps over to TasteLang, a sub-project which will allow us to scale up inclusion of those types of apps without having to say no so often to combo apps (e.g Angular + CoffeeScript).
This issue is to track which apps we want to move. Please feel free to list your selections :)
It's the harder choice to make, but I think that a clean split where we say if it isn't JS it has to go into TodoLang makes sense.
+1 on that. We should make sure they're still easily discoverable. That would make it
I hope I didn't miss anything.
Thanks for checking!. We also need to decide on the strategy for apps currently in progress/PRs - do we ask authors to resubmit to TasteLang or just manually copy them over and ensure attribution?.
Probably a good idea for us to label these PRs either way (e.g TasteLang)
@addyosmani git subtree split ;) It preserves attribution. I did it on all the generators when I extracted them. I can do it when we've decided on what apps to move.
git subtree split
Should we consider apps for thus that we previously punted on in the wiki? There probably aren't that many now that I think about it.
@addyosmani Looks like this would only affect the Meteor + CoffeeScript example, but maybe there are some PRs that didn't make it to the wiki. I'll look that up soon.
We should start to think about when we want to make this move and how we want to represent apps that have been transferred over to the other repo. If we can figure out how to visualize this on the homepage, the move can probably start to happen soon. Do we want to just have another block/section where we link to these or introduce tabs/separate pages?
I would like to see it equal to TodoMVC.
We can just use the existing layout. I'll come up with some stuff soon.
I like it!