App-Templer

 view release on metacpan or  search on metacpan

MANIFEST  view on Meta::CPAN

t/test-templer-plugin-factory.t
t/test-templer-plugin-filecontents.t
t/test-templer-plugin-fileglob.t
t/test-templer-plugin-filters.t
t/test-templer-plugin-redis.t
t/test-templer-plugin-rootpath.t
t/test-templer-plugin-shellcommand.t
t/test-templer-plugin-timestamp.t
t/test-templer-site-new.t
t/test-templer-site.t
t/test-templer-synchronization.t
templer.cfg.sample
META.json                                Module JSON meta-data (added by MakeMaker)

README.md  view on Meta::CPAN

distinct output directory, instead output is written to the same directory in
which is encountered.  Given an input directory you might see this kind of
transformation:

    index.wgn           -> index.html
    about.wgn           -> about.html
    favicon.ico         [Ignored and left un-modified.]
    robots.txt          [Ignored and left un-modified.]
    ..

There is _also_ a *synchronized* mode. When working synchronized any file in
the output directory which do not have a source file in input directory (page
or asset) is removed each time the site is rebuild.


Pages
-----

Your site will be made of pages, which are snippets of HTML you write.  These
snippets will be processed and inserted into the layout file before being output
to disk.

templer.cfg.sample  view on Meta::CPAN

#   ..
#
#
# in-place = 1
#
##


##
#
# If we're working synchronized then files in output must have a source file
# in input or else they are removed
#
# sync = 1
#
##


##
#
# The more common way of working is to produce the output in a separate



( run in 0.252 second using v1.01-cache-2.11-cpan-0d8aa00de5b )