> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/platform/liquid/basics/syntax.md).

# Syntax

Liquid is a template language, which means that it uses special syntax to mark the places where Liquid code starts and ends. In this way, Liquid code can be used to fill in calculated values in a larger document.

In Shopify, Liquid is usually found in HTML templates. In Mechanic, Liquid is usually found in JSON templates.

## Liquid with output

When using the `{{ code }}` syntax, the result of the Liquid code inside will form output.

In the following example, this syntax is used to output the string `"world"`. When this template is rendered, it will produce `Hello, world`.

```liquid
Hello, {{ "world" }}
```

## Liquid without output

When using the `{% ... %}` syntax, the Liquid code inside is given the opportunity to perform work without generating output. This syntax is for preparing and modifying [variables](/platform/liquid/basics/variables.md) (using tags like [assign](/platform/liquid/tags/assign.md)), or for specifying [control flow](/platform/liquid/basics/control-flow.md) (using [conditions](/platform/liquid/basics/control-flow/condition.md) or [iteration](/platform/liquid/basics/control-flow/iteration.md)).

In the following example, a variable is assigned, modified with a new variable, and is finally rendered as output.

```liquid
{% assign scope = "world" %}
{% assign message = "Hello, " | append: scope %}

{{ message }}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/platform/liquid/basics/syntax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.