> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/june-17th-2022-how-to-use-jinja-in-rewst.md).

# June 17, 2022 - How to use Jinja in Rewst

This call discusses what Jinja is, how to use it and some examples of how it can be used within Rewst to manipulate and transform your data, as well as filters that are implemented within the platform such as " | upper" and "| random"

A few of these examples are below

:::info {{ output }}

* "{{ }}" is used to output whatever is inside.\
  ::: :::info
* "{% %}

" is used when setting a variable, no output here. ::: :::info {# Comment #}

* "{# #}" can be used to add comments into the code. ::: :::info {{- output -}}
* "{{- -}}" removes any whitepsacing around the output. :::

If you're not sure what these are, make sure you watch the video in this recording!

{% embed url="<https://www.youtube.com/embed/uTh0rFgRgq4>" %}

**Additional Resources**

Jinja Live Parser: <https://j2live.ttl255.com/>

Jinja Filter Documentation: <https://jinja.palletsprojects.com/en/3.1.x/templates/#builtin-filters>


---

# 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://docs.rewst.help/updates/roc-open-mics/roc-open-mics-north-america/2022-roc-open-mics/june-17th-2022-how-to-use-jinja-in-rewst.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.
