Skip to content
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

Open
quadrupleslap opened this issue Nov 4, 2017 · 7 comments
Open

Comments

@quadrupleslap
Copy link
Contributor

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.

@luciusmagn
Copy link
Collaborator

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?

@yutthhh
Copy link

yutthhh commented Dec 17, 2017

@yutthhh
Copy link

yutthhh commented Dec 17, 2017

@yutthhh
Copy link

yutthhh commented Dec 17, 2017

08544398.,

@yutthhh
Copy link

yutthhh commented Dec 17, 2017

0854439809

@luciusmagn
Copy link
Collaborator

@yutthhh do you need something regarding awesome-rust? State your business

@Israel-Laguan
Copy link
Contributor

Israel-Laguan commented Jan 18, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants