Web template system: Difference between revisions

Revision as of 20:13, 12 February 2024

Latest revision as of 11:33, 28 August 2025

(9 intermediate revisions by 8 users not shown)

Line 8:

[[File:TempEngWeb016.svg|thumb|The basic process for a server-side '''web templating system''': content (from a [[database]]), and "presentation specifications" (in a '''web template'''), are combined (through the [[template processor|template engine]]) to mass-produce web documents.]]

A '''web template system''' in [[web publishing]] allows web designers and developers to work with ''web templates'' to automatically generate custom [[web page]]s, such as the results from a search. This reuses static web page elements while defining dynamic elements based on [[HTTP request|web request]] parameters.

Web templates support static content, providing basic structure and appearance. Developers can implement templates from [[content management system]]s, [[web application framework]]s, and [[HTML editor]]s.

Line 17:

* ''[[Template resource]]'': ''web template''s specified according to a [[template language]];

The template and content resources are processed and combined by the template engine to mass-produce web documents, each with a similar visual format. For purposes of this article, web documents include any of various output formats for transmission over the web via [[Hypertext Transfer Protocol|HTTP]], [[HTTPS]], or another [[Internet Protocol|Internet protocol]].

===Template engine===

Line 108:

| [[Python (programming language)|Python]]

| Use the "Django template language".

|-

| EJS (Embedded JavaScript)

| [[JavaScript]]

| Public. [[Web template#Template languages|Embedded complex language]].

|-

| [[FreeMarker]]

Line 115 ⟶ 119:

| [[Facelets]]

| [[Jakarta EE]]

| Public. Part of [[Jakarta Server Faces]]

|-

| [[Genshi (Templating Language)|Genshi]]

Line 171 ⟶ 175:

| Topsite

| [[Python (programming language)|Python]]

| Public. ''"As of 2008-02-20, this project is no longer under active development."''<ref>{{cite web|last=jodyburns|title=Topsite Templating System|url=httphttps://sourceforge.net/projects/topsite/|access-date=15 October 2013}}</ref>

|-

| [[Twig (template engine)|Twig]]

Line 218 ⟶ 222:

|-

| [[ColdFusion Markup Language]] (CFM)

| Public ([[Lucee]], [[Railo]], [[OpenBD]]). Proprietary ([[Adobe ColdFusion]]).

|-

| [[Jakarta Server Pages]] (JSP)

Line 252 ⟶ 256:

===Client-side systems===

[[File:ClientSideTemplates.gif|thumb|right|Client-side and [[Distributed computing|distributed]] (decentralized) template system.]]

{{see also|JavaScript templating}}

Many web browsers can apply an [[XSLT]] stylesheet to XML data that transforms the data into an XHTML document, thereby providing template functionality in the browser itself.<br />

Other systems implement template functionality in the browser using [[JavaScript]] or another [[client-side scripting]] language, including: