I've had a few issues with this, the latest one being this part from the ScriptObject documentation:

"Notice that when using a function with pipe calls like {{description | string.strip }}``, the last argument passed to the string.strip` function is the result of the previous pipe. That's a reason why you will notice in all builtin functions in scriban that they usually take the most relevant p

In Handlebars, mustaches can be escaped by backslash. Highlighting such things could be useful.
See jsfiddle example on how escaping works.

Statik's docs are going to quickly become out of date. We need to rather incorporate the documentation into the getstatik.com site (ideally as a Statik web site as well 😁).

Description

When developing on a responsive website there are some elements that has to be cloned and used doubled - for example a navigation for the burger-style-menu on mobile and the mega-menu on a large screen.

Instead of loading both at once, what, if it would be possible to load a module only when a certain viewport width/height is valid, like:

import { ModuleSigna

You can use the renderFn() to validate varNames and then render() to do the quick render.
also you can set that flag upon compilation that validates the names (or set it to false to let you do it)

With something like changing the lambda render callable parameter from the current lamda function to a callable object, chevron could cleanly expose the current rendering context (chevron scope) to advanced callable contexts.

In the meantime, we're relying in ugly hacks like:

import threading
import chevron.renderer

def chevron_scopes_from_render(render, _lock=threading.Lock()):

We've lost some of the coverage earned at #6 but we were not close to the requirements of https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standards

Tests, where practical. If the library/program is testable, then coverage should be >= 80% for non-data-related packages and >=90% for data related packages. Notice: the tests will be reviewed too. We will check your cove

It would be nice to put the ocamldoc-generated docs of the API online. For that we need a make doc target, and I don't know how to do that with jbuilder.