Talk:Comparison of web template engines

This is the talk page for discussing improvements to the Comparison of web template engines article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1: 2 months

Software: Computing List‑class

	This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SoftwareWikipedia:WikiProject SoftwareTemplate:WikiProject Softwaresoftware
List	This article has been rated as List-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Computing.

Template system?? (redirecting here)

SEE Template System redirection problems on Talk:Template#Template_system.3F.3F_.28redirecting_here.29

Template system?? (redirecting here)

SEE Template System redirection problems on Talk:Template#Template_system.3F.3F_.28redirecting_here.29

Pug

Pug (disambiguation) says "Pug, an HTML template engine; see Comparison of web template engines". But I see nothing about Pug here (or about Jade, which an earlier comment says is an older name for it). This page is also xref'd from JADE (programming language). Should Pug be listed here, or is it covered somewhere else? --Macrakis (talk) 15:01, 30 June 2020 (UTC)[reply]

Probably it isn't "notable enough" for Wikipedia. "Notability" is a vague criterion, used by officious Wikipedians to delete information about anything they think should disappear into obscurity. But in the case of web template engines, I think there are too many, rather than too few, listed. There are 30+ web template engines listed here. Imagine you're a contract web developer and somebody asks you to take over maintenance of their website. You rashly say "Sure" and then discover it was developed using the Frooboz web template engine that's (1) no longer maintained, (2) has documentation two versions behind the code, (3) has a tiny and shrinking user community .... Point (3) is probably true of at least half the engines listed here, and if (1) and (2) aren't yet, they will be soon. Longitude2 (talk) 07:56, 6 April 2021 (UTC)[reply]

Any indication on how well maintained the template engine is

It would be nice if there was some kind of indication of how well maintained the template engine is. For instance, Apache Velocity has not had an update in the past 13 years and has everal vulnerabilities (see https://mvnrepository.com/artifact/org.apache.velocity/velocity/1.7).

This could be done by adding a column that shows when the last update was if it is no longer actively maintained. For template engines that are actively maintained, it would be too much of a hassle to update this every time if it's not automated, so it would be enough to say "Actively maintained" (maybe with a link to where the latest version can be found). 2001:1C01:3B1E:FE00:59FD:68C5:F95E:ECD2 (talk) 21:26, 31 May 2023 (UTC)[reply]