-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split templating engines category into "static" and "dynamic" #371
Comments
Hmm, I guess you are right. However, so far, we only have 8 templating engines, which are already split into categories - Handlebars, HTML, Mustache and one freestanding, so I am not sure if fragmenting it even further is a good idea. What do you think, @kud1ing? |
จ |
ง |
08544398., |
0854439809 |
@yutthhh do you need something regarding awesome-rust? State your business |
I think a user is more interested in the "type" (i.e. handlebars, jade, jinja, etc.) than if it's dynamic or static. I suggest adding a phrase mentioning if it is static or dynamic instead of separating it into categories, or just not adding this suggestion. A user can enter each repo anyway and check themselves. |
Not the best names, but some template engines can load templates at run-time, whereas others work at compile-time (because they use plugins or macros, like Horrorshow). This is a pretty big distinction that should probably be mentioned.
The text was updated successfully, but these errors were encountered: