SliTaz Repositories

     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/perl-template-toolkit/description.txt	Fri Sep 01 12:04:33 2023 +0000
     1.3 @@ -0,0 +1,34 @@
     1.4 +The Template Toolkit is a collection of Perl modules which implement a fast,
     1.5 +flexible, powerful and extensible template processing system.
     1.6 +
     1.7 +It is "input-agnostic" and can be used equally well for processing any kind
     1.8 +of text documents: HTML, XML, CSS, Javascript, Perl code, plain text,
     1.9 +and so on.
    1.10 +However, it is most often used for generating static and dynamic web content,
    1.11 +so that's what we'll focus on here.
    1.12 +
    1.13 +Although the Template Toolkit is written in Perl, you don't need to be a Perl
    1.14 +programmer to use it. It was designed to allow non-programmers to easily
    1.15 +create and maintain template-based web sites without having to mess around
    1.16 +writing Perl code or going crazy with cut-n-paste.
    1.17 +
    1.18 +However, the Template Toolkit is also designed to be extremely flexible and
    1.19 +extensible. If you are a Perl programmer, or know someone who is, then you
    1.20 +can easily hook the Template Toolkit into your existing code, data, databases
    1.21 +and web applications.
    1.22 +Furthermore, you can easily extend the Template Toolkit through the use of
    1.23 +its plugin mechanism and other developer APIs.
    1.24 +
    1.25 +Whatever context you use it in, the primary purpose of the Template Toolkit
    1.26 +is to allow you to create a clear separation between the presentation elements
    1.27 +of your web site and everything else.
    1.28 +
    1.29 +If you're generating static web pages, then you can use it to separate the
    1.30 +commonly repeated user interface elements on each page (headers, menus,
    1.31 +footers, etc.) from the core content.
    1.32 +If you're generating dynamic web pages for the front end of a web application,
    1.33 +then you'll also be using it to keep the back-end Perl code entirely separate
    1.34 +from the front-end HTML templates.
    1.35 +Either way, a clear separation of concerns is what allow you to concentrate
    1.36 +on one thing at a time without the other things getting in your way.
    1.37 +And that's what the Template Toolkit is all about.