~subsetpark/bagatto

8517aaa0849884239bf18816c0b244533e74124c — Zach Smith 4 months ago 84175f7
Minor typo updates
1 files changed, 7 insertions(+), 6 deletions(-)

M MANUAL.md
M MANUAL.md => MANUAL.md +7 -6
@@ 500,10 500,10 @@ Here's the contents of `post.temple` in the Bagatto demo directory:
The appeal of Temple is in its simplicity. It consists of four types
of expression, all of which are seen here.

- `{$ ... $}`: Evaluate the expression between the $s at compile time;
- `{% ... %}`: Evaluate the expression between the %s at runtime,
- `{$ ... $}`: Evaluate the expression between the `$`s at compile time;
- `{% ... %}`: Evaluate the expression between the `%`s at runtime,
  escape and interpolate the output;
- `{- ... -}`: Evaluate the expression between the -s at runtime,
- `{- ... -}`: Evaluate the expression between the `-`s at runtime,
  interpolate the output without escaping it.
- `{{ ... }}`: Evaluate and interpolate the expression inside the curly braces.



@@ 572,9 572,10 @@ with placeholders for the values to be interpolated.
### Renderer Generators

Because `bagatto/render` is such a common operation, Bagatto offers a
convenience function that will generate a **renderer** that will make
the above call. For instance, if I wanted to specify the above
template in a site specification, I'd probably write this:
[convenience function](#bagattorenderer) that will generate a
**renderer** that will make the above call. For instance, if I wanted
to specify the above template in a site specification, I'd probably
write this:

```clj
repl:6:> (def site {:_ {:path "out.txt"