public
Description: Liquid markup language. Save, customer facing template language for flexible web apps.
Homepage: http://www.liquidmarkup.org
Clone URL: git://github.com/tobi/liquid.git
Click here to lend your support to: liquid and make a donation at www.pledgie.com !
liquid /
name age message
file .gitignore Mon Apr 06 07:10:13 -0700 2009 Ignore pkg directory [tobi]
file CHANGELOG Thu Apr 16 15:33:20 -0700 2009 Ruby 1.9.1 bugfixes Signed-off-by: Tobias Lütk... [Jakub Kuźma]
file History.txt Thu May 08 08:34:43 -0700 2008 Merged last set of changes from original SVN lo... [tobi]
file MIT-LICENSE Thu May 08 08:28:13 -0700 2008 Initial github import of liquid [tobi]
file Manifest.txt Mon Jun 23 06:42:15 -0700 2008 Seriously... [tobi]
file README.txt Thu May 08 08:34:43 -0700 2008 Merged last set of changes from original SVN lo... [tobi]
file Rakefile Mon Jun 15 07:35:49 -0700 2009 Added convenience task rake profile:grind to lo... [tobi]
directory example/ Thu May 08 08:28:13 -0700 2008 Initial github import of liquid [tobi]
file init.rb Thu May 08 08:28:13 -0700 2008 Initial github import of liquid [tobi]
directory lib/ Tue Sep 08 08:06:50 -0700 2009 fixed Variable#render to work under Ruby 1.9.1 ... [chriskottom]
file liquid.gemspec Thu Apr 16 15:33:21 -0700 2009 regenerated gemspec Signed-off-by: Tobias Lütk... [Jakub Kuźma]
directory performance/ Mon Jun 15 07:33:33 -0700 2009 Performance improvement for Block parsing. ~ 10... [tobi]
directory test/ Mon Jun 15 06:00:30 -0700 2009 Merge branch 'master' of git@github.com:tobi/li... [tobi]
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"