Web template system

Developers can implement templates from content management systems, web application frameworks, and HTML editors.

With the model typically held in a relational database, the remaining components of the MVC architecture are the control and view.

Five templating system types are classified based on when they replace placeholders with real content and assemble pages.

[citation needed] Programming languages such as Perl, Ruby, C, and Java support template processing either natively, or through add-on libraries and modules.

These technologies are typically used in server-side templating systems, but could be adapted for use on an "edge-side" proxy or for static page generation.

These can be viewed as a ready-made web design, used to mass-produce "cookie-cutter" websites for rapid deployment.

In the majority of cases, this "publish option" doesn't interfere with the template system, and it can be made by external software, as Wget.

People began to use server-side dynamic pages generated from templates with pre-existent software adapted for this task.

Next, a simple but relevant technology was the direct execution made on extension modules, started with SSI.

Other systems implement template functionality in the browser using JavaScript or another client-side scripting language, including: The most simple form is transclusions (HTML frames).

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 engine ) to mass-produce web documents.
A diagram illustrating all of the basic elements and processing flow of a template engine.
Outside server template system architecture.
Server-side template system
Client-side and distributed (decentralized) template system.