> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/customize-your-pages/custom/custom-liquid.md).

# Custom Liquid

**Custom Liquid** lets you add your own code to extend or adjust the theme’s default design. It’s a flexible option for advanced users who want more control without editing core theme files. The block is added inside a section, so the snippet renders at exactly the point in the layout where you place it, and it can be moved, duplicated, or removed like any other block.

Typical uses are an app snippet that has to sit in a particular spot, or a small piece of dynamic output the standard settings do not cover.

### How to add it <a href="#how-to-add-it" id="how-to-add-it"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Online Store > Themes > Customize**.
2. In the left sidebar, click the section you want to extend.
3. Click **Add block** and choose **Custom Liquid**.
4. Paste the snippet into **Liquid code**, then drag the block to the position it should render in.
   {% endhint %}

*Result:* the preview renders the output of the snippet in that position, so you can check it before saving.

### General settings <a href="#general-settings" id="general-settings"></a>

<figure><img src="/files/0eFSTRJ9L0qYeKt49E5n" alt=""><figcaption></figcaption></figure>

| Setting         | Description                                                                                                                                                                                                  |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Liquid code** | The snippet rendered at this point in the section. Paste app snippets here as they are given to you, and test the page after saving, since faulty code shows up on the storefront rather than being ignored. |

### What changes on the storefront <a href="#what-changes" id="what-changes"></a>

* Shoppers see whatever the snippet outputs, in the position the block occupies in the section.
* Because the code lives in a block rather than in a theme file, it stays with the section it was written for and can be removed by deleting the block.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Custom](/velare/customize-your-pages/custom.md): the group this block belongs to
* [Custom CSS](/velare/customize-your-pages/custom-css.md): where store wide styling changes belong instead
* [Basic](/velare/customize-your-pages/basic.md): the standard blocks worth trying before adding code


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uxsmart.gitbook.io/velare/customize-your-pages/custom/custom-liquid.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
