tobi / liquid
- Source
- Commits
- Network (39)
- Issues (5)
- Downloads (0)
- Wiki (7)
- Graphs
-
Tree:
6dd4f71
commit 6dd4f716f824b66680976f564cfc85615283fe9e
tree 2faccd8b59b98f214ebfca63fac4bf43837a35bb
parent 5c259a3f49a3305bc638f3f044843e78a9684501
tree 2faccd8b59b98f214ebfca63fac4bf43837a35bb
parent 5c259a3f49a3305bc638f3f044843e78a9684501
liquid /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | ||
| |
CHANGELOG | ||
| |
History.txt | Thu May 08 08:34:43 -0700 2008 | |
| |
MIT-LICENSE | Thu May 08 08:28:13 -0700 2008 | |
| |
Manifest.txt | Mon Jun 23 06:42:15 -0700 2008 | |
| |
README.txt | Thu May 08 08:34:43 -0700 2008 | |
| |
Rakefile | ||
| |
example/ | Thu May 08 08:28:13 -0700 2008 | |
| |
init.rb | Thu May 08 08:28:13 -0700 2008 | |
| |
lib/ | ||
| |
liquid.gemspec | ||
| |
test/ |
README.txt
= Liquid template engine
Liquid is a template engine which I wrote for very specific requirements
* It has to have beautiful and simple markup.
Template engines which don't produce good looking markup are no fun to use.
* It needs to be non evaling and secure. Liquid templates are made so that users can edit them. You don't want to run
code on your server which your users wrote.
* It has to be stateless. Compile and render steps have to be seperate so that the expensive parsing and compiling can
be done once and later on you can
just render it passing in a hash with local variables and objects.
== Why should i use Liquid
* You want to allow your users to edit the appearance of your application but don't want them to run insecure code on
your server.
* You want to render templates directly from the database
* You like smarty style template engines
* You need a template engine which does HTML just as well as Emails
* You don't like the markup of your current one
== What does it look like?
<ul id="products">
{% for product in products %}
<li>
<h2>{{product.name}}</h2>
Only {{product.price | price }}
{{product.description | prettyprint | paragraph }}
</li>
{% endfor %}
</ul>
== Howto use Liquid
Liquid supports a very simple API based around the Liquid::Template class.
For standard use you can just pass it the content of a file and call render with a parameters hash.
@template = Liquid::Template.parse("hi {{name}}") # Parses and compiles the template
@template.render( 'name' => 'tobi' ) # => "hi tobi" 

