tastejs / tastelang Goto Github PK

Continuation of #894:

TodoMVC added value AFAIK is: it fixes the characteristics of a product to be built, then asks producers to build a compliant product (not > necessarily identical to others), easing comparisons between producers.
I think TodoMVC shouldn't put effort into touching/handling/hosting producer's code.

About project listing, some ideas for the question What do I want when I look for a framework?:

Overview

Samples

• Snippets
• Whole apps

Goal: reason of existence

I like to see: design patterns used, relationship to other solutions/technologies

I don't like: buzzwords ("to build fast, scalable...", "easy to maintain..." and similar)

What is it very good for (outstanding) and why

Key Things: list of ~5 framework-specific classes/objects/concepts I must necessarily know about to properly use the framework
Current state

Starting | in Beta | Used in Prod by online sites {X, Y, ...} | etc.
Starting year, # of past and current maintainers
Dependencies

Community

Mailing lists, groups, etc.

Docs

Articles & Guides

Some things (Community, Current state) applies only to frameworks and no to usage samples of framework combinations.

Sounds good? For sure needs to evolve but do you think it's a starting point?

A sample implementation info following these guidelines is at https://github.com/dprotti/TasteLang#implementations.

That's about What do I want when I look for a framework?

About the question What do I want when I want to compare frameworks?:

First, I like to see only what is relevant to my comparison. Examples:

• Only frameworks that have dependency X
• Only frameworks that use design pattern W
• Only frameworks in X state of development, or more/less than Y years old
• etc

So I think it's valuable to have some kind of filtering / grouping mechanism for frameworks listing. I'm not sure how this can be accomplished using Github wiki features, but whatever the final solution is it would helpful if we uniform the fields describing the project info.

Would be nice to have a simple logo. Something similar to the TodoMVC logo maybe.

We need to define the project.

Why does it exist? Who is it intended for?

We need to adjust the app spec to account for TasteLang.

https://github.com/tastejs/todomvc/wiki/App-Specification

We also need to be much more explicit that this is a curation, not a collection. We can't accept everything. We should also be clearer about the criterias.

We need a site. I'm thinking we just reference the TodoMVC CSS and copy over the HTML and modify it.

Continuation of tastejs/todomvc#499

I can do it with git subtree split, but we need an updated list of apps to move over.