An implementation of the Jinja2 template language in Haskell

Version on this page:
LTS Haskell 22.26:
Stackage Nightly 2023-12-26:
Latest on Hackage:

See all snapshots ginger appears in

MIT licensed by Tobias Dammers
Maintained by [email protected]
This version can be pinned in stack with:ginger-,2938


Build Status Hackage

A Haskell implementation of the Jinja2 template language.

A note of warning: the git repository at has been deleted and restored with a rewritten commit tree on 2016-04-06 in order to clean up the messy history. This means that if you have a checkout from before that date, merging the bitbucket repo will most likely break things; please do a fresh clone to fix this. Sorry for the inconvenience.


Ginger provides most of the original Jinja2 template language, as much as that makes sense in a Haskell host application.

We do, however, some of the most blatant Pythonisms, especially when we felt the features in question were more of an accidental result of binding template constructs to Python constructs.

On top of that, we deviate on a few points, and add some features that we think are very useful and help make the language better and more consistent.


Ginger is available from Hackage, and it is in Stackage, so you can use it in plain Cabal projects as well as Stack ones.

Installing with Cabal:

cabal install ginger

Installing with Stack:

stack install ginger

Using as part of another project:

Add the following to your .cabal’s build-depends:

ginger >= && <0.4

Template Syntax

Full template syntax documentation is available from the /docs subdirectory in the project repository itself, or from the User Guide section on the Ginger website.

Minimal example template

<!DOCTYPE html>
        <title>{{ title }}</title>
    {# This is a comment. Comments are removed from the output. #}
        <menu id="nav-main">
        {% for item in navigation %}
            <li><a href="{{ item.url }}">{{ item.label }}</a></li>
        {% endfor %}
        <div class="layout-content-main">
            <h1>{{ title }}</h1>
            {{ body }}

There are two kinds of delimiters. {% ... %} and {{ ... }}. The first one is used to execute statements such as for-loops or assign values, the latter prints the result of an expression to the template.

Not implemented yet: Jinja2 allows the programmer to override the default tags from {% %} and {{ }} to different tokens, e.g. <% %> and << >>. Ginger does not currently support this.

Haskell API

The Haskell API is documented fully through Haddock documentation, available from Hackage. We’ll just provide a short overview here.


On the Haskell side of things, executing a template is a two-step process. First, template source code is parsed into a ‘Template’ data structure, which is then fed to ‘runGinger’ or ‘runGingerT’.


Because Ginger templates can include other templates, the parser needs a way of resolving template names. Instead of hard-wiring the parser into ‘IO’ though, Ginger will work on any Monad type, but requires the caller to provide a suitable template resolver function. For ‘IO’, the resolver would typically load a file from a template directory, but other monads might have access to some sort of cache, or expose template compiled into a program, or simply return ‘Nothing’ unconditionally to disable any and all imports. A suitable example implementation for ‘IO’ would look like this:

loadFile fn = openFile fn ReadMode >>= hGetContents

loadFileMay fn =
    tryIOError (loadFile fn) >>= \e ->
         case e of
            Right contents ->
                return (Just contents)
            Left err -> do
                print err -- remove this line if you want to fail silently
                return Nothing

(Taken from cli/GingerCLI.hs). This interprets the template name as a filename relative to the CWD, and returns the file contents on success or ‘Nothing’ if there is any error.

If you don’t need a monadic context for resolving includes (e.g. because you have pre-loaded all template sources), you can use the pure ‘parseGinger’ flavor, which does not rely on a host monad.


The core function for running a template is ‘runGinger’ (or its monadic flavor ‘runGingerT’); in order to pass an initial context to the template engine, pass a suitable ‘GingerContext’, which you can create using the ‘makeContext’ / ‘makeContextM’ functions.

An example call (for running a template in ‘IO’) would look something like this:

runGingerT (makeContextM scopeLookup (putStr . Text.unpack . htmlSource)) tpl


  • Expose parser error position details

  • ‘|json’ filter

  • StripBlocks and LTrimBlocks options
  • + tag modifier to override whitespace stripping

  • keepTrailingNewlines option
  • Ability to pass parser options into parseGinger
  • Runtime warnings

  • Documentation fixes

  • Haddock documentation fix

  • Exceptions / exception handling.

  • Marshalling and hoisting: it is now possible to fully marshal GVals between arbitrary carrier monads, as long as suitable conversion functions are provided.

  • Added map(), upper(), lower() functions

  • Documentation fixes

  • Release-related fixups

  • Bugfixes wrt indentation mode

  • Expose parser error pretty-printer from the library

  • Indentation mode: {% indent %} introduces an indentation context

  • Statements can now return values
  • Added do expressions (lift statements into expressions)

  • Fixed a parser bug related to whitespace in script mode

  • Fixed the way local scopes work in script mode
  • Documented script mode

  • Script mode: alternative syntax that makes it easier to use Ginger as a scripting language, used inside {% script %} blocks.

  • Various dependency issues fixed

  • Added a {% switch %} statement