Talk:Web template system

message: I replaced the entry
Zope Page Templates	Zope	Is a Embedded programable language implemented as a Attribute Language.
by the reference to the now-existing Template Attribute Language article. I'm not sure what is meant by "embedded programmable language" anyway; IMHO it is no programming language at all; if "programable language" was written on purpos, it must be explained, which doesn't seem to me to be the case at the linked location. --TobiasHerp 17:05, 9 April 2007 (UTC)
thread_title:  ZPT -> TAL 

message: Someone should repair all those Embedded complex language links. Most of them do not point to the same target nor the Target exists. I didn't find any further explanation of what Embedded complex language means at all. (sorry, english is not my favorite language...) 11:14, 10 November 2009 (UTC)
thread_title:  Embedded complex language 

message: This article on a technology subject has apparently fallen under the spell of a project focused on philosophical metathinking about "Systems" (an all-encompassing vague word).  This has caused the article to become borderline useless for those of us with a practical interest in the subject.  For someone reading up on current web page generation technology, this page provides only confusion and semi-nonsense too far removed from reality to be of any value.  Furthermore the article does not link to an alternative real-world article on the subject, even if such an article might exist somewhere.
More specifically, some major issues with the content of this article are:
# The article and drawings seem to confuse what used to be called "catalog web publishing systems" with what is nowadays commonly called "content management systems" both of which categories includes template-based subcategories.  The main distinction is that the former kind of system is about turning a structured database into a web site based on that data, while the latter is about providing uniform layout and styles to a collection of documents (which may happen to be stored in a database, but are not otherwise database-like).  An example of a catalog publishing system in current use is the module pages at [CPAN], an example of a content management system is Wikipedia itself.
# The article uses terminology from "Systems science" rather than the slightly different terminology used by practitioners in the field.  This makes the article hard to read and difficult to accurately understand and verify.
# The systems categorized as "Outside server systems" at a minimum need to be split into 2 main categories: author-side systems (such as FrontPage and Dreamweaver) and backoffice server systems (such as Website Meta Language).  The former resides where the content author writes pages, while the latter runs on an intermediate server which collects content or data together and produces finished pages which are then bulk uploaded to the web server for later retrieval by visitors.
# The lists of specific technologies lack some obvious entries such as ASP.NET (a Microsoft technology quite separate from their older ASP technology, except by name and category), and Website Meta Language (the latter of which links to this article as its category).
77.215.46.17 (talk) 23:08, 12 January 2011 (UTC)
thread_title:  Overly formalistic article 

message: ...of a site that uses templates; could this be cited? For the record, a client-side template system based on ours could be simulated using iframes and DOM (parser functions would be executed in the browser using JavaScript). 68.173.113.106 (talk) 22:38, 13 June 2012 (UTC)
thread_title:  We're a good example 

message: Hello fellow Wikipedians,
I have just added archive links to  on Web template system. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20121204081204/http://www.phpwact.org:80/pattern/template_view to http://www.phpwact.org/pattern/template_view#separating_html_from_programming_code
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 23:00, 16 January 2016 (UTC)
thread_title:  External links modified 

message: The section on static site generators discusses WYSIWYG HTML editors instead. The two should be separated.
A static site generator is not an editor and does not include an editor; it is an application that generates (the files of) the website from a description in some other (often generator-specific) format. Editing the source files and using the generator are two separate things. This format may or may not look like HTML pages with some templating syntax thrown in, so the connection with this article is tenuous. Examples: Hugo, Jekyll, Gatsby; some more are listed here.
Web page editors such as FrontPage and DreamWeaver interactively let their users create websites directly, without a separate site generation process. When using some templating, they will do a bit of static site generation under the hood; but generators they aren't. Rp (talk) 21:16, 14 November 2021 (UTC)
thread_title:  Separately discuss static site generators and editors 

message: These are long discontinued - why is this not indicated?
Gordon Findlay (talk) 09:00, 28 February 2022 (UTC)
thread_title:  Frontpage, dreamweaver?