Labyricorn/liquid
1
0
Fork 0
mirror of https://github.com/Shopify/liquid.git synced 2026-09-18 18:30:40 -07:00
Code Issues Packages Projects Releases Wiki Activity

Migrated from home v17

RichMorin
2010-08-12 13:45:47 -07:00
parent 7e709838e0
commit 1f92e1189b
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Home.textile
+11 -9
@@ -1,17 +1,19 @@
Liquid is a template engine which was crafted 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 separate 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.
* It has to have simple markup and beautiful results. Template engines which don't produce good looking results 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. The compile and render steps have to be separate, so that the expensive parsing and compiling can be done once; later on, you can just render it by passing in a hash with local variables and objects.
* It needs to be able to style emails as well as HTML.
h2. Stuff to read
h2. Stuff to read, watch, etc.
* [[Liquid for Programmers]]
* [[Liquid for Designers]]
* [[Getting Liquid to Work in Rails]]
* "Liquid":http://railscasts.com/episodes/118-liquid (screencast)
h2. Who uses Liquid?
* "Shopify":http://www.shopify.com
@@ -27,8 +29,8 @@ h2. Who uses Liquid?
h2. 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 template engine language
* 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 language of your current template engine.