You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're a template designer who already knows Liquid, you should already know everything you need to know—the language should support everything that Liquid supports. Plus there are a few syntactic shortcuts to reduce the amount of Liquid you need for simple tasks, like macros.
Or, if you know a Moustache- or Handlebar-style templating language, you are most of the way there. See Liquid.NET for Designers for more information.
For Developers
If you're a programmer, Liquid.NET makes it simple to:
provide data to your template designers
write extensions (filters, tags and blocks) without having to worry too much about Liquid.NET internals, security, or text parsing.
There are several things missing from Liquid that are on the roadmap....
One difference between Liquid.NET and Liquid is that Liquid.NET takes care of security for you. There are no "Drops" to extend or interfaces to implement—Liquid.NET takes care of this for you.
Liquid.NET or DotLiquid?
DotLiquid is a great project and has been around for a lot longer than Liquid.NET and is more mature. There are two reasons why we replaced DotLiquid with Liquid.NET. The first is that DotLiquid has not been actively maintained for several years, and has fallen out of step with Ruby Liquid. The second reason is that Ruby Liquid and DotLiquid share the limitation that they are grammarless parsers, and therefore difficult to modify and extend. Liquid.NET has a grammar and uses ANTLR4-generated parser in order to create a more maintainable code-base.