view release on metacpan or  search on metacpan

README.md  view on Meta::CPAN

    * [Footnotes](#footnotes)
* [Layout](#layout)
    * [Variables](#variables)
    * [Comments](#comments)
    * [Filters](#filters)
    * [Conditionals](#conditionals)
    * [Iteration](#iteration)
    * [Blocks](#blocks)
    * [Perl code](#perl-code)
    * [Includes](#includes)
    * [Macros](#macros)
    * [Plugins](#plugins)
    * [Chomping](#chomping)
    * [Dumping](#dumping)
* [Deployment](#deployment)
    * [Amazon S3](#amazon-s3)
    * [GitHub Pages](#github-pages)
* [What Dapper Doesn't Do](#what-dapper-doesnt-do)
* [Upgrading from 0.21](#upgrading-from-021)
* [Troubleshooting](#troubleshooting)
* [Further Reading](#further-reading)

README.md  view on Meta::CPAN

               "path/to/template2.html" a = "An arg" b = "Another arg" %]

If it's important that the included file *not* be parsed for directives, an
alternative directive may be used called `insert`. `Insert` directives act in
exactly the same way that `include` directives do, but does not process any 
directives that the inserted file might contain. Example:

    [% insert "path/to/template1.html",
              "path/to/template2.html" %]

## Macros

The `macro` directive can be thought of as a way to define a miniature function
that can be used elsewhere in the template. Example:

    [% macro foo(i, j) block %]You passed me [% i %] and [% j %].[% end %]
    [% foo(1, 2) %]

Result:

    You passed me 1 and 2.