> 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.md). # Basics Learn the fundamentals of Liquid in Mechanic — syntax, data types, variables, filters, operators, and control flow. Mechanic uses [**Liquid**](/platform/liquid.md), a template language created by Shopify. If you have worked with the code behind Shopify themes, you've worked with Liquid. If you are new to Liquid or need a refresher, the next few sections will cover the basics of the language. {% hint style="info" %} Mechanic's use of Liquid comes with a few extra features. It has all the core features of Liquid itself, and adds a few that specifically facilitate Mechanic development. {% endhint %} ## Shopify Liquid cheat sheet Shopify offers an excellent [Liquid cheat sheet](https://www.shopify.com/partners/shopify-cheat-sheet), a quick reference for the fundamentals. Note, however, that Liquid objects documented here do not mirror the objects offered in Mechanic-flavored Liquid. When using this cheat sheet for Mechanic work, ignore the "Objects" section entirely. :) Learn more about the difference between Shopify Theme Liquid objects and Mechanic objects here: [Mechanic objects](/platform/liquid/objects.md) ## Shopify's introduction to Liquid {% embed url="" %} ## Sources Content in this section was compiled from the following Shopify resources: * * --- # 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.md?ask=&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.