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

* Seperated 'Howto' into 'How to'.

Browse Source 
* Added periods to the second list as the first item has them. I guess I'm anally retentive like that. :)
This commit is contained in:
Dan Atkinson
2012-03-14 14:58:12 +00:00
parent 0e3b522fe2
commit 1ee342d83b
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -5
View File
@@ -11,10 +11,10 @@ Liquid is a template engine which was written with very specific requirements:
## Why you should use Liquid ## Why you should 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 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 want to render templates directly from the database.
* You like smarty (PHP) style template engines * You like smarty (PHP) style template engines.
* You need a template engine which does HTML just as well as emails * You need a template engine which does HTML just as well as emails.
* You don't like the markup of your current templating engine * You don't like the markup of your current templating engine.
## What does it look like? ## What does it look like?
@@ -31,7 +31,7 @@ Liquid is a template engine which was written with very specific requirements:
</ul> </ul>
``` ```
## Howto use Liquid ## How to use Liquid
Liquid supports a very simple API based around the Liquid::Template class. 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. For standard use you can just pass it the content of a file and call render with a parameters hash.