App-Microsite-Assemble
view release on metacpan or search on metacpan
lib/App/Microsite/Assemble.pm view on Meta::CPAN
This module assembles F<templates/> into fully-baked pages.
Your project should contain a F<fragments/> subdirectory, filled with files that contain bits of copy. Any template can use C<{{fragment "copy-file-name"}}> to inline the text from that file.
Subdirectories of F<templates/> can establish a hierarchy of wrappers. For example, you might have F<templates/basic/contact/> which is page C<contact> wrapped by wrapper C<basic>. The F<templates/basic/contact/> directory would have a F<content.hand...
Any directory in the hierarchy can have a F<wrapper.handlebars> which wraps everything below it. So the top-level F<templates/> could have a very generic F<wrapper.handlebars> that sets up C<< <html> >> etc. Subdirectories under F<templates/> can pro...
Similarly, any directory can have a F<config.json> which will combine in the usual way; files deeper in the hierarchy override settings from their upwards directories. Config variables will be provided in the template and its wrappers. This is intend...
You can put partials in any directory under F<templates/> and they will cascade; deeper partials will shadow shallower partials.
Finally, the F<fragments/> directory structure should match F<templates/>. The search path for fragment names works just like everything else.
=head1 AUTHORS
=over 4
=item *
Shawn M Moore <code@sartak.org>
( run in 0.460 second using v1.01-cache-2.11-cpan-49f99fa48dc )